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, 15 Oct 2003 17:17:01 -0700
Message-ID: <020A3CF87FB5AC47AA67966B33845755067E01EF@xboi22.boise.itc.hp.com>
To: don@lexmark.com, Steven Pemberton <steven.pemberton@cwi.nl>
Cc: w3c-html-wg@w3.org, voyager-issues@mn.aptest.com, elliott.bradshaw@zoran.com, www-html@w3.org

Don,

Here is a new section in the Design Rationale portion of the spec:

<h3 id="s.1.3.7">1.3.7 Character Model</h3>
<p>
The W3C architectural specification <cite>Character Model for the
World Wide Web 1.0</cite> [<a href="#ref_charmod">CHARMOD</a>] gives
the <em title="RECOMMENDED in RFC 2119 context"
class="RFC2119">RECOMMENDED</em> representation of characters in
XHTML-Print.
Authors of XHTML-Print producing applications
<em title="SHOULD in RFC 2119 context" class="RFC2119">SHOULD</em>
be aware that lost cost printers might be limited in both
processing power and memory and therefore,
that fully-normalized ([<a href="#ref_charmod">CHARMOD</a>],
<a href="http://www.w3.org/TR/charmod/#sec-FullyNormalized">4.2.3)
utf-8 encoded documents could print more quickly than documents
in other forms and encodings.
</p>

I hope that this section will help discourage UTF-16.

Jim
Received on Wednesday, 15 October 2003 20:18:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:58 GMT