Once <oXygen/> is installed you can use the Preferences dialog accessed from
-> to customize <oXygen/> for your requirements and network environment.A restricted version of the Preferences dialog is available at any time in editors of the <oXygen/> plugin by right-clicking in the editor panel and selecting Preferences:
This panel presents the data of the license key which enables the <oXygen/> plugin: registration name, category and number of purchased licenses, encrypted signature of the license key. Clicking on the Register button opens the <oXygen/> XML Editor License dialog that allows you to insert a new license key:
The path to a web browser executable to be used to open XSLT or PDF transformation results.
Use these options to configure the visual aspect, formatting parameters, and behaviour of the content assistant. The same options panel is available in the restricted version of the Preferences dialog.
Use this option to set the background color of the editor.
Use this option to set the background color for the content completion window.
Use this option to set the foreground color for the content completion window.
Use this option to set the background color for the window containing documentation for the content completion elements.
Use this option to set the foreground color for the window containing documentation for the content completion elements.
Use this option to select the font family and size used to display text in the editor.
This option will do a soft wrap of long lines, that is automatically wrap lines in edited documents. When this option is checked line folding will be disabled.
This option enables highlight for the tag matching the one on which the caret is situated.
If checked, it enables folding when a new editor is opened.
If "Enable folding when opening a new editor" is checked, you can specify the minimum number of lines for folding. If you modify this value, you'll notice the changes when you open/reopen the editor.
The editor tries to detect the indent settings of the opened XML document. In this way you can correctly format (pretty-print) files that were created with different settings, without changing your options. More than that you can activate the advanced option for detecting the maximum line width to be used for formatting and hard wrap. These features were designed to minimize the differences created by the pretty print operation when working with a versioning system, like CVS for example.
When checked enables 'Indent with tabs' to sets the indent to a tab unit. When unchecked, 'Indent with tabs' is disabled and the indent will measure as many spaces as defined by the 'Indent size' option.
Sets the number of spaces or the tab size that will equal a single indent. The Indent can be spaces or a tab, select the preference using the Indent With Tabs option. If set to 4 one tab will equal 4 white spaces or 1 tab with size of 4 characters depending on which option was set in the Indent With Tabs option.
Indent paste text corresponding to the indent settings set by the user. This is useful for keeping the indent style of text copied from other document.
This feature saves time when writing a reach text XML document. You can set a limit for the length of the lines in your document. When this limit is exceeded the editor will insert a new line before the word that breaks the limit, and indent the next line. This will minimize the need of reformatting the document.
If checked, it inserts a new indented line between start and end tag.
If checked, it detects the line width automatically when the document is opened.
Defines the point at which the "Format and Indent" (Pretty-Print) function will perform hard line wrapping. So if set to 100 Pretty-Print will wrap lines at the 100th space inclusive of white spaces, tags and elements.
When checked, the Format and indent the document on open operation will format and indent the document before opening it in the editor panel.
When checked the Format and Indent operation will preserve all empty lines found in the document on which the pretty-print operation os applied.
When checked the Format and Indent operation will output empty elements with a separate closing tag, ex. <a atr1="v1"></a>. When not checked the same operation will represent an empty element in a more compact form: <a atr1="v1"/>
When checked the Format and Indent operation will add a space before the closing slash of an empty element, for instance an empty br will appear as <br />.
When checked the Format and Indent operation will sort the attributes of an element alphabetically. When not checked the same operation will leave them in the same order as before applying the operation.
If checked, the "Format and Indent" (Pretty-Print) function will break the line before the attribute's name.
If checked, the "Format and Indent" (Pretty-Print) function will preserve the line breaks found in attributes. When this option is checked, Break long lines option will be disabled.
If checked, the "Format and Indent" (Pretty-Print) function will preserve text nodes as they are without removing or adding any whitespace.
If checked, the "Format and Indent" (Pretty-Print) function will break long attributes.
This list contains simplified XPath expressions for the names of the elements for which the contained white spaces like blanks, tabs and newlines are preserved by the Format and Indent operation exactly as before applying the operation. The allowed XPath expressions are of one of the form:
The namespace prefixes like xs in the previous example are treated as part of the element name without taking into account its binding to a namespace.
This list contains the names of the elements for which contiguous white spaces like blanks, tabs and newlines are merged by the Format and Indent operation into one blank.
If checked, automatic tags indentation while editing will take place for all elements including the ones that are excluded from Pretty Print (default behaviour). When unchecked, indentation while editing will not take place in elements that have the 'xml:space' attribute set on 'preserve' or are in the list of Preserve Space Elements.
If checked, the class content is indented during a "Format and Indent" (Pretty-Print) operation.
If checked, the class body (including the curly brackets) are placed on a new line after a Pretty-Print operation.
If checked, an empty line is added between two classes after a Pretty-Print operation is performed.
If selected the <oXygen/> plugin will perform a well-formed check every time the user saves a document.
Save all opened files before validating or transforming an XML document. In this way the dependencies are resolved, for example when modifying both the XML document and its XML Schema.
Code templates are small document fragments that can be reused in other
editing sessions. We have defined a large set of ready-to use templates for
XSL and XML Schema stored in a file named
code_templates.xml
located in the
<oXygen/> Preferences folder (folder Application Data\com.oxygenxml
on Windows /
.com.oxygenxml
on Linux of the
user home directory). So you can even share the templates from this file
with your colleagues using the import function. To obtain the template list
you have use the Content Completion on request shortcut key (usually CTRL-SPACE).
Define a new code template.
Edit the selected code template.
Delete the selected code template.
Import a file with code templates.
Export a file with code templates.
When no schema is specified in the edited document, <oXygen/> will try to use one of the default association rules set. It will try to use the association rules in the order presented in the Editor/Default Schema Association pane.
Specifies the namespace of the root element from the association rules set (any by default).
Specifies the local name of the root element (any by default).
Specifies the name of the file (any by default).
Specifies the type of schema to be used in the association rules for the document.
Specifies the location from where to load the schema to be
used in the current association rule. The macro ${frameworks}
can be used and it will be expanded to the path of the
subdirectory frameworks
of the
<oXygen/> installation directory.
Opens a new dialog allowing you to specify a new association rule.
Opens a new dialog allowing you to edit an existing association rule.
Deletes one of the existing association rule.
Moves the selected association rule one level up (the order is important because the first schema mapping in the list that can be associated with the document will be associated.
Moves the selected association rule one level down.
The Content Completion feature enables inline syntax lookup and Auto Completion of mark-up elements and attributes to streamline mark-up and reduce errors while editing.
These settings define the operating mode of the content assistant.
This option enables Content Completion feature. When unchecked, all Content Completion features are disabled.
When it is checked the search in the content completion window when you type a character is case sensitive ('a' and 'A' are different characters).
When inserting elements from the Content Completion assistant, both start and end tags are inserted.
When checked, the end tag of the inserted element will be automatically added only if it is not already present in the document.
If the Use Content Completion option is not checked and if this option is checked, <oXygen/> will close the last opened tag when </ is typed.
When checked, <oXygen/> will set the cursor automatically between tags. Even if the auto-inserted elements have attributes that are not required, the position of cursor can be forced between tags.
When checked, <oXygen/> will display a list with all the internal and external entities declared in the current document when the user types the start character of an entity reference (i.e. &).
When checked, <oXygen/> will insert automatically the required elements from the DTD or XML Schema.
When checked, <oXygen/> will insert automatically the optional elements from the DTD or XML Schema.
When checked, <oXygen/> will insert automatically the first Choice particle from the DTD or XML Schema.
When checked, <oXygen/> will insert automatically the required attributes from the DTD or XML Schema for an element inserted with the help of the Content Completion assistant.
When checked, <oXygen/> will insert automatically any FIXED attributes from the DTD or XML Schema for an element inserted with the help of the Content Completion assistant.
When checked, <oXygen/> will display the annotations that are present in the used schema for the current element, attribute or attribute value.
If checked, it shows the annotations of elements and attributes as tooltips.
When checked, <oXygen/> will use all DTD comments as annotation.
When checked, <oXygen/> will remember the last inserted items from the Content Completion window. The number of items to be remembered is limited by Maximum number of recent items shown combo box. These most frequently used items are displayed on the top of Content Completion window and their icon is decorated with a small red square.
When checked, <oXygen/> will display a list with all attributes values learned from the current document.
When checked, <oXygen/> will automatically learn the document structure when the document is opened.
These settings define what elements are suggested by the content assistant in addition to the XSL ones.
The Content Completion will offer only the XSL information.
Includes XHTML Transitional elements as substitutes for xsl:element.
Includes Formating Objects elements as substitutes for xsl:element.
Includes elements from a DTD file, a XML Schema file or a RNG Schema file specified from a URL as substitutes for xsl:element.
Disables and enables content completion in XPath expressions entered in the XSL attributes match, select and test and also in the XPath toolbar.
Options are available to allow the user to include XPath functions, XSLT functions or axes in the content completion suggestion list.
If operation is slow for very large schemas disabling the schema diagram view will improve the speed of navigation through the edited schema.
If this option is disabled the schema diagram for XML Schemas will not be generated and displayed.
If this option is disabled the schema diagram for Relax NG schemas will not be generated and displayed.
When checked, the spell checker is activated. Spell errors will be highlighted as you type.
When checked, a spell check action will be performed on entire document, highlighting all encountered errors.
On large documents, spell checking the entire content may take a lot of time.
The dictionary combo allows you to choose the dictionary you need.
These options allow the user to specify if the spell checker will be enabled inside Comments, Attribute values, Text and CDATA sections.
When checked, operations ignore capitalization errors.
When checked, operations do not check words containing case mixing (e.g. "SpellChecker").
When checked, the Spell Checker does not check words containing digits (e.g. "b2b").
When checked, the Spell Checker does not signal two successive identical words as an error.
When checked, ignores words looking like URL or file names (e.g. "www.oxygenxml.com" or "c:\boot.ini") .
When checked, punctuation checking is enabled: misplaced white space and wrong sequences, like a dot following a comma, are detected.
Enables the "Replace Always" feature.
When checked, all words formed by concatenating two legal words with an hyphen are accepted. If the language allows it, two words concatenated without hyphen are also accepted.
When checked, a word formed by concatenating a registered prefix and a legal word is accepted. For example if "mini-" is a registered prefix, accepts "mini-computer".
When checked, accepts any word ending with registered file extensions (e.g. "myfile.txt", "index.html" etc.).
This option indicates the type of spell checker accuracy, which may be: "Favour speed over quality", "Normal" and "Favour quality over speed".
Validation of edited document is executed as the document is modified by editing in <oXygen/>.
The period of keyboard inactivity which starts a new validation (in seconds).
If there are many validation errors the process of marking them in the document is long. You should limit the maximum number of reported errors with this setting to keep the time for error marking short
The name of the custom validation tool displayed in the External Validation toolbar
The path to the executable file of the external validation tool. The following macros can be used:
The path to user home directory
Project directory
Oxygen installation directory
The working directory of the external validation tool. The following macros can be used:
The path to user home directory
Project directory
Oxygen installation directory
The editors which can perform validation with the external tool.
Command line arguments used to validate the current edited file against different types of schema (W3C XML Schema, Relax NG full syntax, Relax NG compact syntax, Namespace Routing Language, Schematron, DTD, other schema type). The arguments can include any custom switch (like -rng) and the macros:
The path of the currently edited file
Path of current file (URL)
The path of detected schema file
The path of detected schema file (URL)
Choose one of the available validation profiles: CSS 1, CSS 2, CSS 2.1, CSS 3, SVG, SVG Basic, SVG Tiny, Mobile, TV Profile, ATSC TV Profile
Choose one of the available mediums: all, aural, braille, embossed, handheld, print, projection, screen
Set the minimum severity level for reported validation warnings. It is one of: all, normal, most important, no warnings.
When using catalogs it is sometimes useful to see what catalog files are parsed, if they are valid or not, and what identifiers are resolved by the catalogs. The Verbosity option is used to control the output of such messages. By default it is not selected.
If the Use default catalog option is checked the first XML catalog which <oXygen/> will use to resolve system IDs at document validation and URI references at document transformation will be a default built-in catalog which maps such references to the built-in local copies of the local DocBook and TEI frameworks and the schemas for XHTML, SVG and JSP documents.
The Prefer option is used to specify if <oXygen/> will try to resolve first the PUBLIC or SYSTEM reference using the specified XML catalogs. If a PUBLIC reference is not mapped in any of the catalogs then a SYSTEM reference is looked up.
When you add/delete an XML catalog to/from the list you must restart the application so that the changes take effect.
Limit the number of errors reported at validation or well-formed check. Use this option when the total number of errors is big and the time of displaying is too large.
http://apache.org/xml/features/validation/schema - This option sets the 'schema' feature to true.
http://apache.org/xml/features/validation/schema-full-checking - This option sets the 'schema-full-checking' feature to true.
http://apache.org/xml/features/validation/honour-all-schema-location - This option sets the 'honour-all-schema-location' feature to true. This means all the schemas that are imported for a specific namespace are used to compose the validation model. If this is false, only the first schema import is taken into account.
This option forces validation against a referred schema (XML Schema, Relax NG schema, Schematron schema) even if the document includes also a DTD declaration. It is useful when the DTD declaration is used to declare entities and the schema reference is used for validation.
Enable XInclude processing - if checked the XInclude support in <oXygen/> is turned on.
[Xerces XML Parser documentation:] According to the specification for XInclude, processors must add an xml:base attribute to elements included from locations with a different base URI. Without these attributes, the resulting infoset information would be incorrect.
Unfortunately, these attributes make XInclude processing not transparent to Schema validation.
One solution to this is to modify your schema to allow xml:base attributes to appear on elements that might be included from different base URIs.
If the addition of xml:base and/or xml:lang is undesired by your application, you can disable base URI fix-up.
[Xerces XML Parser documentation:]The processor will preserve language information on a top-level included element by adding an xml:lang attribute if its include parent has a different [language] property.
If the addition of xml:lang is undesired by your application, you can disable the Language fix-up.
Checks the ID/IDREF matches when the Relax NG document is validated.
Checks the Relax NG to be feasibly valid when this document is validated.
1.0 - Allows XSLT 1.0 expressions for Schematron assertion tests.
2.0 - Allows XSLT 2.0 expressions for Schematron assertion tests.
2.0 - Allows XSLT 2.0 expressions for Schematron assertion tests.
If you want to use an XSLT transformer different than the ones that ship with <oXygen/> namely Apache Xalan and Saxon all you have to do is to specify the name of the transformer's factory class which <oXygen/> will set as the value of the Java property "javax.xml.transform.TransformerFactory". To perform an XSLT transformation with Saxon 7 for instance you have to place the Saxon 7 jar file in the <oXygen/> libraries directory (the lib subdirectory of the installation directory), set "net.sf.saxon.TransformerFactoryImpl" as the property value and select JAXP as the XSLT processor in the transformation scenario associated to the transformed XML document.
Allows the user to enter the name of the transformer factory Java class.
Allows the user to set the XSLT Engine used for validation of XSL 1.0 documents.
Allows the user to set the XSLT Engine used for validation of XSL 2.0 documents.
The XSLT options which can be configured for the Saxon 6 transformer are:
Line numbering: If checked line numbers are maintained for the source document.
Allow calls on extension functions: If checked external functions called is allowed. Not checking this is recommended in an environment where untrusted stylesheets may be executed. Also disables user-defined extension elements, together with the writing of multiple output files, all of which carry similar security risks.
Policy for handling recoverable errors in the stylesheet: Allows the user to choose how dynamic errors will be handled. Either one of the following options can be selected: recover silently, recover with warnings or signal the error and do not attempt recovery.
The XSLT options which can be configured for the Saxon 8 transformer (both the Basic and the Schema Aware versions) are:
Version warnings: If checked a warning will be output when running an XSLT 2.0 processor against an XSLT 1.0 stylesheet. The XSLT specification requires this to be done by default.
Allow calls on extension functions: If checked external functions called is allowed. Not checking this is recommended in an environment where untrusted stylesheets may be executed. Also disables user-defined extension elements, together with the writing of multiple output files, all of which carry similar security risks.
DTD based validation of the source file: If checked XML source documents are validated against their DTD.
Line numbering: If checked line numbers are maintained for the source document.
Policy for handling recoverable errors in the stylesheet: Allows the user to choose how dynamic errors will be handled. Either one of the following options can be selected: recover silently, recover with warnings or signal the error and do not attempt recovery.
Strip whitespaces feature can be one of the three options: All, Ignorable, None.
Saxon8SA specific options
Schema based validation of the source file: This determines whether source documents should be parsed with schema-validation enabled.
Lax schema based validation of the source file: This determines whether source documents should be parsed with schema-validation enabled.
Validation errors in the result tree treated as warnings: If checked, all validation errors are treated as warnings, otherwise they are treated as fatal.
The options of the XSLTProc processor are the same as the ones available in the command line for the XSLTProc processor:
If checked XInclude references will be resolved when XSLTProc is used as transformer in the transformation scenario.
If checked the DTD specified in the DOCTYPE declaration will not be loaded.
If checked the default attributes declared in the DTD and not specified in the document are not included in the transformed document.
If checked the remote references to DTD's and entities are not followed.
If the limit of maximum templates is reached the transformation ends with an error.
If checked the transformation will output detailed status messages about the transformation process in the Warnings view.
If checked <oXygen/> will display in the Warnings view the version of the libxml and libxslt libraries invoked by XSLTProc.
If checked the Warnings view will display the time necessary for running the transformation.
If checked the Warnings view will display debug information about what templates are matched, parameter values, etc.
If checked <oXygen/> will display in the Warnings view the URL of all the files loaded during transformation.
If checked <oXygen/> will display in the Warnings view a table with all the matched templates, and for each template: the match XPath expression, template name, number of template modes, number of calls, execution time.
If checked <oXygen/> will display in the Warnings view a list with all the registered extension funtions, extension elements and extension modules.
If checked the XSLTProc processor will not write any part of the transformation result to an external file on disk. If such an operation is requested by the processed XSLT stylesheet the transformation ends with a runtime error.
If checked the XSLTProc processor will not create any directory during the transformation process. If such an operation is requested by the processed XSLT stylesheet the transformation ends with a runtime error.
The options of the MSXML 3.0 and 4.0 processors are the same as the ones available in the command line for the MSXML processors:
If checked and either the source or style sheet document has a DTD or schema against which its content should be checked, validation is performed.
By default, MSXSL instructs the parser to resolve external definitions such as document type definition (DTD), external subsets or external entity references when parsing the source and style sheet documents. If this option is checked the resolution is disabled.
If checked strip non-significant white space from the input XML document during the load phase. Enabling this option can lower memory usage and improve transformation performance while, in most cases, creating equivalent output.
If checked the relative speed of various transformation steps can be measured: time to load, parse, and build the input document; time to load, parse, and build the style sheet document; time to compile the style sheet in preparation for the transformation; time to execute the style sheet.
Although style sheet execution usually begins in the empty mode, this default may be changed by specifying another mode. Changing the start mode allows execution to jump directly to an alternate group of templates.
The options of the MSXML.NET processor are the same as the ones available in the command line for the MSXML.NET processor:
If checked XInclude references will be resolved when XSLTProc is used as transformer in the transformation scenario.
If checked and either the source or style sheet document has a DTD or schema against which its content should be checked, validation is performed.
By default MSXML.NET resolves external definitions such as DTD external subsets or external entity references when parsing source XML document and stylesheet document. Using this option you can disable this behaviour. (Note, that it may affect also the validation process.)
If checked strip non-significant white space from the input XML document during the load phase. Enabling this option can lower memory usage and improve transformation performance while, in most cases, creating equivalent output.
If checked the relative speed of various transformation steps can be measured: time to load, parse, and build the input document; time to load, parse, and build the style sheet document; time to compile the style sheet in preparation for the transformation; time to execute the style sheet.
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 references when they cannot be represented in the output encoding. That means that when you output a character that cannot be represented in output encoding, it will be outputted as '?'. Usually this happens when output encoding is set to ASCII. With this option checked the output is forced to be ASCII encoded and all non-ASCII characters get escaped as XML character references (&#nnnn; form).
This option allows to create multiple result documents using the exsl:document extension element.
This option allows to specify a custom URI resolver class to resolve URI references in xsl:import/xsl:include instructions (during XSLT stylesheet loading phase) and in document() function (during XSL transformation phase).
The previous option specifies partially or fully qualified URI resolver class name, e.g. Acme.Resolvers.CacheResolver. Such name requires additional assembly specification using this option or the next option, but fully qualified class name (which always includes an assembly specifier) is all-sufficient. See MSDN for more info about fully qualified class names. This option specifies a file name of the assembly, where the specified resolver class can be found.
This option specifies partially or fully qualified name of the assembly in the global assembly cache (GAC), where the specified resolver class can be found. See MSDN for more info about partial assembly names. Also see the previous option.
This option allows to specify extension object classes, whose public methods then can be used as extension functions in an XSLT stylesheet. It is a comma-separated list of namespace-qualified extension object class names. Each class name must be bound to a namespace URI using prefixes as when providing XSLT parameters.
MSXML.NET supports rich library of the EXSLT and EXSLT.NET extension functions via embedded or plugged in EXSLT.NET library. EXSLT support is enabled by default and cannot be disabled in this version. If you want to use an external EXSLT.NET implementation instead of a built-in one use this option.
This option allows to specify user credentials to be used when loading XML source documents. The credentials should be provided in the "username:password@domain" format (all parts are optional).
This option allows to specify user credentials to be used when loading XSLT stylesheet documents. The credentials should be provided in the "username:password@domain" format (all parts are optional).
Allows you to select the XSLT Processor to validate the XQuery
When checked the transformer's output is formatted and indented (pretty printed).
If checked, <oXygen/> takes the results of a query and creates an XML document containing copies of all items in the sequence, suitably wrapped.
Saxon8 options:
If checked external functions called is allowed. Not checking this is recommended in an environment where untrusted stylesheets may be executed. Also disables user-defined extension elements, together with the writing of multiple output files, all of which carry similar security risks.
Allows the user to choose how dynamic errors will be handled. Either one of the following options can be selected: recover silently, recover with warnings or signal the error and do not attempt recovery.
Can have one of the three values: All, Ignore, None. All - strips all whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document. Ignore - strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element-only content. None - strips no whitespace before further processing.
Saxon8SA specific options:
This determines whether source documents should be parsed with schema-validation enabled.
This determines whether source documents should be parsed with schema-validation enabled.
If checked, all validation errors are treated as warnings, otherwise they are treated as fatal.
eXist options:
URI to the installed eXist engine. If you like to set a default collection you have to first press the Refresh button in order for the Collection list to be populated.
User name to access the eXist database engine
Password to access the eXist database engine
eXist organizes all documents in hierarchical collections. Collections are like directories. They are used to group related documents together. This combo box is populated after pressing the Refresh button and allows the user to set the default collection name.
Berkeley DB XML options:
Path to the Berkeley DB XML's home directory.
The user can choose between four levels of verbosity: DEBUG, INFO, WARNING, ERROR.
X-Hive/DB options:
URI to the installed X-Hive/DB engine.
User name to access the X-Hive/DB database engine.
Password to access the X-Hive/DB database engine.
The name of the database to access from the X-Hive/DB database engine.
MarkLogic options:
The hostname or ip address of the installed MarkLogic engine.
The port number of the MarkLogic engine.
User name to access the MarkLogic engine.
Password to access the MarkLogic engine.
TigerLogic options:
The hostname or ip address of the installed TigerLogic engine.
The port number of the TigerLogic engine.
User name to access the TigerLogic engine.
Password to access the TigerLogic engine.
The name of the database to access from the TigerLogic engine.
The following settings are available:
Enable or disable rendering of output to the XHTML Output document View during the transformation process. For performance issues, it is advisable to disable XHTML output for large jobs. Also, the XHTML area is only able to render XHTML documents. In order to view the output result of other formats, such as HTML, save the Text output area to a file and use the required external browser for viewing.
If checked, the debugger presents the output of xsl: result-document instruction into the debugger output view.
Set this option to receive notifications when an infinite loop occurs during transformation.
How many templates (<xsl:templates>
) instructions can appear on the
current stack. This setting is used by the infinite loop
detection.
This section explains the settings available for XSLT Profiler mode. To display settings select Profiler (see the section called “Debugger”).
-> -> -> -> +The following settings are available:
Show the total time that was spent in the node.
Show the inherent time that was spent in the node.
Show how many times the node was called in this particular call sequence.
The time scale options determine the unit of time measurement, which may be milliseconds (ms) or microseconds (µs).
The threshold below which hot spots are ignored is entered in milliseconds (ms).
The threshold below which invocations are ignored is entered in microseconds (µs).
The percentage base determines against what time span percentages are calculated.
Absolute: Percentage values show the contribution to the total time.
Relative: Percentage values show the contribution to the calling node.
Besides the built-in formatting objects processor (Apache FOP) the user can use other external processors. <oXygen/> has implemented an easy way to add RenderX XEP as external FO processor if the user has the XEP installed.
When checked all FOP output will be displayed in a results pane at the bottom of the editor window including warning messages about FO instructions not supported by FOP.
If your FOP transformations fail with an "Out of Memory" error select from this combo box a larger value for the amount of memory reserved for FOP transformations.
You should specify here the path to a FOP configuration file, necessary for example to render to PDF using a special true type font a document containing Unicode content.
The users can configure the external processors for use with <oXygen/> in the following dialog.
The name that will be displayed in the list of available FOP processors on the FOP tab of the Transforming Configuration dialog.
The description of the FO processor displayed in the Preferences->FO Processors option.
The directory in which the intermediate and final results of the processing will be stored. Here you can use one of the following macros:
The path to user home directory.
The path of current file directory.
The project directory.
The command line that will start the FO processor, specific to each processor. Here you can use one of the following macros:
The FOP transformation method (pdf, ps, txt).
The input FO file.
The output file.
When checked, unescapes the entities found in the XPath expression. For example the expression
//varlistentry[starts-with(@os,'s')]
is equivalent with
//varlistentry[starts-with(@os,'s')]
.
If checked <oXygen/> will consider unprefixed element names in XPath expressions evaluated in the XPath console as belonging to no namespace.
If checked <oXygen/> will consider unprefixed element names in XPath expressions evaluated in the XPath console as belonging to the same namespace as the root element of the document.
If checked the namespace of the root element will be applied to the unprefixed elements in the XPath console only if it is set as default namespace on the root element.
The user has the possibility to enter here the namespace of the unprefixed elements used in the XPath console
Associates prefixes to namespaces. These mappings are useful when applying an XPath in XPath console and you don't have to define these mappings for each document separately.
The New button creates an editable prefix-namespace mapping.
The Remove button deletes the selected mapping.
One can configure other transformation engines than the ones which come with the <oXygen/> distribution. Such an external engine can be used for XSLT / XQuery transformations within <oXygen/>, in the Editor perspective, and is available in the list of engines in the dialog for editing transformation scenarios. However it cannot be used in the Debugger perspective.
The following parameters can be configured for a custom engine:
Here you can configure the JDBC Drivers for the Import from Database
action. Any database server that supports JDBC connectivity can be configured. You can check the list of JDBC drivers
(http://www.oxygenxml.com/database_drivers.html)
available for the major database servers. Before configuring a new JDBC
driver for your database server in the following dialog you have to copy the
jar file containing the driver in the lib
subfolder
of the <oXygen/> installation folder and restart the <oXygen/> application.
Opens the JDBC Drivers dialog, allowing you to configure a new driver that will appear in in the list from "Select database table" dialog.
Provide the name for the JDBC Driver
Provide the URL for the JDBC Driver
Provide the Driver Class for the JDBC Driver
Adds the JDBC driver class library.
Removes driver class library from the list.
Detects JDBC driver candidates.
Stops the detection of the JDBC driver candidates.
Opens the JDBC Drivers dialog, allowing you to edit the selected driver. See above the specifications for the JDBC Drivers dialog.
Deletes the selected JDBC Driver.
Here it is configured how empty values and null values are handled when they are encountered in an import operation.
If this option is enabled an empty value from a database column will be imported as an empty element.
If this option is enabled a null value from a database column will be imported as an empty element.
If checked, the generated XML Schema will contain an annotation for each of the imported table's columns. The documentation inside the annotation tag will contain the remarks of the database columns (if available) and also information about the conversion between the column type and the generated XML Schema type.
If Data base specific Date/Time format is checked, the date and time formats specific to the database will be used for import. The type used in the generated XML Schema will be xs:string.
If XSL Schema specific Date/Time format is checked, the ISO8601 format ( yyyy-MM-ddTHH:mm:ss ) will be used for imported date/time data. The types used in the generated XML Schema will be xs:datetime, xs:date and xs:time.
Some networks use Proxy servers to provide Internet Services to LAN Clients. Clients behind the Proxy may therefore, only connect to the Internet via the Proxy Service. The Proxy Configuration dialog enables this configuration. If you are not sure whether your computer is required to use a Proxy server to connect to the Internet or the values required by the Proxy Configuration dialog, please consult your Network Administrator.
Open the Proxy Configuration dialog by selecting
-> -> .Complete the dialog as follows:
When checked enables <oXygen/> to use the specified Proxy Server. When unchecked, Proxy Server is disabled.
The IP address or Fully Qualified Domain Name (FQDN) of the Proxy Server.
The TCP Port Number, normally set to 80 or 8080.
The Name of the user if required. Can be empty.
The Password for authentication. Can be empty.
Specify domains for which no proxy should be used.
When checked enables SOCKS using the specified host and port for the server. When unchecked, SOCKS is disabled.
The SOCKS host you wish to connect to.
The SOCKS port you wish to connect to.
The period in seconds after which <oXygen/> will consider a HTTP server is unreachable if it does not receive any response to a request sent to that server.
A change to this setting takes effect only after the Eclipse platform is restarted.
The Proxy settings are first looked up in the options. If there were no previous options set then the settings are loaded from the "servers" file located in the "%HOME%\Application Data\Subversion\" folder on Windows and %HOME%\.subversion\ folder on Linux and Mac OS X.
In <oXygen/> there are provided two types of Keystores: Java KeyStore (JKS) and Public-Key Cryptography Standards version 12 (PKCS-12). A keystore file is protected by a password.
Represents the type of keystore to be used.
Represents the location of the file to be imported.
The password which is used to protect the privacy of the stored keys.
The alias to be used to store the key entry (the certificate and /or the private key) inside the keystore.
It is only necessary in case of JKS keystore. It represents the certificate's private key password.
Verifies the entries from the fields; assures that the certificate is valid.
Allows you to import all transformation scenarios from a scenarios properties file. Their names will appear in the "Configure Transformation Scenario" dialog followed by "(import)". This way there are no scenarios' names conflicts.
Allows you to export all transformation scenarios available in the "Configure Transformation Scenario" dialog.
When drag and drop is disabled for the tree displayed by the outline view there is no possibility to accidentally change the structure of the document.
When checked, a line in the Console view will be hard wrapped after Maximum character width characters.
When checked the content of the Console view will be limited to a configurable number of characters.
Console buffer - specifies the maximum number of characters that can be written at some point in the Console view.
Tab width - specifies the number of spaces used for depicting a tab.
<oXygen/> supports Syntax Highlight for XML, DTD, Relax NG (XML and Compact Syntax), Java, JavaScript, XQuery, C++, C, PHP,CSS, Perl, Properties, SQL, Shell and Batch documents. While <oXygen/> provides a default color configuration for highlighting the tokens, you may choose to customize, as required, using the Colors dialog.
Open the Syntax Highlight panel by selecting Window->Preferences->oXygen->Syntax Highlight and choose one of the supported Document Types. Each document type contains a set of Tokens. When a Document Type node is expanded, the associated tokens are listed. Selecting a token displays the current color properties and enables you to modify them. You can also select a token by clicking directly in the preview area on that type of token.
One row of the table contains the association between a namespace prefix and the color used to mark start tags and end tags in that prefix. Note that the marking mechanism does not look at the namespace bound to that prefix. If the prefix is bound to different namespaces in different XML elements of the same file all the tags with the prefix will be marked with the same color.
One can choose that only the prefix to be displayed in the chosen color by checking the Draw only the prefix with a separate color option.