• 2023

    25.0
    Version 25.0 - October 13, 2022
  • 24.1
    Version 24.1 - March 7, 2022
  • 2022

    24.0
    Version 24.0 - October 18, 2021
  • 23.1
    Version 23.1 - March 4, 2021
  • 2021

    23.0
    Version 23.0 - November 19, 2020
  • 22.1
    Version 22.1 - May 19, 2020
  • 22.0
    Version 22.0 - February 12, 2020
  • 2020

    21.1
    Version 21.1 - May 23, 2019
  • 21.0
    Version 21.0 - February 22, 2019
  • 2019

    20.1
    Version 20.1 - June 15, 2018
  • 20.0
    Version 20.0 - March 16, 2018
  • 2018

  • 19.0
    Version 19.1 - September 29, 2017
    Version 19.0 - April 5, 2017
  • 2017

  • 18.0
    Version 18.1 - October 18, 2016
    Version 18.0 - April 21, 2016
  • 2016

  • 17.0
    Version 17.1 - October 20, 2015
    Version 17.0 - May 5, 2015
  • 2015

  • 16.0
    Version 16.1 - October 7, 2014
    Version 16.0 - May 20, 2014
  • 2014

  • 15.0
    Version 15.2 - January 22, 2014
    Version 15.1 - October 7, 2013
    Version 15.0 - June 7, 2013
  • 2013

  • 14.0
    Version 14.2 - February 13, 2013
    Version 14.1 - October 19, 2012
    Version 14.0 - June 27, 2012
  • 2012

  • 13.0
    Version 13.2 - January 12, 2012
    Version 13.1 - October 26, 2011
    Version 13.0 - August 29, 2011
  • 2011

    12.0
    Version 12.2 - May 19, 2011
    Version 12.1 - January 12, 2011
    Version 12.0 - September 14, 2010
  • 2010

  • 11.0
    Version 11.2 - March 16, 2010
    Version 11.1 - December 17, 2009
    Version 11.0 - October 9, 2009
  • 2009

    10.0
    Version 10.3 - June 29, 2009
    Version 10.2 - April 15, 2009
    Version 10.1 - February 25, 2009
    Version 10.0 - October 23, 2008
  • 2008

  • 9.0
    Version 9.3 - July 2, 2008
    Version 9.2 - May 9, 2008
    Version 9.1 - December 18, 2007
    Version 9.0 - November 2, 2007
  • 2007

    8.0
    Version 8.2 - May 7, 2007
    Version 8.1 - January 25, 2007
    Version 8.0 - November 20, 2006
  • 7.0
    Version 7.2 - June 6, 2006
    Version 7.1 - March 2, 2006
    Version 7.0 - January 13, 2006
  • 2006

  • 6.0
    Version 6.2 - September 19, 2005
    Version 6.1 - July 19, 2005
    Version 6.0 - May 22, 2005
  • 2005

    5.0
    Version 5.1 - January 18, 2005
    Version 5.0 - October 15, 2004
  • 4.0
    Version 4.2 - July 15, 2004
    Version 4.1 - June 10, 2004
    Version 4.0 - April 30, 2004
  • 3.0
    Version 3.1 - February 6, 2004
    Version 3.0 - January 14, 2004
  • 2004

  • 2.0
    Version 2.0.4 - September 19, 2003
    Version 2.0.3 - August 14, 2003
    Version 2.0.2 - June 9, 2003
    Version 2.0.1 - May 15, 2003
    Version 2.0 - April 2, 2003
  • 2003

  • 1.0
    Version 1.2.4 - December 17, 2002
    Version 1.2.3 - November 27, 2002
    Version 1.2.2 - October 22, 2002
    Version 1.2.1 - September 27, 2002
    Version 1.2 - June 27, 2002
    Version 1.1.9 - June 15, 2002
    Version 1.1.8 - June 5, 2002
    Version 1.1.7 - May 27, 2002
    Version 1.1.6 - May 24, 2002
    Version 1.1.5 - May 20, 2002
    Version 1.1 - May 15, 2002
    Version 1.0 - April 15, 2002

