ISSUE-76: Clarify 'preferred name' for encodings

Clarify 'preferred name' for encodings

Raised by:
Richard Ishida
Opened on:
4.2. Character encoding declaration

"The value must be a valid character encoding name, and must be the preferred name for that encoding, as specified in the IANA [Character Sets] registry."

It would be good to have a link on 'preferred name' to make it clear that this includes the encoding name if there is no preferred name. See:
"The preferred MIME name of a character encoding is the name or alias labeled as "preferred MIME name" in the IANA Character Sets registry, if there is one, or the encoding's name, if none of the aliases are so labeled."

Otherwise it is misleading. (To be honest, it's still not overly clear. Much as new jargon is best avoided, this may be a case where we need a slightly different term, such as 'html-preferred'.)
Related Actions Items:
No related actions
Related emails:
  1. Review of tracker issues for best practices (part II) (from on 2015-03-28)
  2. [Bug 13395] i18n-ISSUE-76: Clarify 'preferred name' for encodings (from on 2012-10-06)
  3. [Bug 13395] New: i18n-ISSUE-76: Clarify 'preferred name' for encodings (from on 2011-07-27)
  4. [minutes] Internationalization WG telecon 2011-07-27 (from on 2011-07-27)
  5. I18N-ISSUE-76: Clarify 'preferred name' for encodings [HTML5-markup-prep] (from on 2011-07-22)

Related notes:

[aphillip]: comment accepted for HTML5 LC

27 Jul 2011, 15:34:46

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Bert Bos <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 76.html,v 1.1 2023/07/19 12:02:06 carcone Exp $