The Properties command pops up the Properties dialog (screenshot below shows the dialog in the Enterprise Edition), in which you can set various properties for the active SPS.
The following properties can be set in the Output tab:
•Output Encoding: In the Output Encoding pane you can select the encoding of your output documents. Changing the encoding in this dialog changes the encoding for the currently active SPS. You can also specify the application-wide for all SPS documents in the Encoding tab of the Options dialog.
•HTML output mode: You can select whether an entire HTML document or only the child elements of the HTML body element are output. The child elements are output parallel to each other—that is, on the same level—and will contain all descendants recursively. As a result, the output documents can be fragments of HTML code..
•HTML output mode (DOCTYPE): You can select whether an HTML5, HTML 4.01 Transitional document, or XHTML 1.0 Transitional document is generated for the HTML output. This setting can be changed at any time while creating or editing the SPS document.
•Internet Explorer Compatibility and CSS support: CSS support in versions of Internet Explorer (IE) prior to IE 6 was incomplete and in some respects incorrectly interpreted. CSS support was enhanced and corrected in IE 6, and further improved and extended in IE 7, IE 9, and higher.
In an SPS, you can select the desired compatibility mode in the Properties dialog (screenshot above). You can select either IE 5, IE 7, or IE 9. (Note that for IE 9 compatibility to apply, IE 9 or higher must be installed.) The specified level of IE support is immediately available in HTML Preview. Note that new SPS documents are created with IE7 compatibility selected. SPS documents created in earlier versions of Altova StyleVision can be re-saved in the required Compatibility Mode (selected in the Properties dialog).
In this tab (screenshot below shows the dialog in the Enterprise Edition), you can specify which XSD validator to use for XML validation and which XSLT version to use in the SPS.
StyleVision has both an XSD 1.0 validator and an XSD 1.1 validator. You can choose from among the following options:
•Use the XSD 1.1 validator if the XSD document's /xs:schema/@vc:minVersion attribute is set to 1.1; otherwise use the XSD 1.0 validator.
•Always use the XSD 1.1 validator.
•Alawys use the XSD 1.0 validator.
Select the XSLT version for the active document in this tab. Checking the option about the xsl:import-schema statement causes the xsl:import-schema element of the XSLT 2.0 and 3.0 specifications to be included in the XSLT document generated by StyleVision. It is recommended that you select this option in order for datatypes to be read from the schema in the event that there is no xsi:schemaLocation attribute in the XML document.
Default paths for various files created by the SPS file and for paths saved in the SPS file are specified in the settings of this tab (screenshot below shows the dialog in the Enterprise Edition).
The following defaults are set in the Paths tab:
•Whether preview files are created in the directory of the SPS file or the Working XML File of the main schema source.
•Where additionally generated files (image files, barcode image files, chart image files, etc) are created.
•Whether file paths in the SPS are relative only when the target directory is in the directory tree of the SPS file, or relative even when the target directory is outside the directory tree of the SPS file.