- From: <bugzilla@jessica.w3.org>
- Date: Sun, 11 Dec 2011 14:34:21 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15142
Glenn Adams <glenn@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |glenn@skynav.com
--- Comment #1 from Glenn Adams <glenn@skynav.com> 2011-12-11 14:34:20 UTC ---
this proposal should be rejected for a variety of reasons:
(1) it is not (or should not be) the prerogative of the HTML specification to
define a character encoding scheme (form) or to associate a label with an
existing scheme (form); rather, HTML is a consumer (user) of externally defined
character encoding schemes (forms);
(2) the Unicode Consortium is the appropriate forum for considering the
possible registration of any new character encoding based upon the Unicode
Character Set; [1]
(3) the term "UNICODE" is a registered trademark of the Unicode Consortium,
governed by the Unicode trademark usage policy [2];
(4) the Unicode Standard expressly DOES NOT equate the character encoding
"UTF-16" with the term "UNICODE", and does not give priority to any of the
standard three Unicode Encoding Forms (UTF-8, UTF-16, UTF-32); see, e.g.,
Section 3.9 of [3]
(5) nonetheless, according to Brian Carpenter, former chair of the Internet
Advisory Board (IETF), "The IETF has made the Unicode-compatible UTF-8 format
of ISO 10646 the basis for its preferred default character encoding for
internationalization of Internet application protocols" [4]
[1] http://www.unicode.org/
[2] http://www.unicode.org/policies/logo_policy.html
[3] http://www.unicode.org/versions/Unicode6.0.0/ch03.pdf
[4] http://www.unicode.org/announcements/pr-3.0.html
regards,
glenn adams
former technical director, unicode consortium
--
Configure bugmail: https://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 Sunday, 11 December 2011 14:34:22 UTC