W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 11423] Character sets not registered with IANA

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Feb 2011 22:58:04 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Po1wC-0002mb-8N@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11423

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-11 22:58:03 UTC ---
(In reply to comment #9)
> The IANA character set registry is what the rest of the Internet uses.

That's not at all clear. In particular, comment 6 suggests it's not what
browser vendors use, which is the target audience of the requirement in
question.


> If you believe it is incomplete, feel free to augment it.

I'm happy for the IANA character set registry to be updated, but whether I do
it, or you do it, or someone else does it, or nobody does it, it doesn't change
what the HTML spec needs to say.


> It would be satisfactory to
> me if the HTML specification decided to define it (as long as the specification
> is sufficiently precise for interoperability and it can be used as the
> reference for the IANA registry).

The HTML spec references a definition of Windows 949.


> Choosing to specify behavior in terms of
> some vendor-specific character set that is undefined actually *harms*
> interoperability.

It isn't undefined, just not registered.


> Since I don't use Windows, how am I to know what byte
> sequences are valid and what their meanings are in this mystery encoding?

Look at its definition, cited in the HTML spec.


> It
> would be totally acceptable for me to simply define windows-949 as UTF-8, since
> there is no other specification, and since it is otherwise undefined, I hereby
> define it as such.

There is another specification.


EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: no new information since comment 8.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 11 February 2011 22:58:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 February 2011 22:58:06 GMT