Re: Are charset names supposed to be case sensitive?

[Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>]

Hi Martin,

"Martin J. Dürst", Sun, 18 Dec 2011 17:33:40 +0900:
> On 2011/12/18 7:02, Leif Halvard Silli wrote:
>> "Martin J. Dürst", Sat, 17 Dec 2011 22:09:31 +0900:
>>> On 2011/12/17 17:01, Leif Halvard Silli wrote:

>>> I would strongly suggest not to use case differences to refer
>>> to different usages of the same label, because this may cause a lot
>>> of confusion. (It already had Shawn confused, and me, too.)
>> 
>> Looking at my registration letter for 'unicode', I think it isn't the
>> very casing, but the language I use about the casing that is possibly
>> confusing:
>> 
>> ''' NB! Alias: At the time of this registration, the spec upon which
>>    the registration of the 'unicode' and the 'unicodeFFFE' charset is
>>    based, defines 'utf-16' (lowercase) as alias for 'unicode'.[2] '''
>> 
>> If I remove the '(lowercase)', then the above should be clear enough,
>> no? Also: In the same letter I say that 'utf-16' lowercase *cannot* be
>> registered as alias for 'unicode' due to the fact that 'UTF-16'
>> uppercase is already registered as a charset name. So there is material
>> enough to at least avoid jumping to conclusions ...
> 
> Can you go over your templates and check for these and similar places 
> and fix and resend them?

Yes, I will do that.

  ... snip ... 

> Yes, and "alias" vs. "name" isn't very direct either. I'd personally 
> use "UTF-16 according to RFC..." vs. "UTF-16 according to Microsoft" 
> or some such.

That's a good wording proposal, thanks.
-- 
Leif Halvard Silli