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

Marcos Douglas md at delfire.net
Mon Dec 16 12:22:54 CET 2013


On Mon, Dec 16, 2013 at 7:41 AM, Mattias Gaertner
<nc-gaertnma at netcologne.de> wrote:
> On Sun, 15 Dec 2013 17:47:09 -0200
> Marcos Douglas <md at delfire.net> 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:
>> >>> So for basic stuff all this is already taken care of.
>> >>
>> >> Only in Lazarus' context... but I have some components that is only
>> >> 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?
>>
>> You propose include LCL in packages that not have LCL references and
>> change all code of these packages to use UTF8 functions??
>
> Note:
> The Lazarus UTF8 functions are in the package LazUtils.
> You don't need to use the LCL (nor LCLBase) if you only need the
> UTF8 functions.
>
> Mattias

You're right.
IMHO, the real problem is not to use LCL/LazUtils but having multiple
calls to SysToUTF8..UTF8ToSys in all code.

Question:
After the new FPC version is released, how Lazarus will work together
"FPC Unicode"?


Marcos Douglas




More information about the Lazarus mailing list