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:01:34 +0800 |
Hi Michael, It seems I am now very close to resovle the issue, as it hits the PSMI transform stage. Having tweaked a couple of <xsl:element> <xsl:attribute> issues, I now end up here: [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. Any thoughts would be much appreciated. Ray 2012/6/19, Michael Kay <mike@xxxxxxxxxxxx>: > >I have a favor to ask what kind of a running sample would be desirable > for you to spot the error. > > A stylesheet and source document, as short as you can make them, which > have no external dependencies, so anyone can try running them. > > > I have tried replacing the line <xsl:variable > name="topicrefClass"><xsl:value-of select="@class"/></xsl:variable> with > this line <xsl:variable name="topicrefClass" select="string(@class)"/> , > but made no difference. > > I should have made it clear that this observation about your code was > just an inefficiency I noticed, it has nothing to do with the problem > you are experiencing. > > 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, Michael Kay |
Re: [xsl] XSLT 2.0 compability issu, Michael Kay | Date | [xsl] How to do this unique groupin, Amit Agarwal |
Month |