Oxygen XML Author plugin 13.2.0

• the time to compile the stylesheet in preparation for the transformation• the time to execute the stylesheetConfiguring the Application | 410• Start transformation in this mode - Although stylesheet execution usually begins in the empty mode, this defaultmay be changed by specifying another mode. Changing the start mode allows execution to jump directly to analternate group of templates.MSXML.NETThe MSXML.NET preferences panel is opened from menu Window > Preferences > Author > XML >XSLT/FO/XQuery > XSLT > MSXML.NET.The options of the MSXML.NET processor are the same as the ones available in the command line for the MSXML.NETprocessor:• Enable XInclude processing - If checked, XInclude references will be resolved when MSXML.NET is used astransformer in the XSLT transformation scenario.• Validate documents during parse phase - If checked and either the source or stylesheet document has a DTD orschema against which its content can be checked, validation is performed.• Do not resolve external definitions during parse phase - By default MSXML.NET resolves external definitionssuch as DTD external subsets or external entity references when parsing source XML document and stylesheetdocument. Using this option you can disable this behaviour. Note, that it may affect also the validation process forthe XML document.• Strip non-significant whitespaces - If checked, strips non-significant white space from the input XML documentduring the load phase. Enabling this option can lower memory usage and improve transformation performance while,in most cases, creating equivalent output.• Show time information - If checked, the relative speed of various transformation steps can be measured:• the time to load, parse, and build the input document• the time to load, parse, and build the stylesheet document• the time to compile the stylesheet in preparation for the transformation• the time to execute the stylesheet• Forces ASCII output encoding - There is a known problem with .NET 1.X XSLT processor(System.Xml.Xsl.XslTransform class): it doesn't support escaping of characters as XML character referenceswhen they cannot be represented in the output encoding. That means that when you output a character that cannotbe represented in output encoding, it will be outputted as '?'. Usually this happens when output encoding is set toASCII. With this option checked the output is forced to be ASCII encoded and all non-ASCII characters get escapedas XML character references (&#nnnn; form).• Allow multiple output documents - This option allows to create multiple result documents using theexsl:document extension element.• Use named URI resolver class - This option allows to specify a custom URI resolver class to resolve URI referencesin xsl:import and xsl:include instructions (during XSLT stylesheet loading phase) and in document()function (during XSL transformation phase).• Assembly file name for URI resolver class - The previous option specifies partially or fully qualified URI resolverclass name, e.g. Acme.Resolvers.CacheResolver. Such name requires additional assembly specificationusing this option or the next option, but fully qualified class name (which always includes an assembly specifier) isall-sufficient. See MSDN for more info about fully qualified class names. This option specifies a file name of theassembly, where the specified resolver class can be found.• Assembly GAC name for URI resolver class - This option specifies partially or fully qualified name of the assemblyin the global assembly cache (GAC), where the specified resolver class can be found. See MSDN for more infoabout partial assembly names. Also see the previous option.• List of extension object class names - This option allows to specify extension object classes, whose public methodsthen can be used as extension functions in an XSLT stylesheet. It is a comma-separated list of namespace-qualifiedextension object class names. Each class name must be bound to a namespace URI using prefixes as when providingXSLT parameters.• Use specified EXSLT assembly - MSXML.NET supports a rich library of the EXSLT and EXSLT.NET extensionfunctions embedded or in a plugged in EXSLT.NET library. EXSLT support is enabled by default and cannot be