On 07/09/2013 12:55 PM, Marco van de Voort wrote:
Well, the main reason is not FPC, but Windows. UTF8 in Windows on
_API_ level is simply not a good idea
You are absolutely right.
Here, in theory the Lazarus LCL and the FPC RTL could help by by
providing an application programmer API that does not force a dedicated
encoding. But to do so without the necessity to provide multiple OS
depending versions of the LCL and RTL interface definition, it would
need the compiler to provide support this.
In a perfect world the application programmer could use the encoding he
thinks is appropriate for the internals of his busyness logic and the
programming system does the correct things do use the API of the OS the
program is compiled for (while for optimum performance do code
conversions only when necessary).
-Michael
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
