[Mono-list] unicode trouble

gabor gabor@z10n.net
Mon, 9 Feb 2004 08:22:25 +0100

On Sun, Feb 08, 2004 at 10:37:45PM -0800, Chris Mullins wrote:
> .NET has the ability to: 
> 1) Iterate over strings by graphemes so that regardless of encoding,
> developers can treat Unicode combining characters and surrogate pairs as
> a single entity. 

> 2) Build and manipulate strings that consist of any currently defined
> Unicode CodePoint. While creating a grapheme for a CodePoint >0xFFFF is
> tricky, once the grapheme is properly encoded into a string, any of the
> standard string manipulations can be used to append it with other
> strings, or otherwise manipulate it. 
ok, so i can use some lower level stuff and basically implement utf16 
(i mean the surrogates).


but that means that the normal string handling stuff will simply be incorrect.

i just can't understand why the designers of dotnet didn't look at the unicode
standards. i can understand that java has this problem, but java is much older 
than dotnet.

maybe it's because winapi uses 16-bit characters?