XML Editor

When an attribute value is deleted, the attribute itself is removed. If an attribute with an empty value is needed, it can be set using a contextual action or by leaving the value empty when the attribute is added.

The predefined attributes are presented before the other ones in the Attributes view. Therefore, the attributes defined on an element are more visible, without the need to scroll down a list with a large number of possible attributes.

Different font styles and colors are used to mark attribute states, allowing you to rapidly spot previously set attributes, default values, and invalid attributes.

The validation, transformation, spell checking and search results are presented in a tree-table view that allows a far better layout than the tree or table views previously available.

A tree-table presentation allows user-defined grouping and sorting. The keys used for grouping form the tree, while the rest of the information is presented using a table layout. The remaining table columns can be sorted.

The results were enhanced with additional information to identify the operation that issued them. This information is used by the tree-table viewer to group messages from the same operation. Relevant messages related to batch operations or complex validation scenarios are easily identifiable.

The Data Source Explorer view displays the content of XML Databases and other data sources supports multiple selections, thus allowing performing operations on multiple resources.

In the Data Source Explorer view it is possible to copy and move resources (files or containers) using drag-and-drop or Copy/Paste actions in the same data source or between different data sources. The supported data sources for such actions are: eXist, xDB (xHive), FTP, WebDAV.

There are additional editor variables available for archives that are expanded to the archive file name, file path, URL, directory and directory URL. These additions are useful when setting parameters to ANT scenarios which can be applied on the zip archive from which the current edited XML file was opened.

Most of the recognized editor variables are available for use and automatically expanded on insertion both within defined code templates and for parameters set to Author operations.

Added JSON editing support. This features validation, format and indent, syntax highlighting, and folding support.

A Grid editing mode is available for the JSON editor that displays the JSON content in a structured manner.

A tool is available for converting XML files to JSON content.

Default CSS files are provided for the NCX, OPF and OCF frameworks thus enabling the Author editing mode on these files. References to other files are rendered as links and these files can be easily opened by following the links.

Default validation scenarios were added to perform enhanced validation on EPUB files, similar with the EpubCheck validation, featuring Relax NG and Schematron checks. This also creates a consistency between the errors reported by the integrated EpubCheck validation and the validation of individual files from the EPUB archive.

An "Edit Reference" action, available from the contextual menu, allows you to edit referenced content by opening the target file containing it and positioning the cursor at the precise location where the action was invoked in the main file.

You can change the default Author mode background (white) and foreground (black) colors from the preferences. If colors are specified in the CSS file they overwrite the default values.

All the actions previously available only in the Text mode for fold management, are also available in the Author editing mode when right-clicking a fold triangle. Many powerful actions, such as collapse/expand child folds, close all other folds, or expand/collapse all folds, can be performed from the fold marker contextual menu.

If an XHTML document specifies a CSS using the link element then the CSS is detected and used by the Author mode to render the XHTML content.

A recovery strategy was added when using the schema-aware editing mode. This is particularly useful when pasting content from office applications or the web browser. The content is automatically converted to match the editor schema when editing DITA, DocBook, TEI or HTML. In some cases additional wrapper elements may result after the conversion and these are automatically removed by this strategy if they are found to be invalid at the insertion point.

Four additional actions allow you to convert the selected content to upper case, lower case or to capitalize sentences and words. There is also an action that counts the number of words and characters from the current opened file.

Browser CSS extensions from IE, Safari, Opera, Mozilla are recognized and validated by default.

All the Oxygen specific CSS functions were renamed to contain an Oxygen prefix "oxy_" in order to easily identify them as extensions. The old names are still supported but they are deprecated.

The content completion proposals contain the Oxygen specific functions when the CSS profile is set to "CSS 3 with Oxygen extensions" (which is the default behavior).

Arithmetic operations are available (addition, subtraction, multiplication, division, modulo), leading to more powerful CSS processing.

This property allows to control the initial rendering of a fold. If the folded property is set to true then the fold is presented collapsed.

Quickly search all the references of a topic, element or key in all the topics referenced from the opened DITA Map. The action is available from the contextual menu of the DITA Maps Manager and the Author mode for opened DITA topics.

You can specify multiple ditaval filters (or multiple defined condition sets). The advanced DITA validation will automatically be performed on the map and the topics resulted after applying each condition set. This allows you to easily check that all the deliverables that you obtain from the same DITA map are consistent.

The default DITA schematron validation was enhanced to automatically check that the defined IDs are unique within the scope of a topic.

The Content Completion Assistant displays the values defined in a subject scheme map for the specified attributes.

By following a key reference to a keyword, you are led to the keyword definition.

The actions that highlight content as bold, italic and underline are implemented as toggle actions. This means that triggering them on content that is already highlighted, removes the highlight.

Including content from another file can be done using the Insert XInclude action that allows you to browse and select the content to be included. It also generates the corresponding XInclude markup automatically.

The actions that highlight content as bold, italic and underline are implemented as toggle actions. This means that triggering them on content that is already highlighted, removes the highlight.

The actions that highlight content as bold, italic and underline are implemented as toggle actions. This means that triggering them on content that is already highlighted, removes the highlight.

