On Sep 16, 2008, at 8:20 PM, Michael Selig wrote:

> I have been pulling my hair out trying to convert a relatively =20
> simple app to support m17n under Ruby 1.9 to see what is involved. I =20=

> need to support all common locales worldwide, and data can also be =20
> stored in UTF-8 or UTF-16. I was hoping that Ruby 1.9 was going to =20
> take the hard work out of this for me. It has to a certain extent, =20
> but UTF-16 is the problem - it breaks so many things, due to its =20
> "ASCII incompatibility" (using Ruby's definition). I can't even do =20
> simple things like pull out fields and substitute into another =20
> string without testing "encoding compatibility". Something as simple =20=

> as:
>
> 	puts "The value is #{val}"
>
> fails if val is UTF-16 data.

I'm not sure I support the pull-them out strategy, but I can confirm =20
that supporting UTF-16 in CSV has eaten about a week of my time and =20
counting.  I keep thinking I have it and finding new problem=85

James Edward Gray II=