What's New in Oxygen XML Editor 25.0

October 13, 2022

Oxygen XML Editor version 25.0 provides a platform to work both with XML and XML-related resources by extending its support to other languages such as JSON and YAML, and being able to treat some file types (Word, Excel, OpenAPI, HTML, Markdown, and others) as DITA-compatible resources and thus reference and use them from DITA maps, similar to how DITA XML topics are referenced and used.

The XSLT/XQuery support comes with new updates and improvements. The latest Saxon 11 update brings new extension functions and other features for XSLT and XQuery transformations and debugging, and validation and transformation support was added for XSLT 4.0 documents.

The JSON feature was improved by adding support for editing and validating using the latest JSON Schema version 2020-12. All the JSON tools where also updated to support the latest schema version. The visual JSON Schema diagram was now comes with new search and refactoring actions.

Support was added for working with OpenAPI, AsyncAPI, JSON-LD documents. The OpenAPI Documentation tool was redesigned to make it easier to read and understand the OpenAPI specification. The OpenAPI Tester tool was improved and comes with support to run test scenarios.

The performance when working with DITA was improved, as large maps and topics are now opened more quickly by having content references and included content expanded on-demand. The DITA map validation tool automatically validates topics that reference Relax NG schemas and it also detects if a related link points to a topic that is not included in the current map.

DITA publishing benefits from performance improvements, you can generate Google Structured Data in WebHelp output, and you can now generate PDF/A-compliant PDFs in CSS-based PDF output.

The Git Client, Batch Documents Converter, and Terminology Checker add-ons received lots of improvements, a new command-line script can be used to validate files or directories, and as usual, this release includes new API entry points, various bug fixes, and component updates.

There are changes in:

DITA Authoring

Modified Maps in the DITA Maps Manager are Automatically Saved

By default, local DITA maps that are edited in the DITA Maps Manager are automatically saved whenever a modification is made. The Automatically save local DITA maps after each modification option in the DITA → Maps preferences page can be deselected to disable this feature.

Improvements for Working With DITA-Compatible Resources

Various improvements have been added to enhance your experience when working with DITA-compatible resources (Word, Excel, OpenAPI, HTML, Markdown) that are referenced in DITA maps and dynamically published:
  • The possibility to insert a topic reference to a DITA-compatible resource in the DITA Maps Manager.
  • The title for each referenced resource is presented in the DITA Maps Manager.
  • When inserting topic references, cross references, or content references to content inside DITA-compatible documents, the insertion dialog box presents a list of DITA-specific IDs from the target document.
  • Utilizing the Validate and Check for Completeness action, DITA-compatible documents that are referenced in the DITA map are now converted to DITA topics in the background and validated the same as any other DITA topic.
  • When transforming DITA maps that have DITA-compatible documents referenced, the transformation converts the documents to normal DITA output on the fly.
Improvements for Working With DITA-Compatible Resources

Expand Map and Topic References On Demand

If the Display referenced content option is not selected in the Author preferences page, when a DITA map is opened in the main editor area in the Author visual editing mode, references to topics or sub-maps can be expanded on demand by clicking the small expansion button located on each element that contains such a reference. If the Allow referenced content to be edited option is selected, referenced topics and sub-maps that are expanded on-demand can also be edited directly.

Expand Content References On Demand

When opening a topic in the main editor area in the Author visual editing mode, content references and content key references can now be expanded on demand by clicking the small expansion button located on each element that contains such a reference (in the main editor area). This functionality is enabled if the Display referenced content option is not selected in the Author preferences page.

Easy Access to DITA Metrics Report

A new Generate Metrics Report action was added to the toolbar in the DITA Maps Manager and in the DITA Maps menu. It generates a metrics report that contains useful statistics for the current DITA map (e.g. the number of maps/topics, content reuse percentages, the number of elements/words/characters, processing instructions, external links, and more).
Easy Access to DITA Metrics Report

Define Conditional Profiling Attribute Groups in a Subject Scheme Map

