W3C home > Mailing lists > Public > www-html@w3.org > October 2003

Re: allow UTF-16 not just UTF-8 (PR#6774)

From: BIGELOW,JIM (HP-Boise,ex1) <jim.bigelow@hp.com>
Date: Wed, 8 Oct 2003 10:24:45 -0400
Message-ID: <020A3CF87FB5AC47AA67966B33845755063CA7B6@xboi22.boise.itc.hp.com>
To: don@lexmark.com
Cc: elliott.bradshaw@zoran.com, www-html@w3.org

uest  - reply #3

Date: Wed Oct  1 12:43:54 2003

Don and Elliott,

The HTML working group discussed my question of why and XHTML-Print
must be a conforming XML processor (in particular, why it must support both
UTF-8 and UTF-16 encodings) on October 1, 2003.  

The answer is that XHTML-Print must be a conforming XML processor and
both UTF-8 and UTF-16 encodings to preserve compatibility between xml-based

If XHTML-Print processors only supported UTF-8 then an xml-based application
could not be reliably depended upon to emit an XHTML-Print document that the
XHTML-print application could process.  For example, an xml-based Xforms
application's output of an XHTML-Print document cannot be restricted by the
XHTML-Print specification to UTF-8 since the application may not be able to
control the encoding.

Section 4.3.3 [1] and Appendix F [2] of the XML specification [3] give
heuristics for determing a document's encoding when the charset parameter of
MIME type [4] is absent.

An example UTF-16 decoder is available at [5] other encodings are at [6].

Jim Bigelow

[1] http://www.w3.org/TR/REC-xml#charencoding
[2] http://www.w3.org/TR/REC-xml#sec-guessing
[3] http://www.w3.org/TR/REC-xml
[4] http://www.ietf.org/rfc/rfc3023.txt
[5] http://interscript.sourceforge.net/interscript/doc/en_iscr_0282.html
[6] http://interscript.sourceforge.net/interscript/doc/en_iscr_0275.html

Received on Wednesday, 8 October 2003 10:24:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:05 UTC