Re: ISO-8859-1 encoding and XmlDecl omision (was Re: L

> Not always though. If the encoding is specified in the transport of the
> XML,

er yes I considerd posting a PS to add that, but thought it would come
up soon enough:-), Leaving the encoding specified by the transport is a
very dangerous practice though, it means you accept a well formed
document from a server (well formed due to encoding speciifed in http
header) save it to the file system, look at it again and lo! it is no
longer well formed.

  If the processor ignored the omit-xml-declaration, then this would cause
  the xml stream to not be well-formed since the (duplicate)
  xml-declarations do not occur at the beginning of the stream.

It has to either ignore the omit-xml-declaration, or ignore the
requested encoding, and to output using an encoding that doesn't require
a text declaration (utf8 or utf16)
the safe way to combine the document fragments is, as you say, to treat
them as general parsed entities and so include them into a master
document via an entity reference. that way each fragment has its own
encoding declaration, and possibly different encodings.

David



-- 
http://www.dcarlisle.demon.co.uk/matthew

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list