24.08.2015 Views

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring the Application | 408in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD orschema as having element-only content.• None ("none") - default setting. No whitespaces are stripped before further processing. However, whitespacewill still be stripped if this is specified in the stylesheet using xsl:strip-space.• Optimization level ("-opt") - Set optimization level. The value is an integer in the range 0 (no optimization) to 10(full optimization); currently all values other than 0 result in full optimization but this is likely to change in the future.The default is full optimization; this feature allows optimization to be suppressed in cases where reducing compiletime is important, or where optimization gets in the way of debugging, or causes extension functions with side-effectsto behave unpredictably. (Note however, that even with no optimization, the lazy evaluation may still cause theevaluation order to be not as expected.)• Allow calls on extension functions ("-ext") - If checked, the stylesheet is allowed to call external Java functions.This does not affect calls on integrated extension functions, including Saxon and EXSLT extension functions. Thisoption is useful when loading an untrusted stylesheet, perhaps from a remote site using an http:// URL; it ensuresthat the stylesheet cannot call arbitrary Java methods and thereby gain privileged access to resources on your machine.• Validation of the source file ("-val") - Requests schema-based validation of the source file and of any files readusing the document() or similar functions. Validation is available only with Saxon-EE, and this flag automaticallyswitches on the -sa option. Available options:• Schema validation ("strict") - This mode requires an <strong>XML</strong> Schema and specifies that the source documentsshould be parsed with schema-validation enabled.• Lax schema validation ("lax") - This mode specifies if the source documents should be parsed withschema-validation enabled if an <strong>XML</strong> Schema is provided.• Disable schema validation - This specifies that the source documents should be parsed with schema-validationdisabled.• Validation errors in the results tree treated as warnings ("-outval") - Normally, if validation of result documentsis requested, a validation error is fatal. Enabling this option causes such validation failures to be treated as warnings.• Write comments for non-fatal validation errors of the result document - The validation messages are written(where possible) as a comment in the result document itself.Saxon HE/PE/EE AdvancedThe Saxon HE/PE/EE Advanced preferences panel is opened from menu Window > Preferences > <strong>Author</strong> > <strong>XML</strong>> XSLT/FO/XQuery > XSLT > Saxon > Saxon HE/PE/EE > Advanced.Figure 175: The Saxon HE/PE/EE XSLT Advanced Preferences PanelThere are some advanced XSLT options which can be configured for the Saxon 9.3.0.5 transformer (all three editions:Home Edition, Professional Edition, Enterprise Edition):• URI Resolver class name ("-r") - Allows the user to specify a custom implementation for the URI resolver usedby the XSLT Saxon 9.3.0.5 transformer (the -r option when run from the command line). The class name must befully specified and the corresponding jar or class extension must be configured from the dialog for configuring theXSLT extension for the particular transformation scenario.• Collection URI Resolver class name ("-cr") - Allows the user to specify a custom implementation for the CollectionURI resolver used by the XSLT Saxon 9.3.0.5 transformer (the -cr option when run from the command line). Theclass name must be fully specified and the corresponding jar or class extension must be configured from the dialogfor configuring the XSLT extension for the particular transformation scenario.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!