XML Editor

The insertion of XML fragments and attributes is checked against the associated schema. If the XML fragment is not accepted at the cursor position, multiple strategies are employed to determine a better insert position. The developers can implement other strategies as needed by customizing the OxygenAuthor mode.

All the major XML documentation frameworks were enhanced with specific schema-aware editing support. For instance, when editing a DocBook document the text inserted directly in a section is wrapped automatically in either a title or a para element. Typing text between the rows of a table will result in automatic creation of table row and table cell elements around the inserted text. Pasting a list item into a section will also create the parent list element and so on. The same functionality is available for DITA, TEI and XHTML.

When a document is loaded into the Author mode, the XML schema information is taken into account to decide whether or not whitespaces are relevant. For instance, spaces between sibling elements are relevant if the model of the parent element is mixed, and they are ignorable if the parent element has an element-only content.

A more compact layout is used for the "full-tags" display mode of the Author mode. This layout is much more ergonomic by placing multiple XML tags on the same line.

By enabling the "Quick up/down" in the visual editing mode, the cursor is moved directly between the lines of text without going through intermediate positions between blocks (the intermediate position can still be reached using the left/right arrows or with the mouse). For instance, you can move the cursor directly from the title text into the paragraph text, without going through the intermediate position between them. This is a very helpful feature when reviewing documents or editing mainly content.

There are additional methods available in the Author API. For example, you can close an editor, or create an XSLT or XQuery transformer. Schema-aware editing can be customized for a specific document type by registering an AuthorSchemaAwareEditingHandler.

The DITA Open Toolkit has been updated to the latest version: 1.5 M24

Starting with version 9.2 Saxon allows setting a configuration file that specifies all the possible options for the processor. You can specify such a configuration file for the Saxon processor embedded in Oxygen XML Editor.

Oxygen XML Editor provides rendering and a set of custom actions to help writing XSLT documentation inside XSLT stylesheets in the visual editing mode.

Any XQuery Processor implementing the XQJ API can be configured and used for XQuery execution in Oxygen XML Editor.

The XProc transformation scenarios allow you to set options and parameters (global or for each port).

The Content Completion Assistant offers the available option names of the built-in steps. When entering a port reference it displays the available port names.

Oxygen XML Editor collects the messages Calabash writes to the standard error and displays them for the user. These provide important information related to the reported errors. For example, the user can find the reason a stylesheet compilation failed.

The schema author can control the error level used for Schematron reports and failed assertions. This can be done using the "role" attribute. Oxygen XML Editor will recognize values (such as info or information, warn or warning, error, and fatal) and will set the error level of the reported messages accordingly.

If the Schematron schema specifies a URL in the "see" attribute then Oxygen XML Editor will report the in-scope see attribute value as additional URL information for the reported message. The user will be able to just click in the message to open that URL. For example, the schema author can specify a URL the user will be directed to if an assertion fails, that URL can provide details about what the assertion checks and what are the possible solution to fix the file when the assertion fails.

The XML validation scenarios can be saved to a file and imported in another Oxygen instance.

The format and indent takes into account schema or DTD information to determine if an element has text, element only or mixed content. It also looks if the schema or the DTD defines a default xml:space attribute to know if the whitespace should be preserved or not.

It is possible to specify a list of elements that have mixed content, thus allowing correct processing of the whitespaces inside those elements in cases when the instance document does not contain enough information to allow Oxygen XML Editor to detect that the content is mixed.

When the "Indent inline elements" option is enabled the XML elements inside mixed content (inline elements) are indented on a new line if they are preceded by whitespace only text. If unchecked, the inline elements are placed on the same line with the surrounding text.

Empty lines are frequently used to delimit sections in the CSS source. The editor preserves the empty lines when you pretty-print a CSS file.

A number of XML search options have been added to the Find/Replace dialog box, allowing you to control exactly what parts from the XML document should be processed (text nodes, attribute values, comments, etc.) This capability is available when using the find/replace operation over a document loaded in the Text mode, or when using it over a set of files.

You can limit the range of the find and replace operations to sections from the XML documents that are covered by the given XPath expression.

The exact search terms are highlighted when shown in the search results list. This makes it easier to spot the term into the surrounding context.

The diff support from Oxygen XML Editor is available also as a separate application or as a component. For more information please see the diff description page.

You can specify file or directory patterns to exclude resources during the comparison operation.

When performing a diff between directories and archives the files can be compared by timestamp, through a binary comparison. Oxygen can also apply content comparison. This allows you to honor comparison options, such as ignoring the whitespaces, the namespace prefixes in XML, etc.

The document windows can be easily arranged using the actions from the Window menu that allow you to tile document windows horizontally/vertically or to stack them together.

The scrolling feature allows to auto synchronize horizontal and vertical scrolling for all visible document windows making easy to inspect similar files when placed side by side. This functionality can be activated from the Window menu.

The last closed document can be quickly reopened with the "Reopen last closed editor" action available from the contextual menu of any editor tab.

The last cursor position of a file edited in Oxygen is restored when the file is reopened.

The user can specify a list of simplified XPath expressions that match the XML elements that will be ignored by the spell checking operation.

When editing an XML document you can assign background colors to XML elements and attributes from different namespaces, by associating colors to prefixes. This option is available in the "Editor / Colors / Elements/Attributes by prefix" options pane.

A framework was added to provide document templates, an XML Catalog, and default schema for KML files. KMZ files are registered in Oxygen XML Editor as archives so they can be easily explored in the Archive browser and the enclosed files can be edited by Oxygen XML Editor directly inside the KMZ archive.

The SVNKit library was updated to version 1.3.1.

Configurable timeout for repository connections and stop non-responsive repository browsing operations.

Added support for importing files into a repository.

Working copy resources can be replaced with their version from the HEAD or BASE revision.

Operations correctly take into account obstructed resources.

Show history for resources deleted from the repository but which are still present in the working copy.