It is now possible to contribute conditional profiling attribute groups by defining them in a subject scheme map. For more details and an example, see Defining Conditional Profiling Attribute Groups in a Subject Scheme Map.

New Action in DITA Reusable Components View Makes it Easy to Insert Images Inside Figures

In the contextual menu of the DITA Reusable Components view, a new action (Insert as Figure) was added that saves you some steps when inserting images inside figures. It is available if the selection is an image and it inserts the selected image inside a figure element (<fig>) with an empty <title> element.
New Action in DITA Reusable Components View Makes it Easy to Insert Images Inside Figures

Performance Improvements When Opening DITA Maps

Various speed improvements were implemented for opening large DITA maps in the DITA Maps Manager or opening large maps in the editor with all the referenced topics resolved.

Enable Inline Insertion Actions in DITA Maps

A new Inline insertion actions CSS style is now available in the Styles drop-down toolbar menu when editing a DITA map in Author mode that makes it easier to insert new topic references. Enabling this style renders an insertion widget in locations in the map document where a new topic reference can be inserted.

Improvements for Editing DITA Open Toolkit Project files

To enhance the user experience when DITA Open Toolkit Project configuration files are edited in the Author visual editing mode, all includes now appear expanded in-place and each deliverable has a play button that can be used to publish it individually.
Improvements for Editing DITA Open Toolkit Project files

Drag and Drop Resource Improvements in the Text Editing Mode

When topic references from the DITA Maps Manager view are dragged and dropped inside a DITA topic open in the Text editing mode, specific DITA elements that contain either direct or key references to the dropped resources are now properly inserted.

Set the Type for Notes Using a New In-place Action

When a DITA topic contains a <note> element, an in-place pop-up action located next to the note type icon can be used to easily change the note type.
Set the Type for Notes Using a New In-place Action

Set the Syntax Highlight Language for Codeblocks Using a New In-place Action

When a DITA topic contains a <codeblock> element, an in-place pop-up action can be used to easily change or set a syntax highlight language (@outputclass attribute) for the code block content.
Syntax Highlights in Codeblocks Now Supported For New Content Types

DITA Preview for Markdown Documents More Permissive

When editing Markdown documents, the DITA preview pane is more permissive, allowing documents that start with a high heading level or where heading levels increase by more than one unit (the heading level skips one or more levels).

DITA Map Validation

Report Related Links Whose Target Topic is Not Referenced in the DITA Map

The DITA Maps Manager view's Validate and check for completeness action now reports related links defined in relationship tables whose target topics are not referenced in the DITA map when the Report links to topics not referenced in DITA maps option is selected.

Report Validation Errors for Relax NG based DITA Topics

The Validate and Check for Completeness action was improved to report validation errors according to the schema in Relax NG-based DITA topics even when the Batch validate referenced DITA resources option is not selected.

DITA Publishing

Dynamically Convert OpenAPI Documents to DITA During Publishing

The Dynamic Non-DITA Resource to DITA Converter now includes the option to convert OpenAPI documents (in either JSON or YAML format) to DITA during the publishing process.
Dynamically Convert OpenAPI Documents to DITA During Publishing

Generate Google Structured Data

You can generate Google Structured Data in DITA WebHelp Responsive output. Google uses structured data to better understand the contents of the page and display special search results in a Google Search. For details about how to do this, see How to Generate Google Structured Data.

Improved Publishing Speed

The speed of DITA transformations was improved when publishing from an Oxygen kit bundled with Java 17, or when using the Oxygen Publishing Engine from the command line using Java 9 or newer.

Syntax Highlights in Codeblocks Now Supported For New Content Types

Syntax highlights now appear in the output when publishing DITA <codeblock> elements that contain YAML, PowerShell, DTD, or CMD (Windows-style command script) content.

Default Validation Now Works on RNG-based Topics and Maps

By default, the publishing engine now reports errors if RNG-based topics or maps are invalid according to the associated schema.

Publish All Deliverables for a DITA OT Project File in Author Mode

