- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 18:57:00 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23923
--- Comment #8 from Michael Dyck <jmdyck@ibiblio.org> ---
(In reply to Tim Mills from comment #5)
>
> When converted to XQueryX/XML 1.0 the &x2028; is not treated by the XML
> parser as a line ending character. It would be if it were XQuery/XML 1.1.
On second thought, I'm not so sure. Semantically, an XQueryX processor
evaluates a query by:
(a) transforming it to the human-readable syntax; and
(b) evaluating the human-readable syntax.
And it's not clear that the version of XML used in (a) must match the choice of
choice of rules for normalizing line breaks in (b).
Specifically, although the query begins with
<?xml version="1.0"?>
and so must be processed by an XML 1.0 processor, which will leave the Line
Separator as is, that happens at (a), and it's still possible for the XQuery
processor at (b) to use the end-of-line rules of XML 1.1 (as indicated in the
test-case), which *will* normalize the Line Separator into a Line Feed.
(Or it can skip the test-case if it's unable to use the 1.1 rules at (b).)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 18:57:02 UTC