Gabor Hojtsy wrote: > MSXML (actually msxsl.exe is able to use MSXML from command line):
Don't expect MSXML to work with DocBook stylesheets -- they are too complicated for MSXML -- it crashes on them without any reasonable error message. > | $ ./msxsl.exe manual.xml xsl/html.xsl > | Error occurred while compiling stylesheet 'xsl/html.xsl'. > | Code: 0x80004005 > | The xsl:apply-imports instruction may only occur within an > | xsl:template instruction with a match attribute, and may not > | occur within an xsl:for-each instruction. > | Error occurred during compilation of included or imported > | stylesheet 'chunk-common.xsl'. > > Nor %instructions;, nor %result-elements; contain apply-templates, > as possible children, so MSXML is right here, and chunk-common.xsl > is not conforming to the XSLT DTD as presented in Appendix C of > the XSLT spec. XSLT spec doesn't say that apply-imports can't be used in template without match pattern. > Saxon: > > | $ ./saxon.exe manual.xml xsl/html.xsl > | Error on line 35 column 5 of file:/g:/phpcvs/phpdoc/manual.xml: > | Error reported by XML parser: Cannot read from > | file:/g:/phpcvs/phpdoc/entities/en/bookinfo.xml > | (\g:\phpcvs\phpdoc\entities\en\bookinfo.xml) > | Transformation failed: Run-time errors were reported > > Saxon errors are because the "what is the base for relative paths?" > question of saxon handled differently than jade/openjade. Saxon > would like to open the files relative to the entity file, and not > relative to the manual.xml file. Hartmut how you can handle this > in your tests with XSL[T] processors? Default parser in Saxon has this sort of bug, which hadn't been completely fixed up to now. You can use Saxon with other then default parser -- look at http://www.kosek.cz/xml/saxon/ how to change parser used by Saxon. > I also searched up XT, but it is quite old, and not updated > since 1999 as I can see. I have not downloaded xalan, as thought, > one of the programs above should work. :(( XT doesn't work with DocBook stylesheets, because it doesn't support full XSLT spec. > I would be very happy to see MSXML working, as it must beat in > spead any Java app on Windows, as it is native MS code. Though When you processing large documents with complex stylesheets internal optimizations of XSLT processor are more significant than language in which processor is written -- compare results of xsltproc and Saxon on bightml output. You can use xsltproc also under Windows http://www.fh-frankfurt.de/~igor/projects/libxml/index.html > this prog is not a solution for general phpdoc needs, it would > be enough for CHM related tasks, if I can get it working... It wouldn't, because MSXML doesn't support output to multiple files. Jirka -- ----------------------------------------------------------------- Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