When a DITA Open Toolkit project file is open in Author mode, there is now a play button next to the project file name that can be used to publish all deliverables specified in the file. While the transformation is running, the button turns into a stop button in case you need to terminate the process.

Make Documents PDF/A-Compliant

For CSS-based PDF transformations, a new pdf.archiving.mode transformation parameter can be used to make PDF documents archive-able. The possible values are: PDF/A-1a, PDF/A-1b, PDF/A-2a, PDF/A-2b, PDF/A-2u, PDF/A-3a, PDF/A-3b, PDF/A-3u. For more details, see How to Allow Document Archiving.

Filter Glossary to Show Only Referenced Entries in PDF Output

For CSS-based PDF output, a new filter.unused.glossentries parameter can be set to yes to filter the glossary to only display referenced glossary entries in the output. If the parameter is set to no (the default), all glossary entries are displayed.

Scaling in Image Maps Improved

When working with image maps, adding the @scale attribute on the <imagemap> element now scales the image and its areas in both WebHelp and PDF output.

DITA Questions/Answers

New Action to Insert Intent Question Within DITA Topic

A new action named Insert Intent Question is available in various menus (in the Insert submenus within the DITA menu, contextual menu, and a drop-down menu on the toolbar) and it can be used to insert a DITA intent question (inside the prolog section). The action inserts a question (that could be asked by a user) and its answer is found in the current topic.
New Action to Insert Intent Question Within DITA Topic

New Questions and Answers DITA Topic Type

You now have the possibility of creating a new DITA topic type named Questions and Answers (Relax NG). It is useful for creating frequently asked question documents that contain multiple question/answer groups. Such documents are used during the publishing process for creating Google Structured Content metadata.
New Questions and Answers DITA Topic Type

Author Visual Editing

Smart Editing in Author Mode Improved

The smart editing mechanism in Author mode was improved so that when you start typing in a location where text is not allowed, Oxygen will search for the closest applicable context that accepts text.

Expand xi:include References On Demand

A Display referenced content option found in the Author preferences page can be deselected to make it possible for xi:includes to be expanded on demand by clicking a small expansion button that is located next to each element that contains such a reference in the main editor area.
Expand xi:include References On Demand

Support for Custom Values for the 'list-style-type' CSS Property

The Author visual editing mode now renders custom string values for the list-style-type CSS property defined in the CSS for list items.

JSON

JSON Schema Version 2020-12 Support in Oxygen

Support was added for the latest JSON schema version 2020-12. This includes:
  • Validating JSON schemas version 2020-12 accordingly to the specification.
  • Content completion proposals when editing JSON schemas version 2020-12.
  • Validating JSON/YAML documents against a JSON schema version 2020-12.
  • Converting older JSON schemas to version 2020-12.
  • A specific framework that will allow you to edit JSON schema documents in Author mode.

JSON Schema in Document Type Configuration

You can now associate a JSON schema with a set of documents by defining it in the Document Type configuration dialog box. The associated schema will automatically be used for validation and content completion when opening a file that matches the particular document type. This allows users to create a framework for any type of JSON/YAML documents and automatically provide validation and content completion support based on the associate JSON Schema.

New Version for JSON Schema Documentation Generator Tool

A new version of the JSON Schema Documentation generator tool is available. This tool (available after installing the add-on) includes support to generate documentation for JSON schema version 2020-12 and 2019-09, as well as various fixes and improvements.
New Version for JSON Schema Documentation Generator Tool

JSON Instance Generator Tool Now Supports JSON Schema Version 2020-12 and 2019-09

The Generate Sample JSON Files tool now supports JSON schemas with the version 2020-12 and 2019-09. This means that it now handles properties such as: $defs, minContains, maxContains, prefixItems, dependentSchemas, unevaluatedItems, unevaluatedProperties.

Generate JSON Schema Tool Now Supports JSON Schema Version 2020-12

You can now generate a JSON schema version 2020-12 from a JSON instance using the Generate JSON Schema tool.

New JSON Schema Converter Tool

A new Convert JSON Schema action is now available in the Tools->JSON Tools menu. It provides a simple tool for converting older versions of JSON schema documents to the latest versions (Draft 2019-09 or Draft 2020-12).
New JSON Schema Converter Tool

Content Completion Improved for Pattern Properties

The content completion support was improved for JSON documents based on the JSON schema when pattern properties are used. Oxygen now determines the definition to be used in the content completion even if the pattern property does not match the property exactly.

Multi-Line Values Now Allowed in Author Mode

Multi-line values are now allowed and preserved when editing JSON schema documents in the Author visual editing mode. Previously, if you edited values that contained a new line character (\ n) and then switched to Author mode, the values were not preserved.

JSON Schema Design

JSON Schema Version 2019-09 and 2020-12 Now Supported

Support was added for the latest JSON schema versions (Draft 2019-09 and Draft 2020-12) in Design mode. This includes automatic detection of the version, validation, contextual menu actions were updated with the new components, and the Palette view was updated to include the new components.
JSON Schema Version 2019-09 and 2020-12 Now Supported

Search and Refactoring Actions Added in JSON Schema Design Mode

New search and refactoring actions were added in the contextual menu of the JSON schema Design mode to improve the handling of JSON definition type components. The new actions are:
  • Search References - Searches all references of the selected definition in a scope determined by the schemas referenced in the file and the main schemas declared in validation scenarios.
  • Search References in - Searches for all references of the selected definition in a defined scope.
  • Search Occurrences in file - Searches all occurrences of the currently selected definition in the current file.
  • Rename Component in - Allows you to rename the selected component name. You can preview the files being affected and these files are identified by searching the references of the selected component in the scope provided.
  • Extract definition in another file - Extracts a definition to a new file. If the file does not already exist, the action will create a new file. If the file does exist, the action will find a corresponding group (or create one) to append the extracted definition.

JSON Schemas Now Support using a Reference ($ref) in Conjunction with Other Keywords

When building a JSON schema, you can now use a reference ($ref) in conjunction with other type-specific keywords (such as properties or items) for stricter validation.

Containers Now Automatically Created When Dragging From Palette View to JSON Schema Design Editor

When dragging and dropping a property/definition or pattern property from the Palette view to the JSON schema editor, if the component does not have the corresponding group component (properties, definitions, patternProperties), it will automatically be created.

OpenAPI/AsyncAPI/JSON-LD

Edit and Validate OpenAPI Documents

Oxygen now offers built-in support for automatic validation, content completion, and editing OpenAPI documents (versions 2.0, 3.0, and 3.1) in Text or Author mode. This is based upon the OpenAPI specification JSON schema associated with each of the three versions. New document templates are also available for OpenAPI documents. For more details, see OpenAPI (Swagger) Document Type (Framework).

Edit and Validate AsyncAPI Documents

Specific support for AsyncAPI documents is now provided with the addition of a new framework. This includes support for content completion, automatic validation, and editing AsyncAPI documents in Text or Author mode. New document templates are also available for AsyncAPI 1.x and AsyncAPI 2.x documents. For more details, see AsyncAPI Document Type (Framework).

Support for JSON-LD Documents

A specialized framework was added for working with JSON-LD files. This support includes automatic validation, new document templates, the content completion mechanism offers valid proposals for these types of documents, and when editing these types of documents, you have access to the various editing features and actions that are available for normal JSON documents. For more details, see JSON-LD Document Type (Framework).

New Version for OpenAPI Documentation Generator

The OpenAPI Documentation Generator tool can be used for generating documentation for OpenAPI documents in HTML format, including annotations and cross references. Various improvements where added in the new version:
  • Redesign - The documentation output has a new design to make it easier to read and understand the OpenAPI specification.
  • OpenAPI 3.1 Support - Support was added to generate documentation for OpenAPI 3.1 documents.
  • Supports for YAML Files - The input file used for generating the documentation can be in either YAML or JSON format.
New Version for OpenAPI Documentation Generator

New Version for OpenAPI Tester

