RE: Are charset names supposed to be case sensitive?

[Shawn Steele <Shawn.Steele@microsoft.com>]

FWIW: I'm on vacation, so I'll probably forget to check in on this thread ;-), however, fwiw:

* I don't mind clarifying the name(s) being used.
* Changing names will break a ton of stuff probably, so anything you see that seems odd is probably "stuck" that way :(  
* So, it'd be nice if any document noted cases where things have been historically different, eg "AAAAA means XXXXX, but sometimes people have done YYYY with it", or "behavior ZZZZ should be named BBBB, but sometimes people call it CCCC"

Doug's suggestion of a table sounds good, but I suspect some columns may end up with multiple meanings.  However maybe we could then easily see where stuff is unambiguous?

-Shawn

 
http://blogs.msdn.com/shawnste


________________________________________
From: Doug Ewell [doug@ewellic.org]
Sent: Monday, December 19, 2011 7:36 AM
To: ietf-charsets@iana.org
Subject: Re: Are charset names supposed to be case sensitive?

I guess I would like to see some sort of table breaking down the various
flavors of UTF-16 and/or UCS-2 that would need to be tagged separately:

* big-endian or little-endian by default
* accepts BOM
* requires BOM
* supports all 17 planes or just BMP
* etc.

That way I would have a clearer sense of what can be currently tagged,
what cannot be tagged and needs to be, and what is just an application
quirk or bug.

It seems Leif might be trying to tag the incomplete or erroneous
behavior of individual applications, even if they don't correspond to
documented behavior, or to tag mis-documented behavior that may not
actually be implemented (like "unicode" meaning "BMP only").  I'm not
sure that's a goal of registering charsets.  It also seemed to me—though
I assume I'm wrong here—that he was trying to call particular attention
to errors in Microsoft implementations, but I'm sure Shawn and others
can speak to that.

--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell ­