Oxygen XML Author plugin 13.2.0

Transforming Documents | 302Because msxsl.exe is only a wrapper, Microsoft Core XML Services (MSXML) must be installed on the computerotherwise you will get a corresponding warning. You can get the latest Microsoft XML parser from Microsoft web-site• MSXML .NET - MSXML .NET is available only on Windows NT4, Windows 2000 and Windows XP platforms. Itcan be used for transformation .Oxygen XML Author plugin performs XSLT transformations and validations using .NET Framework's XSLTimplementation (System.Xml.Xsl.XslTransform class) through the nxslt command line utility. The nxsltversion included in Oxygen XML Author plugin is 1.6.You should have the .NET Framework version 1.0 already installed on your system otherwise you will get thefollowing warning: MSXML.NET requires .NET Framework version 1.0 to be installed.Exit code: 128You can get the .NET Framework version 1.0 from the Microsoft website• .NET 1.0 - A transformer based on the System.Xml 1.0 library available in the .NET 1.0 and .NET 1.1 frameworksfrom Microsoft (http://msdn.microsoft.com/xml/). It is available only on Windows.You should have the .NET Framework version 1.0 or 1.1 already installed on your system otherwise you will getthe following warning: MSXML.NET requires .NET Framework version 1.0 to be installed.Exit code: 128You can get the .NET Framework version 1.0 from the Microsoft website• .NET 2.0 - A transformer based on the System.Xml 2.0 library available in the .NET 2.0 framework from Microsoft.It is available only on Windows.You should have the .NET Framework version 2.0 already installed on your system otherwise you will get thefollowing warning: MSXML.NET requires .NET Framework version 2.0 to be installed.Exit code: 128You can get the .NET Framework version 2.0 from the Microsoft websiteConfiguring Custom XSLT ProcessorsYou can configure other XSLT transformation engines than the ones which come with the Oxygen XML Author plugindistribution. Such an external engine can be used for XSLT transformations within Editor perspective, and is availablein the list of engines in the dialog for editing transformation scenariosThe output messages of a custom processor are displayed in an output view at the bottom of the application window. Ifan output message follows the format of an Oxygen XML Author plugin linked message then a click on the messagein the output view highlights the location of the message in an editor panel containing the file referred in the message.Configuring the XSLT Processor Extensions PathsThe Xalan and Saxon processors support the use of extension elements and extension functions. Unlike a literal resultelement, which the stylesheet simply transfers to the result tree, an extension element performs an action. The extensionis usually used because the XSLT stylesheet fails in providing adequate functions to the user for accomplishing a morecomplex task.Samples on how to use extensions can be found at:• for Xalan - http://xml.apache.org/xalan-j/extensions.html• for Saxon 6.5.5 - http://saxon.sourceforge.net/saxon6.5.5/extensions.html• for Saxon 9.3.0.5 - http://www.saxonica.com/documentation/extensibility/intro.xmlIn order to set an XSLT processor extension (a directory or a jar file), you have to use the Extensions button of thescenario edit dialog. The old way of setting an extension (using the parameter -Dcom.oxygenxml.additional.classpath)was deprecated and you should use the extension mechanism of the XSLT transformation scenario.