[fpc-devel] Unicode resource strings

[Florian Klämpfl]

Am 20.08.2012 20:27, schrieb Graeme Geldenhuys:
> 
>>>   * UnicodeString is always UTF-16 (so everything but Windows takes a
>>> conversion penalty)!
>>
>> A decision has been made and you are not happy with it. Fine. But before
>> you called the fpc team being in a deadlock?
> 
> Many things by the FPC team get discussed or debated behind closed
> doors, so how are we even in the fpc-devel mailing list to know what
> is decided. Last I read in fpc-devel it was still heavily debated and
> no decision was in sight. I guess now we know, the decision is UTF-16
> everywhere where UnicodeString is used.

Actually, you overestimate what the "FPC team" can decide. The
"decision" was more like: somebody popped up and proposed to implement
Unicodestring support in a D2009+ compatible way without breaking too
much legacy stuff. So we could say, ok, we merge this into fpc's svn.
The alternative would have been to say no, we leave things as they are:
"deadlock".

The current situation is:
- either somebody starts to implement support for unicodestring being
utf-8 (or whatever) on linux in a compatible way with the current
approach, then 2.8.0 will use this
- nobody works on it, then 2.8.0 comes with unicodestring=utf-16 always.