On 26 Nov 14, at 17:23, Jonas Maebe wrote: > On 26/11/14 17:21, Sven Barth wrote: > > Yes, nevertheless the header record is the same for UnicodeString and > > AnsiString and thus it also has a codepage field which is always > > initialized to CP_UTF16 however. > > It can also be CP_UTF16BE (which it is on big endian FPC targets right now).
BTW, in this context - can users choose UTF16BE on little endian platforms (and vice versa)? In other words - do the respective UnicodeStringManager routines have to check the source/target endiannes in the respective field of the header when performing conversion between AnsiStrings and UnicodeStrings? Not that the current implementations for Unix or Windows would seem to worry about this, but I'd prefer to know (and preferably have documented ;-) ) whether it's an omission or intention based on an explicitly defined rule... Tomas _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
