The Options command opens a dialog (screenshot below) in which you can specify the encoding of the HTML output file.
In the Design tab (screenshot below), you can set the application-wide general options for designs.
The following options can be set:
|•||Maximum width (in pixels) of markup tags. Enter the positive integer that is the required number of pixels.|
|•||Grid size of layout containers in absolute length units. The specified lengths are the distances between two points on the respective grid axis.|
|•||Default additional width and height of Layout Boxes. These additional lengths are added to all layout boxes in order to provide the extra length that is often required to accommodate the bigger text renditions of print formats. These values can be specified as percentage values or as absolute length units.|
|•||The default behavior when a node-template is created at a location where the context node is not know. This option typically applies to User-Defined Templates in which the template has been created for items that cannot be placed in context in the schema source of the design. If a node is created within such a user-defined template, then the node can be created with (i) only its name, or (ii) with the full path to it from the schema root. You can set one of these options as the default behavior, or, alternatively, ask to be prompted each time this situation arises. The default selection for this option is Always Ask.|
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 Options tab. 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: (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:|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
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" />
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.
In the meta information of HTML output files, the line, 'Generated by StyleVision', will be generated by default. Purchased versions of the product provide an option to disable the generation of this line.
Network Proxy options
The Network Proxy section enables you to configure custom proxy settings. These settings affect how the application connects to the Internet (for XML validation purposes, for example). By default, the application uses the system's proxy settings, so you should not need to change the proxy settings in most cases. If necessary, however, you can set an alternative network proxy using the options below.
|Note:||The network proxy settings are shared among all Altova MissionKit applications. So, if you change the settings in one application, all MissionKit applications will be affected.|
Use system proxy settings
Uses the Internet Explorer (IE) settings configurable via the system proxy settings. It also queries the settings configured with netsh.exe winhttp.
Automatic proxy configuration
The following options are provided:
|•||Auto-detect settings: Looks up a WPAD script (http://wpad.LOCALDOMAIN/wpad.dat) via DHCP or DNS, and uses this script for proxy setup.|
|•||Script URL: Specify an HTTP URL to a proxy-auto-configuration (.pac) script that is to be used for proxy setup.|
|•||Reload: Resets and reloads the current auto-proxy-configuration. This action requires Windows 8 or newer, and may need up to 30s to take effect.|
Manual proxy configuration
Manually specify the fully qualified host name and port for the proxies of the respective protocols. A supported scheme may be included in the host name (for example: http://hostname). It is not required that the scheme is the same as the respective protocol if the proxy supports the scheme.
The following options are provided:
|•||Use this proxy for all protocols: Uses the host name and port of the HTTP Proxy for all protocols.|
|•||No Proxy for: A semi-colon (;) separated list of fully qualified host names, domain names, or IP addresses for hosts that should be used without a proxy. IP addresses may not be truncated and IPv6 addresses have to be enclosed by square brackets (for example: [2606:2800:220:1:248:1893:25c8:1946]). Domain names must start with a leading dot (for example: .example.com).|
|•||Do not use the proxy server for local addresses: If checked, adds <local> to the No Proxy for list. If this option is selected, then the following will not use the proxy: (i) 127.0.0.1, (ii) [::1], (iii) all host names not containing a dot character (.).|
Current proxy settings
Provides a verbose log of the proxy detection. It can be refreshed with the Refresh button to the right of the Test URL field (for example, when changing the test URL, or when the proxy settings have been changed).
|•||Test URL: A test URL can be used to see which proxy is used for that specific URL. No I/O is done with this URL. This field must not be empty if proxy-auto-configuration is used (either through Use system proxy settings or Authomatic proxy configuration).|
The options listed below are available for the conversion of SPS files to MobileTogether Design (MTD) files. (These conversions are done via the Export as MobileTogether Design File command.)
|•||Static text and paragraph-level text that contain inline formatting (for example a paragraph element that contains a bold or italic element) is by default converted into a single MTD label, where the text will have the formatting of the block-level text. You can however set an option to split this kind of text (block-level text with inline formatting) into multiple MTD labels, where each label has the formatting that corresponds to the original text fragment.|
|•||If the SPS has a condition with branches, then the conversion to MTD will, by default, convert all branches of the condition and will position them in sequence one below the other in the MTD document. You can optionally choose to suppress the conversion of the condition (and all its branches).|
On the Java tab, you can optionally enter the path to a Java VM (Virtual Machine) on your file system. Note that adding a custom Java VM path is not always necessary. By default, StyleVision attempts to detect the Java VM path automatically by reading (in this order) the Windows registry and the JAVA_HOME environment variable. The custom path added on this dialog box will take priority over any other Java VM path detected automatically.
You may need to add a custom Java VM path, for example, if you are using a Java virtual machine which does not have an installer and does not create registry entries (for example, Oracle's OpenJDK). You might also want to set this path if you need to override, for whatever reason, any Java VM path detected automatically by StyleVision.
Note the following:
|•||The Java VM path is shared between Altova desktop (not server) applications. Consequently, if you change it in one application, it will automatically apply to all other Altova applications.|
|•||The path must point to the jvm.dll file from the \bin\server or \bin\client directory, relative to the directory where the JDK was installed.|
|•||The StyleVision platform (32-bit, 64-bit) must be the same as that of the JDK.|
|•||After changing the Java VM path, you may need to restart StyleVision for the new settings to take effect.|
Changing the Java VM path affects the following areas:
|•||Java extension functions for XSLT/XPath|
© 2019 Altova GmbH