XML Editor

This is an automatically synchronized tree-based Outline view. The document tree structure will be presented as the document is edited. The modified element will be automatically revealed and selected in the Outline view. Also an element can be selected in the Text editing mode by clicking on the corresponding node in the Outline view. It uses a robust parser thus it will be able to handle not well formed documents properly.

Bookmarks can be easily added, deleted and retrieved so you can rapidly navigate to the important locations from your documents.

Once defined, a scenario can be re-used for any document. For instance, you can configure a scenario such as DocBook to PDF and use it to convert any DocBook document to PDF.

Importing and exporting scenarios make the share of transformation scenarios easy.

XInclude support can be enabled from the "XML Parser options" Preferences page.

Not only can the edited files now be opened from a remote location but also the files involved in a transformation scenario.

The remote file editing also adds security, thus, along with FTP and WebDAV/HTTP support from version 3, WebDAV/HTTPS support is available.

The user is assisted by a wizard helping him/her to easily associate a DTD or a schema file (XML Schema, RelaxNG or NRL schema) with the edited document.

Although it was possible with previous versions of Oxygen to convert between different types of schemas, this is now very simple. When a file is edited the user can choose the "Convert to..." action and just select the target format. A file name for the result schema is automatically suggested and also the result file can be automatically opened in the editor. Advanced options allow the user to customize different conversion parameters.

Previously, when the actual element content did not match the model of the element type, the reported error was on the end tag of the element. Oxygen now also reports an error on the first element that caused the actual content to not match the model of the element type, thus making it easy to understand and fix validation errors.

XML documents can be easily associated and validated with NRL schemas. If a NRL schema is selected in the new document wizard it will be automatically associated with the document. Also the Associate Schema dialog box supports NRL schemas.

New NRL schemas can be created, edited and validated.

Any JAXP compliant XSLT processor can be easily integrated to work from within Oxygen. All you have to do is to place the XSLT processor jar(s) in the libraries folder and set the javax.xml.transform.TransformerFactory from the preferences to point to your XSLT processor transformer factory implementation. Then in the transformation scenarios select JAXP as the XSLT processor.

Thanks to Hiroshi Okugawa Oxygen's interface is available also in Japanese.

It is possible to specify elements for which spaces should be preserved and elements for which spaces should be stripped. This allows users to pretty-print documents and have some control over space handling without using xml:space attribute or CDATA sections. A common use case is the DocBook programlisting element where the user wants to preserve the spaces and as the DocBook DTD does not define the xml:space attribute this is possible only if a CDATA section is used. The programlisting can be added to the preserve spaces elements list and it will be treated exactly as if an xml:space="preserve" attribute was added to this element.

The format and indent action can be configured to maintain the attributes order or to order them. Also it is possible to configure if the empty elements should be formatted as <empty/> or as <empty></empty>.

A pretty-print action is available on the RNC editor to nicely format a RNC schema.

The keywords are offered in the code completion on-request pop-up when editing RNC files.

Some keywords are offered in the code completion pop-up when editing DTD files.

If the content of a file is included using an external entity reference then open file at cursor will open the external entity file. This makes the navigation to the components of the document faster.

The user can now specify a configuration file for the Apache FOP, thus being able to use custom fonts for the generated PDF, for instance.

The output messages of Apache FOP can be displayed in the console if the user wants to see them. Also the maximum memory that will be used by FOP is configurable.

The user can specify what application to be used as external browser.

The documents printed from Oxygen will now look better as only integer number of lines will appear on each page.

Oxygen now handles all the Java encodings as XML documents encoding.

The editing area can be expanded on the whole window if a double-click is issued on the current edited tab. Double-click again to restore the editing area.

The "surround in" option offers the possible elements according to the DTD or schema, but now it also allows the user to specify a custom tag.

The licensing mechanism requires just to paste a few lines of text in a dialog box that appears automatically when the editor starts. This is all, no more license files and problems where to place them.

The document structure will be used for driving the Content Completion Assistant when a schema or a DTD is not specified when a document is opened.

The version of the XML parser, of the XSLT processors, FOP and the versions of the document frameworks bundled with Oxygen is available in the about box.