Procedure:
Enter the name of the XML document to be transformed in the field named XML Input File.
Choose one of the transformations in the combobox named Transformation. (See the section called “Specifying a transformation” to learn how to specify a new one).
Enter the name of the output file in the field named Name.
If the Directory toggle is checked, enter the name of the directory that will contain the output file. The basename of the output file will be the basename of the input file with the extension specified for the chosen transformation.
Example: the input file is
C:\docs\src\mydoc.xml; the transformation is "DocBook to HTML (one page)"; the Directory toggle is checked and the output directory isC:\docs\out; the output file name will beC:\docs\out\mydoc.html.Click on .
Once the conversion has been started, it may be canceled by clicking on the same button now renamed . The conversion cannot be canceled in the middle of a transformation step (example of transformation step: compiling the XSLT stylesheet), so you may have to wait a few seconds until the current transformation step is finished.
If canceling the current transformation takes a long time, it is probably because a software component loops forever (this sometimes happens with FOP). In such case, after 30 seconds, XSL Utility displays the following dialog box which may be used to abort the current conversion.
After aborting a conversion, it is highly recommended to quit XSL Utility as the state of this application may now be unstable.
Once all the fields of the main window have been filled, subsequent conversions may be initiated by simply dragging and dropping an XML file anywhere inside XSL Utility expect inside text fields.
Notes about the integrated console:
The console can be cleared by clicking on the small button with a red cross icon located between the scroll bars.
A message displayed by the console generally contains the time spent executing the corresponding transformation step. If you are interested by this kind of performance info, do not forget to run the same conversion several times because the Java™ HotSpot™ VM optimizes more and more the code each time it is executed.