Oxygen includes a built-in transformation scenario to convert TEI documents to EPUB.

Built-in transformation scenarios to convert TEI documents to and from DOCX are available.

Built-in transformation scenarios to convert TEI documents to and from ODT are available.

The actions that highlight content as bold, italic and underline are implemented as toggle actions. This means that triggering them on content that is already highlighted, removes the highlight.

Changes inside documents are displayed using two levels of granularity: a coarser one which displays blocks of changes and a finer one that highlights the actual changes inside blocks.

The visual representation of changes was improved. Highlight colors and cleaner change delimiters reduce clutter in the central working area and allow you to focus on a specific change.

Navigation operations were updated to take into account the unified two-level diff. They can jump from one block of changes to the another and they also step into blocks passing through each actual change.

Merging operations are faster and offer more flexibility, being able to act both on blocks of changes and single modifications.

Much effort was put into redesigning the Diff application layout in order to offer better ergonomics and improved workflow: a redesigned toolbar with reworked icons help improve the user experience. Also, an in-place widget provides quicker access to content-dependent actions that allow you to copy, replace or delete the content of any difference.

File locks in the Working Copy view are presented using graphic symbols, which allow you to rapidly identify files with active, broken or stolen locks. Also, when synchronizing your working copy with the repository, you can see the current lock state of files in the repository, including those locked by other users.

Repositories view displays the existing file locks when browsing repository content. You can lock or unlock files directly in the repository, using actions available in the Repositories view.

Comparing algorithm has been improved to detect differences at a finer level of granularity. Besides the old detection of different blocks of text, Syncro SVN Client brings a second level of comparison, by directly emphasizing word differences inside these blocks. Management of differences was improved by presenting an in-place widget which gives quicker access to actions which allow you to copy or replace content of the currently selected difference.

Improved connection security when accessing a repository through SSH protocol for the first time. Syncro SVN Client allows you to interrupt the connection to an untrusted SSH host.

Syncro SVN Client signals the existence in repository of files considered to have the same name on a case-insensitive operating system, such as Microsoft Windows. These files are marked as being in a Name Conflict state in your working copy.

The framework definitions (aka Document Types) contain a priority field. This allows setting higher priority values for user-supplied frameworks, thus making sure that they override eventual default provided frameworks for the same vocabulary.

A custom Oxygen installation can be bundled with default preferences that provide everybody using the application with the same initial consistent settings. As an alternative, a remote preferences file can be specified using a custom system property, thus the default settings can be changed dynamically from a common location for all users.

An action in the Archive Browser View allows you to see, for example, how an EPUB is rendered in your system's default EPUB reader application.

An option allows you to preserve previously set element id's when copying content in the same document.

WSDL 1.1 with SOAP 1.1 validation was improved to adhere to the WSDL specification. Thus it reports more XML Schema-related problems (including broken references between WSDL and schema components).

The printed pages header and footer content can be configured from Oxygen options. This setting applies to the Text and Author modes.

This action, that can be used to insert an XInclude reference by selecting the content to be included, is also available in the Source section of the Text editing mode's contextual menu.

The DITA Open Toolkit was updated to version 1.5.3.

The TEI XSLT stylesheets were updated to version 5.54.

Updated SVNKit library to version 1.3.5, compatible with Apache Subversion^TM 1.6.15, which contains various bug fixes and improvements.

This operation allows browsing for and selecting the content to be included. It also generates the corresponding XInclude instruction automatically.

Inserts a fragment containing a customizable MathML equation and starts the editing of this equation in the default configured MathML editor.

This operation removes the current element tags or the tags of an element identified with an XPath location.

This operation allows content wrapping in a specific element that can have specific attributes, or content unwrapping. For example, it can be used to implement actions that toggle bold, italic or underline text styles.

Methods in the Workspace interface allow you to clear the image cache, especially useful when working with remote images.

When a document contains attributes that should not be presented to the user, the API can be used to filter them from the Outline and the Attributes views.

The method "ro.sync.exml.workspace.api.editor.WSEditorBase.saveAs(URL)" can be called to save the content of the editor to another location (just like performing File > Save As). You can add a "ro.sync.exml.workspace.api.listeners.WSEditorListener" on an editor that will be notified before and after an editor has saved its content, with the possibility to reject this operation. This API is available also in the Author Component.

Use the "ro.sync.exml.workspace.api.editor.WSEditor.changePage(String)" method to switch modes (Text, Author, Grid, or Design).

A validation problems filter can be added using the "ro.sync.exml.workspace.api.editor.WSEditor.addValidationProblemsFilter(ValidationProblemsFilter)" method and can be used to remove or add entries in the automatic or manual validation list of errors.

Use the "ro.sync.exml.workspace.api.util.XMLUtilAccess.addPriority" methods to add priority entity and URI resolvers which will be called before the application tries to resolve resources through the standard catalog support.

The AuthorComponentFactory now implements a ReferencesCustomizer, allowing the developer to add an input URL chooser customizer to the Author Component. This API was previously available only for plugins installed in the standalone editor.