Re: Anachronistic Acronyms in Parrot?

[Dan Sugalski]

At 01:57 PM 9/21/2001 +0100, Donal K. Fellows wrote:
>Dan Sugalski <[EMAIL PROTECTED]>
> > I am also willing to put up with some hair if it means things go faster
> > many places. I've my eye on China and Japan (amongst other places) as
> > targets for parrot, and Unicode's not gonna cut it there.
>
>Why would UCS-16 not make it in China or Japan, where you already need
>a multibyte encoding anyway?  Or are you persisting in mixing up
>Unicode and UTF-8?

I'm well aware of the differences between Unicode and the UTF-X encodings. 
(For various values of X) 16 bits is enough for some but not all character 
sets, and Parrot will use it where appropriate. (As it will 8 and 32 bit 
characters) Internally some strings might, if someone provides the library, 
encoded with UCS-16. The engine itself, however, will only deal with fixed 
length characters. IIRC that shoots down UCS-16, as it's got some set 
shifting code in there. (Might be remembering wrong)

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk