CR> W3C Character Model and Early Uniform Normalization

CR> W3C Character Model and Early Uniform Normalization

BIGELOW,JIM (HP-Boise,ex1) jim.bigelow at hp.com
Thu Sep 18 20:01:21 EDT 2003


Hello,

I've been reading the W3C Working Draft, Character Model for the World Wide
Web [1], which deals with requires of internet applications should as
producers and consumers of XHTML-Print. 

This report [1] indicates that XHTML-Print as a derivate of XHTML is bound
by it. Therefore, by extension, all XHTML-Print producing and consuming
applications are bound by this report all thought this is never explicitly
stated in any version of the XHTML-Print specification [2,3].

One of the interesting parts of [1] is the requirement that applications
that produce XHTML-Print should produce fully-normalized text [4] meaning,
among other things, that it is in Unicode Normalized Form C [5], which
favors the canonical composite forms of Unicode characters. 

>From the printer's perspective, as a receiver of XHTML-Print documents, this
makes its job easier since it can always assume that text is
fully-normalized and it doesn't have to do so itself. 

My question to you is, do you think that the XHTML-Print specification
should be amended to site the requirement that a conforming XHTML-Print
document be fully-normalized?  Furthermore, should a printer be required to
check an XHTML-Print document to see that it is fully-normalized or should
it assume so?  Lastly, should a printer normalize text that is not
fully-normalized or discard it?

Jim 

--
Jim Bigelow, 
Editor: XHTML-Print & CSS Print Profile
Member: W3C HTML and CSS Working Groups
Hewlett-Packard
208-396-2068
jim.bigelow at hp.com  


[1] http://www.w3.org/TR/charmod/
[2] http://www.pwg.org/xhtml-print/HTML-Version/XHTML-Print.html
[3] http://www.w3.org/TR/xhtml-print/
[4] http://www.w3.org/TR/2003/WD-charmod-20030822/#sec-FullyNormalized
[5] http://www.unicode.org/unicode/reports/tr15/#Specification



More information about the Cr mailing list