Re: C # character model

Antoine Leca [EMAIL PROTECTED] wrote: [...] APIs use and return single 16-bit values. Ah, that may be a problem (what is the ToUpper return value of ß?) I don't know the mentioned API, but it could return 0x00DF or (to indicate it as an error) 0x. I don't see a problem. --Torsten

Re: C # character model

Torsten Mohrin wrote: Antoine Leca [EMAIL PROTECTED] wrote: [...] APIs use and return single 16-bit values. Ah, that may be a problem (what is the ToUpper return value of ß?) I don't know the mentioned API, but it could return 0x00DF or (to indicate it as an error) 0x. I don't

Re: C # character model

Almost all international functions (upper-, lower-, titlecasing, case folding, drawing, measuring, collation, transliteration, grapheme-, word-, linebreaks, etc.) should take *strings* in the API, NOT single code-points. Single code-point APIs almost always malfunction once you get outside of

Re: C # character model

Antoine Leca [EMAIL PROTECTED] wrote: Torsten Mohrin wrote: Antoine Leca [EMAIL PROTECTED] wrote: [...] APIs use and return single 16-bit values. Ah, that may be a problem (what is the ToUpper return value of ß?) I don't know the mentioned API, but it could return 0x00DF or (to

C # character model

Anyone notice the new product from MS called C# (C-sharp)? It is a Java-like language...appears to be the Java-like product available via J++ a while back. I noticed its character specs. A char is a 16-bit Unicode code point...no UTF-32, no 32-bit Unicode value. It appears that this new product

Re: C # character model

John O'Conner wrote: It appears that this new product is not adopting UTF-32...and is sticking with UTF-16 (or more appropriately UCS-2?). APIs use and return single 16-bit values. This certainly doesn't make surrogate-pair values easy to use. What influence, if any, does this have on the