XML Author

When you paste content Oxygen checks if that is valid at the cursor position and if that fails then recovery strategies are proposed in order to keep the document valid. Version 15.2 includes a strategy that automatically analyzes nearby positions to determine a valid location for that content.

You can choose to insert an element that is not valid at the current position and Oxygen will trigger automatically recovery strategies to place that element in a valid location. This removes the requirement to position the cursor in the exact location where an element is accepted, you can insert it also if the cursor is positioned in a near-by location.

The Author editing mode in Oxygen offers support for rendering PDF images by installing a third-party library.
read more

The Author editing mode in Oxygen can properly render JPEG images that have an embedded CMYK profile.
read more

The Author editing mode in Oxygen offers support for rendering TIFF images.
read more

All the CSS Level 3 structural pseudo-classes are supported (:root, :last-child, :first-child, :nth-child, :nth-of-type, :not(), :empty, etc.)

The experimental subject selector from CSS Level 4 is now supported. It can match an element by taking into account its children (for instance, "chapter! > title" will match any chapter that contains at least a title).

You can style your XML documents depending on the mouse and cursor position over the document by using the :hover and :focus CSS pseudo-classes.

You can use constructs such as ${i18n(key.name)} directly in the CSS content of a 'before:' or 'after:' pseudo-element to reference keys which can be translated to multiple languages through the built-in Oxygen internationalization support.
read more

Import instructions from CSS documents are passed through the XML catalog URI mappings.
read more

By adding a URI mapping to map a specific URI to a CSS file you can contribute a CSS to be used when rendering any XML document in the Author editing mode. This allows you to enforce some specific styles on any XML file without the need to modify the CSS documents which come with existing document type configurations.
read more

The content used for the ":before" and ":after" pseudo-elements can be created incrementally from the content specified by these properties. This reduces the complexity of selectors when the content depends on multiple conditions.
read more

Two additional boolean properties are available allowing to display the associated action's text and/or icon on the button form control (showText and showIcon).

Using the actionContext property, available on the oxy_button and oxy_button_group form controls, the author actions associated with these form controls can be executed either in the context of the element that contains the form controls or in current context, if that is included in the element that contains the form control. For example, this allows you to place element specific actions on an element and execute them to perform actions at the cursor position (if the cursor is inside that element).

If the attribute edited through a form control is from a specific namespace then you can specify it in the edit property as a QName. The CSS must contain a namespace declaration mapping the QName prefix to the attribute namespace.

You can add syntax highlight to the codeblock and pre sections from your published PDF and XHTML-based outputs by setting specific programming language values to the outputclass attribute.

If you are using index terms in your DITA content, the PDF output generated with the default bundled PDF processor (Apache FOP) will also contain the index page at the end of the PDF.

You can create new troubleshooting topics based on the included experimental DITA 1.3 Troubleshooting DTD specialization plugin.

An alternate CSS was introduced, so you can now edit codeblock sections using the Text Area form control. Thus, you benefit from syntax highlight for a variety of document types.

An alternate CSS was introduced, so you can now edit program listings using the Text Area form control. Thus, you benefit from syntax highlight for a variety of document types.

You can set your custom CSS pseudo-classes on the nodes from the AuthorDocument. These are similar to the normal XML attributes, with the important difference that they are not serialized, and by changing them the document does not create undo and redo edits - the document is considered unmodified. You can use custom pseudo-classes for changing the style of an element (and its children) without altering the document.
read more

If you have both a plugin and a framework which need to set an AuthorDocumentFilter, you can obtain the existing filter implementation and wrap it in your own filter implementation using the API AuthorDocumentController.getDocumentFilter().

Added the API method AuthorDocumentController.refreshNodeReferences(AuthorNode) to refresh references on a certain node for developers who implement a custom AuthorContentReferencesResolver.

Added the API method WSDITAMapEditorPage.getActionsProvider() to obtain actions defined in the DITA Map Editor Page and mount them to custom controls.

You can obtain in your extension Java operations the current unique attributes processor in order to check if certain attributes should be removed when copying content using the API AuthorDocumentController.getUniqueAttributesProcessor().

The CSS Alternatives drop-down button defined in the document type can be added to the toolbar of an Author Component application using the API WSAuthorComponentEditorPage.createCSSAlternativesToolbar().

If a DITA Map URL does not have an extension and a custom URL Connection is implemented for it in the application the method URLConnection.getContentType() can return the value application/ditamap to identify it as such.

If a custom form control performs a custom edit, it can pass the Runnable containing the edit to the application in order to integrate better in the editing flow using the API EditingEvent.customEdit.

The ExecuteMultipleActionsOperation can execute a sequence of actions, defined as a list of IDs. The actions must be defined by the corresponding framework, or one of the common actions for all frameworks supplied by Oxygen. ExecuteMultipleActionsOperation.