I don't mind if we require that an XHTML-Print printer normalizes its
input.
We probably have to stipulate what this means for CR. If a printer
advertises a repertoire that supports two combinable characters, is it
implicitly saying that it also supports the combination of the two? I am
inclined to put this point in Best Practices and leave it out of the
normative spec.
(I'll track this as a Last Call issue for CR.)
--------------------------------------------------------------------------------
Elliott Bradshaw
Director, Software Engineering
Zoran Imaging Group (formerly Oak Technology Imaging Group)
781 638-7534
"BIGELOW,JIM
(HP-Boise,ex1) To: "'cr at pwg.org'" <cr at pwg.org>
" cc:
<jim.bigelow at h Subject: RE: CR> W3C Character Model and Early
p.com> Uniform Normalization
Sent by:
owner-cr at pwg.o
rg
09/22/2003
06:51 PM
Ira wrote:
>> (2) [answering Jim]
> No - a printer should _never_ throw away any document data
> that happens not to be normalized ...
I agree. However, the XHTML-Print spec [1, 2, 3] in their Printer
Conformance sections that a printer may "flush or otherwise reject a
non-conforming XHTML-Print document." This is the source of my worry that
a
printer could reject a document that is not normalized.
>> (3) [answering Jim]
> No - a printer should _never_ trust the sender/generator
> to have properly normalized Unicode data.
If a very low cost printer assumed that an XHTML-Print document's content
is
normalized and it is not, the very worse that could happen is that word
breaks occur in the wrong place, e.g., between a letter and it's
non-spacing
mark, or class/id selectors don't match the value of the class/id attribute
-- causing the misapplication of style sheet rules.
I think the a printer should normalize and therefore correctly handle
combining characters. I just wondering if other printer people think such a
normalization should be mandated for all printers.
Jim
[1] ftp://ftp.pwg.org/pub/pwg/xhtml-print/drafts/xhtml-print-draft-095.pdf
[2] http://www.pwg.org/xhtml-print/HTML-Version/XHTML-Print.html
{3]