Various improvements were made to the OpenAPI Tester add-on:
  • A new Run OpenAPI Test Scenario tool is available in the Tools->JSON Tools menu. It provides you with the capability of running a test suite for an OpenAPI document.
  • Syntax highlights are now rendered in the Request body and Response area to help make the code more readable.
  • Undo/redo support was added in the Request body and Response area.
New Version for OpenAPI Tester

New OpenAPI Test Scenario Framework

A new framework for OpenAPI test scenario files was added. This helps you to create and edit test scenarios more easily by offering automatic validation, content completion, and a visual editing interface in the Author visual editing mode.

New Author Mode CSS Style to Render Markdown Syntax Highlights for OpenAPI and AsyncAPI Documents

When editing OpenAPI or AsyncAPI documents in Author mode, a new Markdown Syntax Highlight CSS style can be selected from the Styles drop-down menu (available on the toolbar). It makes it easier for you to visualize descriptions with Markdown style syntax highlights.

XSLT/XQuery

XSLT Transformation and Debugging

The Saxon built-in XSLT processor used for XSLT transformations and debugging has been updated to version 11.4. The Saxon 11 release is currently considered as the most stable and reliable release. For the complete list of changes see https://www.saxonica.com/documentation11/#!changes.
XSLT Transformation and Debugging

XQuery Transformation and Debugging

Updated the Saxon XQuery processor used for XQuery transformations and debugging to version 11.4.

New Saxon Extension Functions

Saxon added more extension functions that are now supported and included in the list of proposals of the content completion assistant. Some examples include: saxon:analyze-uri($string), saxon:characters($string), saxon:EQName($string), saxon:in-scope-namespaces($element), saxon:array-member, saxon:function-annotations, saxon:new-element, and many more. For details, see https://www.saxonica.com/documentation11/index.html#!functions/saxon.

Dropped Saxon Functions

The saxon:path() function has been dropped, but you can use the standard fn:path() function instead. The undocumented and untested functions saxon:pause-tracing() and saxon:resume-tracing() have also been dropped.

Syntax Highlights for xsl:package Improved

Syntax highlights are now rendered in text value templates when used inside the xsl:package element.

Template Priority Added in Index for XSLT Stylesheet Documentation Generator

When using the XSLT Stylesheet Documentation generator tool, the priority of the template is now generated in the template reference from the index (that is also sorted by priority).

XSLT 4.0 Support

Validation and transformation support was added for XSLT 4.0 documents. Also, the content completion assistant now includes proposals for XSLT 4.0 elements, attributes, and XPath functions.

Add-ons

A variety of add-ons are available for Oxygen that extend the functionality of the application.

Semantic Versioning For Add-ons

The version defined for an add-on in the XML descriptor file can now have either the usual MAJOR.MINOR.PATCH form or the semantic version form (MAJOR.MINOR.PATCH-PRE_RELEASED_VERSION), making it easier for developers to create add-on builds for pre-release versions.

Git Client Improvements

Some improvements were made to the Git Client add-on:
  • A new Validate each file before committing option was added in the Git Client preferences page. Selecting this option enables automatic validation of each file before each commit.
  • A new Validate all files from the project's "Main Files" folder before pushing option was added in the Git Client preferences page. Selecting this option enables automatic validation of the files located in the Main Files folder before the push operation processes.
  • The integrated JGit library was upgraded to version 6.3, which brings support for ssh-agent forwarding.

For a complete list of updates added in the Git Client, see https://github.com/oxygenxml/oxygen-git-plugin/releases.

Batch Documents Converter Improvements

