On 04/13/2016 11:08 AM, Sven Barth wrote:
The code pages that are relevant here are only single byte code pages
(e.g. CP1252) or UTF-8, *never* UTF-16 as a AnsiString can not store
UTF-16 data.
I see. And using 8 bit encoding as the brand for not the explicitly
user-defind "String" type does make sense for a compiler that is
supposed to create executables for multiple OSes does make prefect sense.
But AFAIK, Unicode aware Delphi uses UTF16 for the not the explicitly
user-defind "String" type. (While AFAIK, not Unicode aware Delphi can't
handle UTF8.)
So this is not compatible to either of them. In fact I am not asking for
such compatibility (let alone that the two Delphi variants are even more
incompatible to each other), but we need to be aware of the issue.
-Michael
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
