[Lazarus] Lazarus (UTF8) and Windows: SysToUTF8, UTF8ToSys... Is there a better solution?

[Marcos Douglas]

On Mon, Dec 16, 2013 at 3:30 AM, Reinier Olislagers
<reinierolislagers at gmail.com> wrote:
> On 15/12/2013 20:47, Marcos Douglas wrote:
>> On Sun, Dec 15, 2013 at 3:13 PM, Reinier Olislagers
>> <reinierolislagers at gmail.com> wrote:
>>> On 15/12/2013 16:25, Marcos Douglas wrote:
>>>> On Sun, Dec 15, 2013 at 1:08 PM, Bart <bartjunk64 at gmail.com> wrote:
>>>> 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?
>>
>> You propose include LCL in packages that not have LCL references and
>> change all code of these packages to use UTF8 functions??
>>
>> I think didn't understand what you proposed...
> I think I don't understand what you're after? You said yourself you
> don't want to pass ANSI strings!?!?

I said "a trick to use only ANSI".

> My suggestion is to replace calls to the FPC (ANSI) RTL with LCL UTF8
> equivalents in your code where possible.

But FPC still ANSI and all read/write in FPC is ANSI. We can not
override these internal FPC's routines... and, some packages are used
by others non-GUI program and that not have dependencies to LCL.

> Apart from that there's not much else you can do except contribute
> patches to help "unicode-ise" the FPC RTL...

Ok... But first I would like to know who have these same problems,
like me, working on Windows and what these people do to bypass these
problems.

Regards,
Marcos Douglas