This tutorial is meant to introduce the XSLT debugger view in Oxygen. It is a supplement to the XSLT Introduction tutorial that covers the mechanics of using XSL files to transform XML files into plain text, and into XHTML. This tutorial is important for using the example files in this and other XSLT tutorials.
- Open
Hamlet XML (ham.xml) - Open XSLT (djb_transformations_transform-first.xsl)
- Switch to the XSLT debugger
- Select the XSLT engine (accept the Saxon-HE default)
- Verify that you’ve chosen the correct XML and XSLT files
- (Optional: Specify an output filename to save output)
- Run the transformation straight through (click on blue arrow)
- Examine the output as text
This tutorial is meant to introduce you to the XSLT debugger view in Oxygen. For this tutorial, you should have <oXygen> downloaded. If you have not set it up already, please visit the tutorial setup page. These slides will cover the mechanics of using XSL files to transform XML files into plain text, and into XHTML.
Open the two files linked on the slide and follow the instructions to set up the XSLT debugger view. Once open, follow the instructions to transform ham.xml into a text file.
Pay particular attention to the comments in djb_transformationss_transform-first.xsl, they can help you understand what gets processed from ham.xml and what is ignored.
- Open
Hamlet XML (ham.xml) - Open XSLT (djb_transformations_transform-second.xsl)
- Switch to the XSLT debugger
- Select the XSLT engine (accept the Saxon-HE default)
Check the XHTML box - Verify that you’ve chosen the correct XML and XSLT files
- (Optional: Specify an output filename to save output)
- Run the transformation straight through (click on blue arrow)
- Examine the output
as XHTML and text
Keep ham.xml open and download the second XSLT stylesheet. Once open, follow the instructions to transform ham.xml into XHTML. The debugger view allows for you to preview XHTML pages in Oxygen, but you can set a location for your output file, then open that file in a browser (or upload it to your server).
Again, the comments (on djb_transformationss_transform-second.xsl) are helpful to understand which elements are processed from ham.xml and which are ignored based on the stylesheet.
- Click on the wrench with the red triangle or type Ctrl-Shift-c (Cmd-Shift-c on Mac)
- Scenario type is
XML transformation with XSLT - Save as
project scenario - Create a
new scenario - XSLT tab
- use the default of
${currentFileURL} - browse to your XSLT file
- use Saxon-HE
- use the default of
- Output tab
- Browse to wherever you want to save the output
- Check preferences (suggested: “Open in browser” and either “Open in Editor” or one of the “Show As” options)
To configure a transformation scenario, follow the instructions included here. You may want to do this when you have a project that will reuse an XSLT file for multiple XML files, or if working in the XSLT debugger view is too cramped for you.
- Install command-line saxon processor and add to path
- Save XML and XSLT to the same directory
- Convenient for one-off projects
- For reuse of XSLT, save it to a library directory, but you then need to specify the path
- Syntax
- Create an alias or batch file
- Not required, but strongly recommended for convenience
- Set the name
saxon to, e.g.,java -jar c:\bin\saxon_9.2\saxon9he.jar
- saxon -o outputfilename xmlfilename xsltfilename
- saxon -o sample.html input.xml transform-input.xsl
- Other command-line switches are available
- Create an alias or batch file
Follow the instructions on this slide to transform XML to XHTML from the command line. If you are familiar with using the command line, we recommend using this resource: Running XSLT From the Command Line.
-
This tutorial is complete, please see links below to continue:
- Proceed to next tutorial in Transformation and Publication Primer
- Return to Transformation and Publication Primer
- Return to main tutorial page