Lists Home |
Date Index |
- To: email@example.com
- Subject: Re: [xml-dev] Whitespace following a text declaration
- From: David Carlisle <firstname.lastname@example.org>
- Date: Mon, 6 Feb 2006 10:29:36 GMT
- Cc: email@example.com
- In-reply-to: <200602061011.KAA17360@nag.co.uk> (firstname.lastname@example.org)
- References: <200602061011.KAA17360@nag.co.uk>
> 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.
Isn't .net right here? The production for a parsed entity is:
 extParsedEnt ::= TextDecl? content - Char* RestrictedChar Char*
which means that all the text after the ?> (including the newline)
should be parsed as content, doesn't it?
The situation is different from a document, where a following element is
mandatory (and white space after the xml declaration is parsed as S?)
An external parsed entity might _only consist of text.
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit: