The Configure Scenario dialog is used to associate a scenario from the list of all scenarios with the edited document by selecting an entry from the list. The dialog is opened by pressing the Configure Transformation Scenario button on the Transformation toolbar of the document view. Once selected the scenario will be applied with only one click on the Apply Transformation button on the same toolbar. Pressing the Apply Transformation button before associating a scenario with the edited document will invoke first the Configure Scenario dialog and then apply the selected scenario.
Open the Configure Transformation dialog by selecting Ctrl+Shift+C) Complete the dialog as follows:
+ → (Specifies an input XML file to be used for the transformation. Please note that this URL is resolved through the catalog resolver. If the catalog does not have a mapping for the URL, then the editor will try to use the file directly.
The following buttons are shown immediately after the input field:
Opens a dialog allowing to introduce special <oXygen/> editor variables in the XSL URL field.
Opens a file browser dialog allowing to select a local file name for the XSL URL field.
Opens a file browser dialog allowing to select a remote file name for the XSL URL field.
Opens the file with the path specified in the XSL URL path in a the editor.
Specifies an input XSL file to be used for the transformation. Please note that this URL is resolved through the catalog resolver. If the catalog does not have a mapping for the URL, then the editor will try to use the file directly.
The above set of browsing buttons are available also for this input.
Use the stylesheet declared with an "xml-stylesheet" declaration instead of the stylesheet specified in the XSL URL field.
This combo box contains all the transformer engines available for applying the stylesheet. If you want to change the default selected engine just select other engine from the drop down list of the combo box.
Opens a dialog for specifying a URL for a header HTML file added at the beginning of the result of an HTML transformation and a URL for a footer HTML file added at the end of the HTML result.
Opens the dialog for adding XSLT stylesheets which are applied on the result of the main stylesheet specified in the XSL URL field.
Opens the dialog for configuring the XSLT/XQuery extension jars or classes which define extension functions called from the XSLT/XQuery transformation.
When creating a scenario that applies to an XML file, <oXygen/> fills the XML URL with the default variable "${currentFile}". This means the input for the transformation is taken from the currently edited file. You can modify this value to other file path. This is the case of currently editing a section from a large document, and you want the transformation to be performed on the main document, not the section. You can specify in this case either a full absolute path: file:/c:/project/docbook/test.xml or a path relative to one of the editor variables, like the current project file: ${pdu}/docbook/test.xml .
When the scenario applies to XSL files, the field XSL URL is containing ${currentFile}. Just like in the XML case, you can specify here the path to a master stylesheet. The path can be configured using the editor variables.
![]() | Note |
---|---|
If you are sharing the scenarios by saving them into the project file (see Transformation Scenario Sharing) it is recommended that the URL fields to have path values relative to the project editor variable ${pdu}. |
Enable or disable the use of FOP during the transformation.
The FO processor is applied to the result of applying the XSLT stylesheet.
The FO processor is applied directly to the current edited document.
The output format of the FO processing: PDF, PostScript or plain text.
The FO processor, which can be the built-in Apache FOP processor or an external processor.
At the end of the transformation it will be displayed a file browser dialog for specifying the path and name of the file which will store the transformation result.
The path of the file where it will be stored the transformation result. The path can include special <oXygen/> editor variables.
If this is checked <oXygen/> will open automatically the transformation result in a browser application specific for the type of that result (HTML/XHTML, PDF, text).
When Open in browser is selected this button can be selected to specify that <oXygen/> should open the file specified in the Save As text field.
When Open in browser is selected this button can be used to specify that <oXygen/> should not open the file specified in the Save As text field, it should open the file specified in the text field of the Other location radio button. The file path can include special <oXygen/> editor variables.
When checked the transformation result set in the Save As field is opened in a new editor panel in <oXygen/> with the appropriate built-in editor type: if the result is an XML file it is opened with the built-in XML editor, if it is an HTML file it is opened with the built-in HTML editor, etc.
It is enabled only when Open in browser is disabled and if this is checked <oXygen/> will display the transformation result in a built-in XHTML browser panel of the <oXygen/> window.
![]() | Important |
---|---|
When transforming very large documents you should be aware that enabling this feature will result in a very long transformation time. This drawback appears due to the Java XHTML browser implementation. In this situations if you wish to see the result of the transformation you should use an external browser. |
If this is checked <oXygen/> will display the transformation result in an XML viewer panel with syntax highlight specific for XML documents.
If this is checked <oXygen/> will display the transformation result in a SVG viewer panel by rendering the result as a SVG image.
If Show As XHTML is checked this text field specifies the path for resolving image paths contained in the transformation result.
The parameters of the XSLT stylesheet used in the transformation scenario are configured from the dialog available from the Parameters button:
The table presents all the parameters of the XSLT stylesheet and all imported and included stylesheets with their current values. If a parameter value was not edited then the table presents its default value. The bottom panel presents the default value of the parameter selected in the table and the system ID of the stylesheet that declares it.
For setting the value of a parameter declared in the stylesheet in a namespace, for example:
<xsl:param name="p:param" xmlns:p="namespace">default</xsl:param>
use the following expression in the Name column of the Parameters dialog:
{namespace}param
Use the following procedure to create a scenario.