Gabor Hojtsy wrote: > 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?
i should have mentioned: right now i run configure with absolute path, using $PWD/configure or `pwd`/configure, that will generate absolute pathes for the auto generated entities i guess the only real solution is to have the entities file generated in two versions and copy the right file to chapters.ent before starting either jade or an xslt processor :( PS: i forgot to mention Xalan, i tried the C++ version, but it is slow compared to saxon (for bightml) and gnome libxslt's xsltproc (for both big and chunked html) -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77 Wir stellen für Sie aus auf der CeBIT 2002 und freuen uns in Halle 6 auf Ihren Besuch am Stand H 18
