XML Editor

ID attributes can be generated automatically for a configurable list of XML element names for a number of frameworks (DITA, DocBook and TEI). The pattern for the unique ID values is also configurable.

An XML framework was added for editing Encoded Archival Description(EAD) XML documents in Author mode.

Oxygen generates automatically ID attributes for topics, tables, lists and figures. The ID generation options are available from the DITA > ID Generation Options menu.

Multiple files can be added to a DITA map with one drag-and-drop action or with one insert reference action.

The find and replace operation can be applied on all the XML files referenced from a DITA map.

The ANT home folder can be changed to an ANT installation outside the Oxygen installation.

An XHTML document can be converted to a DITA concept, DITA reference, DITA task or DITA topic using predefined transformation scenarios.

Oxygen can generate automatically ID attributes for a number of DocBook elements. The ID generation needs to be enabled and can be configured from the DocBook > ID Generation Options menu.

Depending on context, the action inserts an inline graphic or figure element.

A pre-configured transformation scenario is available for DocBook 4 and 5 documents for generating HTML chunked output.

Developers can register mouse listeners and cursor listeners for receiving notifications on the currently edited XML document.

Methods were added in the Author API for finding and changing the content of the DTD internal subset. This is useful, for example, to add or edit a DTD entity declaration.

Extensions developers can store and retrieve data from an options storage that is persisted by Oxygen and associated with the XML framework the extension belongs to.

All the extensions of a document type are registered in an extensions bundle thus simplifying the configuration in the Oxygen options and providing developers with a single point of extending the Author functionality for a specific XML framework.

The Component Dependencies view displays a tree of component dependencies starting with a specified component. For example, you can quickly see where a schema type is used and expand further to see where the components that use that type are used and so on. Or you can see from where an XSLT template is called and, if called from other named templates, you can expand further to see where they are called from.

The tree of references displayed in the Component Dependencies view is the result of a search performed on a configurable scope. The search scope can be set to the current project or to a set of specified locations.

The XSLT dependencies allows to find where different XSLT components are used (named templates, functions, variables, parameters, attribute sets, character maps, etc.)

The XML Schema Dependencies view allows you to find where a specific XML Schema component is used. It can search for types, elements, attributes, groups, attribute groups, etc.

The Relax NG schema Dependencies view allows to find where a specific Relax NG pattern is used and to expand further to see where the referencing patterns are used at their turn.

The NVDL script Dependencies view allow to find where a named mode is used.

The properties that are displayed in the XML Schema diagram for each schema component are configurable.

The XML Schema annotations are presented in callouts pointing to the component they describe. Errors can be more easily spotted on the diagram with the help of the in-diagram error markers.

The format of the images containing schema diagrams can be selected from JPEG, PNG and GIF.

The XML Schema documentation generation dialog box contains an option that controls the inclusion of the local elements and attributes in the table of contents.

XQuery Update operations are now possible using the Saxon SA XQuery processor (that ships with Oxygen). XML documents can be updated with the various insert/delete/modify/create instructions defined in the W3C candidate recommendation for XQuery Update 1.0.

The XSLT content completion support offers all the XSLT attributes (for example, the xsl:use-attribute-sets attribute on literal result elements).

Syncro SVN Client supports SVN 1.6.2, allowing users to take advantage of the latest SVN improvements and fixes. Previous SVN versions are also supported, the user being able to decide whether a working copy should be updated to version 1.6 or not.

Apache Subversion^TM 1.6 recognizes a type of conflict, known as a "tree conflict". Such conflicts manifest at the level of directory structure, rather than file content. These conflicts include deletions of locally modified files and incoming edits to locally deleted files. Syncro SVN Client allows to handle these conflicts offering a dialog box that lists possible solutions for solving these conflicts.

Apache Subversion^TM 1.6 allows to link to external files by putting their URLs in the svn:externals property on the parent folder. Syncro SVN Client allows you to create, update, commit and remove external links from the user interface changing automatically the svn:externals property as needed.

Syncro SVN Client stores the result of a revision graph operation and re-uses that for further operations on the same repository, thus avoiding unnecessary requests to the SVN server for the same data. This results in a noticeable increase in performance.

Network SVN repositories can be accessed using file URLs of the form "file://server/path".

Syncro SVN Client detects and handles infinite recursions by analyzing the structure created by the use of symbolic links.

The search and replace operation can act on all opened files.

The Saxon-SA and Saxon-B processors that ship with Oxygen were updated to the latest 9.1.0.7 version.

The libxml XML parser was updated to version 2.6.32. The libxslt transformer was updated to version 1.1.23.

The DocBook XSL stylesheets were updated to version 1.75.1.

The TEI schemas and XSLT stylesheets were updated to the latest 1.4.0 and 5.23 versions, respectively.