Re: UTF-16 [was: Re: Charset reviewer appointed]

[Dan Kegel <dank@alumni.caltech.edu>]

>Ken Whistler wrote:
>
>> With regards to Harald Alvestrand's summary of the open
>> issues with respect to the UTF-16 registration, the only
>> way I see forward, given the nature of the "charset"
>> definition, is to split this request into two registrations:
>> 
>> UTF-16   big-endian UTF-16
>> UTF-16BS little-endian (byte-swapped) UTF-16

How about
UTF-16BE   big-endian UTF-16
UTF-16LE   little-endian UTF-16
and, for those occasions where the byte order can vary,
UTF-16BM   UTF-16 beginning with a byte order mark

- Dan