At 2006-02-05 20:34 +0000, Michael Kay wrote:
>Given an external parsed entity of the form:
>
><?xml version="1.0" encoding="UTF-8" ?>
><extEnt attr="x"><sub2>z</sub2></extEnt>
>
>I'm surprised to discover that the parser in .NET includes the newline after
>the text declaration as part of the entity's expanded text, while both
>Crimson and Xerces (the versions built into JDK 1.4 and JDK 1.5
>respectively) exclude the newline.
>
>I can't see any justification for excluding the newline: is this a
>non-conformance?
Given XML http://www.w3.org/TR/2004/REC-xml-20040204 production 77
for a text declaration does not include a newline and production 78
states that content immediately follows the text declaration, I agree
that the newline should be part of content.
In my book materials I extensively use external parsed general
entities comprised solely of text, most of which are generated as
output from XSLT, and I wouldn't expect any characters to be removed
when they are used.
. . . . . . . . . . . Ken
--
Upcoming XSLT/XSL-FO hands-on courses: Denver,CO March 13-17,2006
World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman mailto:
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
