I'm very much ignorant about widestrings, utf-16, and internationnal
support in Lazarus. I mean, I have just no clue of what kind of work
it requires. What needs to be changed in the lcl source code.
If someone could point me to an example and the implications of the
changes, I'll see if I'm able to give some help on the issue.
2006/5/17, Mattias Gaertner <[EMAIL PROTECTED]>:
On Wed, 17 May 2006 09:52:46 -0500 (CDT)
[EMAIL PROTECTED] wrote:
>
> > UTF-16 is multibyte.
> > There are more unicode characters than 2 byte numbers, so you won't find
> > a complete 2 byte unicode encoding.
>
> I read somewhere that there was a previous Unicode format that ALWAYS uses
> 2 bytes for each character, but DOESN'T support all languages.
>
> If I'm right, we can use that as a start to design a Unicode L.C.L.,
> and eventually change to other format that support other languages.
The decision was to 'create' a unicode LCL with UTF-8 supporting all
languages.
*IF* we add properties/methods with widestrings, then they will be UTF-16,
also supporting all languages.
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
