Oxygen XML Author plugin 13.2.0

Custom Editor VariablesAn editor variable can be created by the user and included in any user defined expression where a built-in editor variableis also allowed. For example a custom editor variable may be necessary for configuring the command line of an externaltool, the working directory of a custom validator, the command line of a custom XSLT engine, a custom FO processor,etc. All the custom editor variables are listed together with the built-in editor variables, for example when editing theworking folder or the command line of a , the working directory, etc.Creating a custom editor variable is very simple: just specify the name that will be used in user defined expressions, thevalue that will replace the variable name at runtime and a textual description for the user of that variable.The custom editor variables are configured in Preferences.Configuring XML CatalogsIn the XML sample file for SDF you did not use a xsi:schemaLocation attribute, but instead you let the editor use theschema from the association. However there are cases in which you must refer for instance the location of a schema filefrom a remote web location and an Internet connection may not be available. In such cases an XML catalog may beused to map the web location to a local file system entry. The following procedure presents an example of using anXML catalogs, by modifying our sdf.xsd XML Schema file from the Example Files Listings.1. Create a catalog file that will help the parser locate the schema for validating the XML document. The file must mapthe location of the schema to a local version of the schema.Create a new XML file called catalog.xml and save it into the {oXygen_installation_directory}/ frameworks / sdf directory. The content of the file should be:2. Add catalog files to your Document Type Association using the Catalogs tab from the Document Type dialog.Author Developer Guide | 200To test the catalog settings, restart Oxygen XML Author plugin and try to validate a new sample Simple DocumentationFramework document. There should be no errors.The sdf.xsd schema that validates the document refers the other file abs.xsd through an importelement:The schemaLocation attribute references the abs.xsd file:xsi:schemaLocation="http://www.oxygenxml.com/sample/documentation/abstractshttp://www.oxygenxml.com/SDF/abs.xsd"/>The catalog mapping is:http://www.oxygenxml.com/SDF/abs.xsd -> schema/abs.xsd