[fpc-pascal] UTF8 codepage for file in trunk: codepage constant names?

Reinier Olislagers reinierolislagers at gmail.com
Thu Jan 9 15:17:03 CET 2014


On 09/01/2014 15:12, Michael Van Canneyt wrote:
> On Thu, 9 Jan 2014, Reinier Olislagers wrote:
>> On 09/01/2014 14:49, Jonas Maebe wrote:
>>> On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
>>>> On 08/01/2014 17:17, Jonas Maebe wrote:
>> I see your point, but I think that people should just regularly update
>> the wiki as information gets outdated etc.
>> If people cannot go from a broken link to typing in the keyword it
>> points to in a search engine, well....
> 
> That is a dangerous path you step onto.
You did not notice I have walked that path for a while now?

> There are so many things I think are so incredibly obvious ;-)
You know, the wiki is free to edit: go ahead.
I don't mind if somebody else thinks this is so important that he wants
to take the time to remove info; a corrolary IMO is that people who take
the trouble to add info, update the wiki etc should do as they see fit.
(IOW: I'm not looking for edit wars and respect contributions/opinions
from people like Jonas and DoDi who put effort into updating the wiki)

A counter example: after trying to get practical examples, concrete
documentation - e.g. the actual names for ($codepage xxx} into fpcdocs
(see bug report I raised about console mode applications that worked in
2.6 and stopped working in trunk) I was told that isn't the way things
are done.
Now I'm not pushing any more and just put useful information on the wiki.




More information about the fpc-pascal mailing list