On Sun, Dec 22, 2013 at 4:56 PM, Marco van de Voort <[email protected]> wrote: > On Sun, Dec 15, 2013 at 06:13:32PM +0100, Reinier Olislagers wrote: >> > FPC's context. >> > These components do not use Lazarus' routines and that is the BIG >> > problem. I need to "remember" in pass only ANSI strings for these >> > components as remember to convert the component's output string >> > results to use in Lazarus. >> >> Why not just include a project reference to LCLBase (IIRC that should be >> enough) and just always use the LCL units until FPC catches up? > > FPC 2.7.x can compile the windows unit in unicode (UTF16) mode. Most system > and > sysutils file related routines are already unicode (UTF16 with Rawbytestring > overload).
So FPC 2.7.x can compile the windows unit in unicode (UTF16) mode. But how it will work with Lazarus that uses UTF-8? Lazarus will not to change to UTF-16 -- only for Windows -- then everything will stay the same to Windows programmers? Thanks, Marcos Douglas -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
