Markus,
I think that big-endian UTF-32 is the only way to go. The solution to ASCII
vs. EBCIDC would go away if we got all of the hardware to support Unicode
natively. We could forget about bytes and make the 32bit word the least
addressable amount of memory.
utf-64 would only be used for vanity characters. Sort of like the star
registry. utf-64 would consist of 0xFFFFFFFF followed by the 64-bit number
as 2 32 bit numbers. Implementing utf-64 would be only for the vain and not
part of any known or imaginable OS.
Carl
> -----Original Message-----
> From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]On
> Behalf Of Markus Scherer
> Sent: Thursday, June 21, 2001 11:16 AM
> To: unicore; unicode
> Subject: The perfect solution for the UTF-8/16 discussion
>
>
> Abolish all in-process Unicode encodings except UTF-16.
> If everyone uses the same encoding form then there is no problem
> with different string lengths, results of binary comparisons, etc.
>
> Once we are here, abolish all little-endian UTF-16
> implementations. This will save a lot of byte swapping, and
> binary comparisons can always be performed with memcmp().
>
> Heck, abolish all little-endian platforms and all platforms with
> integer widths other than 8, 16, 32, etc.
>
> :-)
>
> markus
>
This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:17:19 EDT