On Fri, 2 Aug 2002, Clifford Heath wrote:
> IMO the ISO 10646 folk should be approached to allocate a 24-bit
[...]
> I agree with Dan's comments, and think this would be the best way
> to resolve the issue.

Then we would delay i18n string processing until the iso 10646 people have 
made such a decision? This will probably never happen! And even if it 
does, then not in the next few years. We need unicode in ruby *now*. It 
seems we can get by with a choice of two possible canonical encodings to 
be used for the result of concatenating strings with different encodings: 
utf-8 and some mojikyu encoding, based on the encodings of the original 
strings. Let's implement it.

  Tobias