Subject: Re: [xsl] XSLT 2.0 compability issue occured in topicmerge.XSL in DITA 1.5.1 From: team wise <dfanster@xxxxxxxxx> Date: Tue, 19 Jun 2012 21:29:39 +0800 |
Hi Mike, To clarify , you are right the input XML as PSMI file to Saxon is not a valid XML at all. That XML parser stops it from being processed , which led to the failure. It comes back to the origional issue to be fixed properly prior to PSMI transform. My apologises for this misleading info. Cheers Ray 2012/6/19, Michael Kay <mike@xxxxxxxxxxxx>: > >[xslt] > D:\InfoShare\DataSOMC\PublishingService\Data\DataExports\GUID-AA6DE3A2-8ECD-47B5-9839-4C705E444AC4.20120618182735036\1\en\out\GUID-F6C2D026-C2A6-4376-AD33-EB2BF5AE0544.psmi:1:39: > > Fatal Error! Error reported by XML parser Cause: > org.xml.sax.SAXParseException: Content is not allowed in prolog. > > >It looks like a Saxon issue. > > Lots of people tend to assume that, despite the fact that Saxon was very > careful to say that the error comes from the XML parser (which is not > part of Saxon), and the XML parser is explicit that the problem is with > the data it is being asked to process. > > "Content not allowed in prolog" is a message that comes from Xerces and > can mean a great number of things. It basically means that it succeeded > in opening an input stream, but what it found there wasn't an XML > document. The "1:39" is a line and column number, and the fact that 39 > is roughly the length of a typical XML declaration might well be > suggestive. Perhaps the file contains an XML declaration and nothing else. > > Michael Kay > Saxonica > > -- Keep an Exacting Eye for Detail
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSLT 2.0 compability issu, Michael Kay | Thread | Re: [xsl] XSLT 2.0 compability issu, team wise |
Re: [xsl] XSLT 2.0 compability issu, Michael Kay | Date | Re: [xsl] XSLT 2.0 compability issu, team wise |
Month |