Various improvements were made to the Batch Documents Converter add-on:
  • You can now convert JSON or YAML files that use and conform to the OpenAPI specification (versions 2.0, 3.0, or 3.1) to DITA documents and there is a Create DITA maps from OpenAPI documents option that can be selected to instruct the converter to split the documents into separate topics that are referenced in a DITA map.
  • Word to DITA or HTML conversion improvements:
    • The Word styles mapping configuration was improved by inheriting the style configuration of the custom style from the base style.
    • SVG images embedded in Word documents are preserved as SVG.
    • IDs that result from image and table bookmarks are now handled better to find the correct location.
    • IDs generation was improved for topics and sections by using the text from headings.
    • Handling of tables was improved by preserving header row information during the conversion when converting Word to DITA or HTML.
  • For HTML to DITA conversions:
    • Conversion of object elements from HTML was improved by adding a proper @outputclass attribute in the DITA result.
    • An option was added in the conversion dialog box that allows you to decide whether or not the <div> elements will be ignored.
  • For Markdown to DITA conversions, support was added for Markdown abbreviations.
  • For HTML to XHTML conversions, the formatting of <pre> elements is prevented.

Terminology Checker Improvements

Various improvements were added to the Terminology Checker add-on:
  • XPath Context - You can define simple XPath expressions for particular defined rules to match or skip specific elements.
  • Part of Speech Tagging - When scanning for terminology problems, the problem is presented only if the term's part of speech matches the one specified in the defined rule (available only for the English language).
  • Phases - In the terminology configuration file, you can set the phase in which incorrect terms are detected (editing/validation/always). Performance improvements were also implemented when checking files.
  • Load Terms Provided by Other Add-ons - Any Oxygen add-on (plugin) can now contribute terminology files to be used by the Terminology Checker. The contributed terminology files will be loaded and used if the contributor add-on is enabled. For more details, see Terminology Files Contributed from Other Oxygen Add-ons.
Terminology Checker Improvements

Scripting

The all platforms distribution of Oxygen is bundled with a scripts sub-folder that contains scripts for automating and running various utilities from a command line interface. To run any of these scripts, you need to purchase a scripting license.

New Command Line Launcher for Validating Files or Directories

It is now possible to validate files or directories from a command line interface. You can check that your documents are valid from an integration server and you can generate reports in several formats (text, XML, JSON, or an HTML visual format). For more information, see the Validate Command Line Script topic in the user guide. The scenarios and configurations that you use to validate files from Oxygen can be used from a command line script:
  • You can specify a certain schema file to validate against.
  • You can validate using the schema(s) that are internally associated within files.
  • You can validate using the default Oxygen validation scenarios for respective file types.
  • You can specify a validation scenario name to be referenced from either a scenarios file or a project file.

Batch Convert OpenAPI Documents to DITA

The Batch Converter script now includes the option to convert multiple documents from OpenAPI to DITA.

Other

Syntax Highlights in DocBook 'programlisting' Element Now Supported For New Content Types

Syntax highlights now appear in Docbook-based WebHelp Classic output when publishing <programlisting> elements that contain JSON, XQuery, YAML, PowerShell, DTD, or CMD (Windows-style command script) content.

Basic Editing Support and Syntax Highlights Added for PowerShell Files

Basic editing support and syntax highlights are now provided for working with PowerShell files in Oxygen.

Folders can be Added to the Main Files Directory

Normal folders can now be added to the Main Files directory when the Main Files Support is enabled. Previously, only logical folders and files could be added.

Control Indentation in Code Blocks

It is now easier to add indentation in code blocks by using the Tab or Shift+Tab keyboard shortcuts.

XPath in Files Speed Improvements

The speed for the XPath in Files mechanism was greatly improved when running XPath over XML documents with associated DTDs, XML Schema, or Relax NG Schemas.

Component Updates

Java 8 is No Longer Supported

Starting with Oxygen version 25.0, Java 8 is no longer officially supported. Java 11 is now the minimum officially supported version.

Windows 11 Support

Starting with Oxygen version 25.0, the Windows 11 operating system is officially supported.

OpenJDK 17.0.4.1

The version of OpenJDK that is bundled with the installation kits for providing the Java Runtime Environment was updated to version 17.0.4.1 from Eclipse Adoptium.

OpenJDK Distribution Runs on Both Intel Macs and Apple Silicon Macs

The OpenJDK distribution of Oxygen for macOS is now universal, as the same distribution now runs on both Intel Macs and Apple Silicon Macs.

