[Lazarus] Unicode on Windows

[Marco van de Voort]

On Mon, Apr 09, 2012 at 11:56:50AM -0300, Marcos Douglas wrote:
> >> The result is 5 not 3, but you did know this of course.
> >
> > Both are valid results. The first is needed when you copy the string (bytes
> > to move) the second to display the string (since it will probably be around
> > 3 glyphs (yes, I know that is not guaranteed))
> 
> Yes, both are valid and do not have problem with the RTL. It was
> designed to work using AnsiString, we know that... but these problems,
> on Windows, is very dangerous to developer, don't you think?

That's why FPC postponed making everything unicode till proper support was
added.