In StyleVision, XSLT stylesheets and output files can be generated using the File | Save Generated Files command or StyleVision Server. Alternatively, if you wish only to validate or transform XML using XSLT, you can do this directly with RaptorXML(+XBRL) Server.
The following files can be generated from StyleVision:
•XSLT stylesheets based on the SPS design. Separate XSLT stylesheets are generated for HTML, Text, and RTF output.
•Output files, generated by processing the Working XML File assigned in the SPS with the XSLT stylesheets generated from the SPS.
The markup for the output is contained in the SPS. The data for the output is contained in the XML document or DB. It is the XSLT stylesheet that brings markup and data together in the output. Both the XSLT stylesheets as well as the actual output can be previewed in StyleVision in the Output Views.
|Note:||If you wish to add a namespace to an SPS or to an XSLT stylesheet being generated from an SPS, the namespace must be added to the top-level schema element of the XML Schema on which the SPS is based.|
Altova website: XML reporting
Given below are important points to note about the generated documents:
•HTML output and stylesheets: (1) The formatting and layout of the generated HTML document will be identical to the HTML Preview of StyleVision and near-identical to the Authentic View of the XML document. (2) Data-input devices (text input fields, check boxes, etc) in the HTML file do not allow input. These data-input devices are intended for XML data input in Authentic View and, though they are translated unchanged into the graphical HTML equivalents, they cannot be used for data-entry in the HTML document.
Altova website: XML to HTML
•RTF output and stylesheets: (1) The RTF design requires specifications for paged media. You can provide these specifications (cover page design, left/right pagination, etc) in the Properties sidebar and the Design Tree sidebar. (2) If data-input devices have been used in the SPS, then, where possible, these are rendered as graphics on the RTF page. When a data-entry device cannot easily be simulated as a graphic (e.g. check boxes), a substitute presentation is used.
•Text output and stylesheets: Since the plain text format does not use formatting, style properties in the design are not passed to the text output.
RTF output is generated from your XML file in a single step by processing the XML document with the XSLT-for-RTF file generated from the SPS. The properties of the RTF output are defined in the SPS, and you can preview the output in the RTF Preview window. To obtain the RTF file, you must generate it (using File | Save Generated Files or StyleVision Server).
|Note:||If there is a problem with an embedded preview, StyleVision will attempt to open the preview document in an external application (usually MS Word or Adobe Reader). An error message about the embedded preview will appear in StyleVision. If the preview document is opened in an external application, you will need to close the external application before regenerating the temporary output document, otherwise you will get an error message saying the file is being used by another process. You should also close the external application before closing the SPS design, otherwise StyleVision will not be able to close the temporary output document due to the file lock placed on the document by the external application.|
Since Text output generates plain text, note the following points:
•Style and page layout properties that are defined in the design will not be applied to the Text output.
•In order to generate Text output, the XSLT version selected for the SPS must be XSLT 2.0 or XSLT 3.0.