[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] "expected markup declaration" error

---

---

Hmm...

It hadn't occured to me that adding the DOCTYPE to define some character
entity references would cause Saxon 6.2 (with built-in parser AElfred)
to attempt to validate the document.

For historical reasons, the content is already being validated against
an SGML DTD (which contains exclusions and inclusions) before I attempt
to transform it.  The data itself is well-formed XML.  I'm just looking
at Saxon's documentation to see if I can tell it not to validate the
document.  Hmm, at
http://users.iclway.co.uk/mhkay/saxon/saxon6.2/conditions.html the
AElfred parser is discussed:

    Subsetting the code to include only the XML non-validating parser
    and SAX driver, with appropriate changes to the setFeature() and
    getFeature() methods.

It seems that AElfred as part of Saxon is already non-validating.  There
goes that theory out the window. :-(

Dave

----- Original Message -----
From: "Jeni Tennison" <mail@xxxxxxxxxxxxxxxx>


> I think that Saxon displays the 'looking for stylesheet PI' message
> while it's parsing the source XML - it parses it first into a node
> tree and then looks for the PI within that - but I could be wrong.
> Mike will obviously be able to confirm.
>
> That, and the message when the PI was removed, are what led me to
> think it was a parse problem with the element start tag. Ahh...
> perhaps it's that there's no !ELEMENT declaration for the root
> element? Perhaps Dave's using a validating parser and it's complaining
> because the DTD isn't complete? Dave, have you tried checking that the
> XML document on its own is well-formed (and valid) XML?



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

---