Volker Bernhard Duetsch wrote:
>>How do you set the CLASSPATH and PATH and how do you start the docbook
>>processing? How does your commandline look like?
>>
>>I can't see xalan in your structure.
>>
>>BTW: I recommend using Apache ANT as buildtool; this prevents you from
>>writing the driver code twice for Windows and Linux.
>>
>>Regards,
>>Gisbert Amm
>
>
> Hello Gisbert,
>
> Pathes look as following:
>
> classpath=xalan.jar;c:\buch\binaries;c:\buch\binaries\lib;
>
> LOCALCLASSPATH=build/fop.jar;buch/binaries\xml-apis.jar;buch/binaries\xercesImpl-2.2.1.jar;buch/binaries\xalan-2.4.1.jar
>
> Defined in Systemsteuerung/System/Erweitert/Umgebungsvariablen.
> xalan is located in binaries.
>
> Processing started with:
> C:\buch>java org.apache.xalan.xslt.Process -IN test.xml -XSL
> c:\buch\docbook\xsl\docbook_1.65.1\html
> \docbook.xsl -OUT t.html
Just one short note here: It's way better for you setting up a
customization layer and not invoking the DocBook XSL directly. See
http://www.sagehill.net/docbookxsl/CustomMethods.html#CustomizationLayer
It may only seem as another piece of work to be done at the moment but
it will pay off in many ways soon.
> The result looks like:
> SystemId Unknown; Line -1; Column -1; XSLT-Fehler
> (javax.xml.transform.TransformerConfigurationExcep
> tion): javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerException: IO-Ausnah
> me bei Stylesheet-Datei: ../VERSION
Xalan does find the docbook.xsl and then tries to execute the first
include statement there (<xsl:include href="../VERSION"/>). Then it
cannot find the file "../VERSION" although it's existing for sure.
Conclusion: Xalan does not know how to map the URIs to real paths on
your system.
How does the header of your test.xml look like?
You probably better should set up a XML catalog first an not mess around
with filesystem paths at the commandline. See
http://www.sagehill.net/docbookxsl/Catalogs.html
Since your environment is German, I suppose you are speaking German. If
so, there's another piece of reading for you, giving you some more
insights into DocBook processing to understand what's actually going on.
There's also an implementation of an ANT buildfile you can start with:
http://www.stefan-rinke.de/articles/publish/
Regards,
Gisbert Amm