From: Dmitry Severin <dmitry.severin@...>
Date: 2006-06-15T14:55:03+09:00
Subject: Re: Unicode roadmap?

------=_Part_91960_2997452.1150350900907
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

IIRC, Matz has said that internally String won't change, and I suspect that
a CharString class (or smth like) won't be ever added.

Maybe just introducing String#encoding flag and addig  new methods to String
with prefixes, like char_array, char_slice, char_length, char_index,
char_downcase, char_strcoll, char_strip, etc. that will internally look at
encoding flag and process respectively bytes in this particular string
without  conversion (just maybe some hidden), and leaving old
byte-processing methods intact, would be the way to keep older code working
and enjoy M17N?

Though, as for me, it is still unclear, what should happen, if one tries to
perform operation on two strings with different String#encoding...

------=_Part_91960_2997452.1150350900907--