Options

•	Sorting of attributes and elements in the Schema Tree View,

•	The processing of the internally generated XSL-FO document, which is required in order to enable the PDF Preview and the generation of PDF files in StyleVision.

In the Schema Tree, elements and attributes can be listed alphabetically in ascending order. To do this, check the respective check boxes in the Schema tab (screenshot below). By default, attributes are listed alphabetically and elements are listed in an order corresponding to the schema structure, as far as this is possible.

In the Project sidebar, when an XML file or XSD file is double-clicked, one of three actions is executed depending on the options set in the Project tab of the Options dialog (screenshot below): (i) Edit the file in XMLSpy; (ii) Create a new design based on the selected file; (iii) Ask the user which action to execute.

In the Default Encoding tab (screenshot below), you can set default encodings for the various outputs separately. The encoding specifies the codepoints sets for various character sets. The dropdown list of each combo box displays a list of encoding options. Select the encoding you require for each output type, and click OK. Every new SPS you create from this point on will set the respective output encodings as defined in this tab.

In the XSLT-for-HTML, the output encoding information is registered at the following locations:

•	In the encoding attribute of the stylesheet's xsl:output element:

<xsl:output version="1.0" encoding="UTF-8" indent="no" omit-xml-declaration="no" media-type="text/html" />

•	In the charset attribute of the content-type meta element in the HTML header:

In the XSLT-for-RTF, the output encoding information is registered in the encoding attribute of the stylesheet's xsl:output element:

•	<xsl:output version="1.0" encoding="ISO-8859-1" indent="no" method="text" omit-xml-declaration="yes" media-type="text/rtf" />

In the XSLT-for-PDF, the output encoding information is registered in the encoding attribute of the stylesheet's xsl:output element:

•	<xsl:output version="1.0" encoding="UTF-8" indent="no" omit-xml-declaration="no" media-type="text/html" />

Note: These settings are the default encodings, and will be used for new SPSs. You cannot change the encoding of the currently open SPS using this dialog. To change the encoding of the currently open SPS, use the File | Properties command.

Once the XSL-FO settings are correctly made, each time the PDF Preview tab is clicked, the following happens:

1.	An XSL-FO document is generated (behind the interface) by processing the Working XML File with the currently active SPS.

2.	The XSL-FO is then processed by an FO processor to generate the PDF that is displayed in the PDF Preview window.

In the XSL-FO tab, the following settings must be made in order for the PDF Preview to be enabled and for PDF files to be generated.

You can use any FO processor of your choice. All you have to do is enter the path to the processor's executable in this dialog. For details, see Setting up StyleVision.

Selecting the FOP 0.93 compliant option filters out those FOP properties that have not yet been implemented in the latest version of FOP. Selecting the Full XSL-FO standard option will not filter out any properties when the XSLT-for-FO is being generated.

Depending on your selection, the XSLT-for-FO will be created with or without the objects, properties, and values that are beyond the compliance level of FOP 0.93. You should be aware of the possible outcomes from this point in the processing. These are as follows:

•	If you have selected FOP compliance and use FOP as your processor, then the PDF generation should work fine.

•

If you have selected full usage of the XSL-FO standard and use FOP as your processor, then any formatting object or property in the FO document that is not supported by the current version of FOP will cause FOP to generate either a warning or an error. An error is fatal, and no PDF will be generated.

•	If you use a processor other than FOP, the success of the transformation will depend upon the compliance level of the processor.

For standard use, we recommend using FOP and selecting FOP 0.93 compliant in the Options dialog.

Note: The XSLT-for-FO that you generate with the File | Save Generated Files | Save Generated XSL-FO File command will be either in compliance with FOP 0.93 or with the full XSL-FO standard, depending on the selection you make for the XSL-FO Generation option in this dialog. Any error will only be reported when the FO document is processed by the FO processor.

Technical Note: StyleVision opens the executable of the FO processor using the path you enter in the FO Processor pane of the Options dialog. It sends the following arguments to the executable:

These arguments are as used in the FOP command: FOP -fo filename.fo -pdf fileame.pdf. You can use these arguments to invoke any FO processor, if the arguments suffice to make a successful call.

File | Properties, for information about changing the encoding of the currently active SPS document.

Setting up StyleVision, for a description of essential setup steps required to work with StyleVision.