Oxygen XML Author plugin 13.2.0

Transforming Documents | 293• Ignorable ("ignorable") - Strips all ignorable whitespace text nodes from source documents before any furtherprocessing, regardless of any xsl:strip-space declarations in the stylesheet, or any xml:space attributesin 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.)The advanced options available only in Saxon PE / EE are:• 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.The advanced options available only in Saxon EE are:• 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 XML 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 XML 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.• Initializer class - Equivalent with the -init Saxon command line argument. The value is the name of a user-suppliedclass that implements the interface net.sf.saxon.lib.Initializer; this initializer will be called duringthe initialization process, and may be used to set any options required on the Configuration programmatically. It isparticularly useful for tasks such as registering extension functions, collations, or external object models, especiallyin Saxon-HE where the option cannot be set via a configuration file. Saxon only calls the initializer when runningfrom the command line, but the same code may be invoked to perform initialization when running user applicationcode.When creating a scenario that applies to an XML file, Oxygen XML Author plugin fills the XML URL field with thedefault variable ${currentFileURL}. This means the input for the transformation is taken from the currently edited file.You can modify this value to some other file path. This is the case when you are currently editing a section from a largedocument, but you want the transformation to be performed on the main document. You can specify in this case eithera full absolute path: file:/c:/project/docbook/test.xml or a path relative to one of the editor variables,for example or the current file directory: ${cfdu}/test.xml.When the scenario applies to XSL files, the field XSL URL initially contains ${currentFile} editor variable. Just likein the XML case, you can specify here the path to a master stylesheet. The path can be configured using the editorvariables or the custom editor variables.