RE: proposed Eistring interface

From: Ben Wing [mailto:ben＠666.com] I wrote this last night: NOTE: One possible default internal representation that was compatible with UTF16 but allowed all possible chars in UCS4 would be to take an unused range of 2048 chars (not from the private area because Microsoft actually uses up most or all of it with EUDC chars). Let's say we picked 4000 - 47FF. Then, we'd have: 0000 - FFFF Simple chars D[8-B]xx D[C-F]xx Surrogate char, represents 1M chars 4[0-7]xx D[C-F]xx D[C-F]xx Surrogate char, represents 2G chars This is exactly the same number of chars as UCS-4 handles, and it follows the same property as UTF8 and Mule-internal: 1. There are two disjoint groupings of units, one representing leading units and one representing non-leading units. 2. Given a leading unit, you immediately know how many units follow to make up a valid char, irrespective of any other context.