[fpc-devel] Unicode proceedings

[Felipe Monteiro de Carvalho]

On Fri, Nov 18, 2011 at 2:36 PM, Michael Schnell <mschnell at lumino.de> wrote:
>> And now very recently I found out that this is no longer valid in 2.7,
>> ansistring can be configured to hold a UTF-8 value in a valid and supported
>> way, and this changes a lot of things to me.
>
> To the worse I gather.

Quite the contrary, everything is so much better now, because from
what I understood ansistring can be configured to hold a utf-8 string
globally. So Lazarus can globally initialize it like this so we can be
on the safe side for the first time in decades: Still using utf-8
everywhere but now with RTL support and doing it the right way.

And it gets even better: From what I understood we don't even need to
request anything to be changed in the RTL, everything required will
automatically come with FPC 2.8

In this solution a migration would be needed, although a very simple
one, and it will likely take years to complete this migration because
we won't jump into requiring FPC 2.8+ so quickly. But it really looks
like this solution could be it. A safe and stable road ahead without
major compatibility breaks.

The only thing that could stop this solution would be FPC dropping
support for the Ansistring-based RTL, which looks very unlikely from
what I understood.

-- 
Felipe Monteiro de Carvalho