Windows ZIP Distribution Bundles 64-bit JRE

The Windows ZIP distribution of Oxygen XML Editor/Author/Developer now bundles the 64-bit version of the OpenJDK (17+) JRE. Previously, the Java 8u202 32-bit version was bundled.

Eclipse 4.25

Updated the Eclipse plugin to support version 4.25.

Eclipse 4.5 is Now the Minimum Required Version

The Eclipse plugin now requires a minimum of Eclipse version 4.5.

Deprecated Support for the MathFlow Integration

Support for using MathFlow when rendering and editing MathML equations in the Author visual editing mode is officially deprecated. It will be replaced soon by a new integration with MathType, developed by Wiris.

DITA OT 3.7.3

The DITA Open Toolkit version that is bundled with Oxygen has been updated to version 3.7.3.

TEI Schemas 4.4.0

Updated the bundled TEI schemas to version 4.4.0.

TEI Stylesheets 7.53.0

Updated the bundled TEI XSLT stylesheets to version 7.53.0.

Apache FOP 2.7

Updated the Apache FOP library to version 2.7.

Apache Batik 1.15

Updated the Apache Batik toolkit to version 1.15.

Calabash 1.5.1-110

Updated the Calabash engine to version 1.5.1-110.

Everit 1.14.1

Updated the JSON Schema Validator library from Everit to version 1.14.1.

Jackson 2.13.2

Updated the third-party Jackson libraries to version 2.13.2 to help prevent vulnerability issues. Specifically, the jackson-annotations, jackson-core, and jackson-dataformat-yaml libraries were updated to version 2.13.2 and the jackson-databind library was updated to version 2.13.2.2.

JSON-Java 20220320

Updated the JSON-Java (org.json) package to version 20220320.

Saxon 11.4

Updated the built-in Saxon processor that is used for XSLT and XQuery transformations and debugging to version 11.4.

XML Resolver 4.5.0

Updated the XML Resolver component to version 4.5.0.

Saxon SQL 11.4

Updated the saxon-sql library to version 11.4.

Saxon XSLT and XQuery Transformer Add-on Updated to Version 10.8

The Saxon 10 transformer add-on was updated to version 10.8. This allows you to validate and transform XSLT and XQuery documents with the Saxon 10.8 engine.

Xerces XPath 2.0 Processor 1.2.1

Updated the Xerces XPath 2.0 processor to version 1.2.1.

Mozilla Rhino 1.7.14

Updated the Mozilla Rhino JavaScript engine to the latest stable 1.7.14 version.

XProc Calabash 1.5.0

The XProc Calabash engine has been updated to version 1.5.0 for Saxon 11.

SnakeYAML 1.31

The SnakeYAML library was updated to version 1.31.

API

Display Syntax Highlights for Various Code Languages

A new API method (OxygenUIComponentsFactory.createTextArea()) was added for creating a custom Swing JTextArea-based component that can be used to display syntax highlights for various code languages. The OxygenUIComponentsFactory.changeContentType() method can be used to change the syntax highlight type for a previously created text area.

Validate Certain XML Resources

A new addition is represented by the PluginWorkspace.getValidationUtilAccess() API method that can be used to validate and return validation problems for an arbitrary list of resources.

Obtain List of Main Files

ProjectController.getMainFileResourcesIterator() is a newly added API method that can be used to obtain the list of resources placed in the project's Main Files folder.

Author Operations to Start and Stop Transformation Scenarios

The new ExecuteCustomizableTransformationScenarioOperation and StopCurrentTransformationScenarioOperation predefined Author operations allow you to start a transformation scenario with a set of custom parameters or to stop a running a transformation scenario.

Access to Author Content as Char Sequence

A new API method (AuthorDocumentController.getContentCharSequence) was added to allow access to the char sequence that contains all text nodes and marker characters from the Author visual editing mode.

Create Editor Panes

The OxygenUIComponentsFactory.createHTMLEditorPane(String, boolean) API method was added to allow you to create an editor pane capable of rendering HTML code that looks similar to the panes implemented in Oxygen.