On Sep 16, 2008, at 3:37 AM, Martin Duerst wrote:

> So I'm suggesting that we produce some special error message for
> UTF-16, such as "UTF-16 not available, use either UTF-16BE or
> UTF-16LE". In general, I don't like such special-casing, but
> given that Ruby tries to be user-friendly, it may be worth
> doing.

I haven't been involved in this discussion, but in my experience a  
fairly high proportion of UTF-16 texts begin with a Byte Order Mark.   
In this case, the programmer doesn't need to worry about BE/LE.  So  
maybe in some cases Ruby could actually accept "UTF-16" and silently  
do the right thing?  -Tim