Configuration within the XML/XSL environment

HTML TIDY

For converting HTML to XHTML and being able to process with
XML tools ZMS falls back on HTML TIDY. The installation path of TIDY is entered in the central configuration menu.

Example:

  C:\Programme\tidy\tidy.exe

XSLT Processor

The configuration of the Java XSLT processor is operated through the central configuration menu of ZMS. For that {in.xml}, {out.xml} and {trans.xsl} must be used as placeholders in the prompt for the XML in-/output and the XSL transformation.

Example: SAXON

  java -jar $SAXON_HOME/saxon.jar {in.xml} 
    {trans.xsl} > {out.xml}

Example: XALAN

  java -cp $XALAN_HOME/bin/xalan.jar; 
    $XALAN_HOME/bin/xercesImpl.jar; 
    $XALAN_HOME/bin/xml-apis.jar 
    org.apache.xalan.xslt.Process -in {in.xml} 
    -xsl {trans.xsl} -out {out.xml}

PATH environment variable

The operating system has to know the path designation where the Java run-time environment is located; JRE is needed for running the Java-based XSL processors.
Note: Under Windows98 the environment variable PATH is entered into the autoexec.bat, e.g.:
SET PATH=C:\PROGRA~1\JAVA\J2RE14~1.1_0\BIN
For this the path must be specified in an 8+3-digit DOS syntax; you get the corresponding abbreviations by following the pathname in the DOS window with the command dir.