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

[Marcos Douglas]

On Tue, Dec 24, 2013 at 3:13 PM, Jürgen Hestermann
<juergen.hestermann at gmx.de> wrote:
> Am 24.12.2013 15:22, schrieb Marcos Douglas:
>
>> Use functions, always, to convert string between RTL and LCL and
>> vice-versa IHMO is wrong because the final code is confusing. In a
>> huge application you still need to think "here is UTF-8 or
>> ANSI/UTF-16?"
>
> That's true.
> It's a pain to pay attention to this.

Someone agreed! :-)

> All units used should use the same string encoding IMO.
> But which?
> I think that's the discussion in  this thread.

Yes, this is the major problem... ;-)

>> If the RTL will be UTF-16, UTF-32, whatever the Lazarus will continues --
>> I think -- working using UTF-8.
>
> But that would be a real pain.

Would not.. IS a real pain today.

> In a program it should be possible to use strings
> without the need to convert back and forth between encodings.
> So all strings from/to FPC and LCL routines should have the same encoding.

This will depend only on the FPC team...

When I created this thread I was looking for a way to only minimize
this problem but...


Marcos Douglas