Add-ons

Oxygen version
CG
CGM support
by Syncro Soft
Version 1.1.0
Oxygen Version: 18.0+
Contribute jcgm library to Oxygen which make it possible to render CGM images in Author mode. This product includes software developed in part by support from the Defense Advanced Research Project Agency (DARPA). ...
Read More
DI
DITA Translation Package Builder
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.0+
This add-on contributes contextual menu actions that help you build a translation package for DITA files that can be sent to translators. You can also extract the changed files back into your project once you receive the package back from the translators. It contributes a sub-menu named "Translation Package Builder" in the DITA Maps Manager 's contextual menu. The actions present in this group are: Generate Milestone - this action is the first one to use. It will generate an unique hash for each documentation resource. This information will be used by the second action to detect which files have been modified. A milestone file should be generated the first time you install this plugin and, afterwards, after each package sent to translators. Create Modified Files Package - this action detects which files have been changed since the last generated milestone. These files are packed insdie a ZIP file that can be send to translators. After doing this you can also generate a new milestone so that the next package will contain just the new changes. This action also creates a report with the modified resources ( modified_resources_report.xhtml ). If your translation agency is DITA-aware you can opt to send him the entire DITA project together with this report. Apply Package - when the translated files arrive from the translator you should open the DITA map that corresponds to the received language (open dita-map-french.ditamap if the package contains the french translation). Invoking this action will extract the changed files inside map's directory.
Read More
DI
DITA References View
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.0+
Side view in Oxygen XML Editor which shows all outgoing references (image references, links, content references) for the current opened DITA topic. For more details see https://github.com/oxygenxml/oxygen-dita-outgoing-references-view What's new in version 2.0.1 Incoming references are now grouped into three categories: Map, Cross, and Content. You can copy the location of the reference target by using Ctrl/Cmd+C on the reference. Fixed an issue where an infinite incoming reference loop was created when a peer map reference was used. What's new in version 2.0.0 Added a new tab where incoming references are presented for the current DITA topic (Oxygen 23 or newer). Added support for translating the view's user interface in English, German, French, Japanese, or Dutch. Fixed various small bugs.
Read More
JS
JSON Schema Validator (json-sKema)
by Syncro Soft
Version 1.1.0
Oxygen Version: 26.0+
This add-on contributes a JSON Schema Validator that can be used for validating JSON documents against Draft 2020-12 JSON schemas. The validation engine is based on json-sKema library (https://github.com/erosb/json-sKema). To use the validator, you need to create a validation scenario by selecting the Configure Validation Scenario(s) from the Validation toolbar drop-down menu, or from the Document > Validate menu (or the Validate submenu when invoking the contextual menu on ...
Read More
Sa
Saxon 11.5 XSLT and XQuery Transformer
by Syncro Soft
Version 11.6.0
Oxygen Version: 26.0+
This plugin installs an external Saxon 11.6 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 11.6. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possibilities to use Saxon 11.6 for validating XSLT: To set Saxon 11.6 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 11.6 (External) as the validation engine.. If you prefer to use Saxon 11.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 11.6 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 11.6 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 11.6 allows one to export the compiled form of a stylesheet as a JSON or as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possibilities to use Saxon 11.6 for validating XQuery: To set Saxon 11.6 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 11.6 (External) as the validation engine.. If you prefer to use Saxon 11.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 11.6 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 11.6 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon-sql-11.jar that is located in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
MS
MS Writing Style Guide Vale Rules
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.0+
MS Writing Style Guide Vale Rules based on the "Microsoft Writing Style Guide" for the "Terminology Checker" add-on IMPORTANT! The "Terminology Checker" add-on must also be installed in order for this add-on to work. This add-on contributes Microsoft Writing Style Guide Vale rules for the Terminology Checker add-on. This add-on contains a Vale-compatible (https://github.com/errata-ai/vale) implementation of the Microsoft Writing Style Guide (https://learn.microsoft.com/en-us/style-guide/welcome/) as provided by the errata-ai's open source project https://github.com/errata-ai/Microsoft. Please note that this project is neither maintained nor endorsed by Microsoft. Microsoft is a trademark of the Microsoft group of companies. Software from the following projects is included: errata-ai/Microsoft Site: https://github.com/errata-ai/Microsoft License: MIT License (https://github.com/errata-ai/Microsoft/blob/master/LICENSE) Microsoft Writing Style Guide Site: https://docs.microsoft.com/en-us/style-guide/welcome License: Creative Commons Attribution 4.0 International (https://github.com/MicrosoftDocs/microsoft-style-guide/blob/master/LICENSE)
Read More
Sa
Saxon 9.9 XSLT and XQuery Transformer
by Syncro Soft
Version 24.1.0
Oxygen Version: 24.1+
This plugin installs an external Saxon 9.9 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 9.9. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 9.9 for validating XSLT: To set Saxon 9.9 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 9.9.1.8 (External) as the validation engine.. If you prefer to use Saxon 9.9 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 9.9.1.8 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 9.9.1.8 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 9.9 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 9.9 for validating XQuery: To set Saxon 9.9 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 9.9.1.8 (External) as the validation engine.. If you prefer to use Saxon 9.9 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 9.9.1.8 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 9.9.1.8 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon9-sql.jar that is located in [OXYGEN_INSTALL_DIR]/lib/ or [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
XS
XSD to JSON Schema Converter
by Syncro Soft
Version 25.0.2
Oxygen Version: 25.0+
Oxygen XML Editor provides a tool for converting an XML Schema file (XSD) to a JSON Schema file. The XSD to JSON Schema action for invoking the tool can be found in the Tools > JSON Tools menu. It requires an additional add-on to be installed, so the first time you invoke the action, Oxygen XML Editor will present a dialog box asking if you want to install it. ...
Read More
Sa
Saxon 9.6 XSLT and XQuery Transformer
by Syncro Soft
Version 24.1.0
Oxygen Version: 24.1+
This plugin installs an external Saxon 9.6 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 9.6. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. The Saxon 9.6 XSLT and XQuery Transformer plugin does not work with XQuery 3.1. If possible, you can use the 9.7 or 9.8 plugin instead. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 9.6 for validating XSLT: To set Saxon 9.6 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 9.6.0.10 (External) as the validation engine.. If you prefer to use Saxon 9.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 9.6.0.10 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 9.6.0.10 (External) as the engine and associate it with the stylesheet. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 9.6 for validating XQuery: To set Saxon 9.6 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 9.6.0.10 (External) as the validation engine.. If you prefer to use Saxon 9.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 9.6.0.10 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 9.6.0.10 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon9-sql.jar that is located in [OXYGEN_INSTALL_DIR]/lib/ or [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Va
Vale Validation
by Syncro Soft
Version 1.0.0
Oxygen Version: 20.0+
Setup Download and unzip the proper Vale executable for your OS. On Linux and Mac, you need to give executable permission to the Vale executable. You can do this by opening a console in the Vale directory and running: chmod u+x vale Go to Options -> Preferences..., go to the plugin's preferences page (Plugins / Oxygen Vale Validation) and specify the path to the previously downloaded Vale executable. In the same preferences page you can also specify a path to a Vale configuration file (.vale.ini). Vale auto detects this file by looking 6 levels up in the current file's ancestor directories, but you can also impose one. Vale Styles Vale uses collections of individual YAML files (or "rules") to enforce particular writing constructs. These collections are referred to as styles and are organized in a nested folder structure at a user-specified location. The .vale.ini file is where you'll control the majority of Vale's behavior, including what files to lint and how to lint them. Vale auto detects .vale.ini, but you can also specify the path to .vale.ini from the plugins preferences page (Options -> Preferences..., page Plugins / Oxygen Vale Validation ). Third-party styles Vale has a growing selection of pre-made styles available for download from its style library.
Read More
Op
OpenAPI Documentation Generator
by Syncro Soft
Version 3.0.0
Oxygen Version: 26.0+
This add-on is used for generating documentation for OpenAPI (https://spec.openapis.org/oas/v3.0.3) components in HTML format, including annotations and cross references. The documentation displays information about the servers, paths, components and tags defined in the OpenAPI documents and it is presented in a visual diagram style with various sections, hyperlinks, and filtering options. What's new in version 3.0.0 An option was added to transform the OpenAPI content into PDF output. What's ...
Read More
Sa
Saxon 9.8 XSLT and XQuery Transformer
by Syncro Soft
Version 24.1.0
Oxygen Version: 24.1+
This plugin installs an external Saxon 9.8 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 9.8. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 9.8 for validating XSLT: To set Saxon 9.8 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 9.8.0.15 (External) as the validation engine.. If you prefer to use Saxon 9.8 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 9.8.0.15 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 9.8.0.15 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 9.8 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 9.8 for validating XQuery: To set Saxon 9.8 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 9.8.0.15 (External) as the validation engine.. If you prefer to use Saxon 9.8 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 9.8.0.15 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 9.8.0.15 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon9-sql.jar that is located in [OXYGEN_INSTALL_DIR]/lib/ or [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Terminology Checker
by Syncro Soft
Version 4.1.1
Oxygen Version: 22.0+
Terminology Checker This add-on contributes a terminology checker to Oxygen XML Editor/Author. What's new in version 4.1.1 Improved sentences detection for Vale rules. What's new in version 4.1.0 Security/Component Update: The SnakeYAML library was updated to version 1.31 - CVE-2022-25857 Any Oxygen add-on can contribute terminology files that will be used by the Terminology Checker. The contributed terminology files will be loaded and used if the contributor add-on is enabled. Extended support for Vale occurrence extension point, by implementing the sentence scope. Added an option that stops presenting errors related to Vale rules (such as unsupported extension points or invalid properties) in Results view. Updated colors in Terminology Checker view for better experience with Graphite theme. Fixed an issue that could cause contextual menu to became to large. Fixed an issue that caused the Terminology Checker view to became to large. What's new in version 4.0.0 XPath context: 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 on the defined rule (available only for the English language). Phases: Set in the terminology configuration file the phase in which incorrect terms are applied: always/editing/validation. Performance improvements when checking files. The feature marked with * are available from Oxygen 24.1 build 2022062007 and newer. What's new in version 3.0.0 Actions to check terminology for multiple selected resources are now available in the DITA Maps Manager and Project view contextual menus.* Terminology Checker can be used as a Validation Engine when creating Validation Scenarios. This allows a validation scenario applied when editing content or when batch validating resources in the Project view to contain a terminology checking stage.* The Terminology Checker preferences page can be saved at project level.* Added a setting (checked by default) to preserve the case (capitalization) when matches are replaced. Added support for Vale Conditional and Repetition extension points. Specify the language for which the terms should be applied in an XML terminology file by using the lang attribute on the incorrect-terms root element. Added in the XML terminology file the possibility to specify a link for each incorrect term. The link can point to a web page where more details are available for the rule and is presented in the Terminology Helper side view and when hovering the highlighted problems. The Terminology Helper side view has been redesigned for better interaction. Avoid presenting problems in read-only elements and in content deleted with Track Changes. Many bug fixes and small improvements. The features marked with * are available from Oxygen 24.0 and newer. What's new in version 2.0.1 Performance improvements when checking large files. Fixed an unhandled exception that appeared when a terminology rule's message doesn't exist. What's new in version 2.0.0 Load Vale files from yml files and highlight matching rules. Side view that gives an overview of the terminology problems. Clicking in the side view on the incorrect term will focus the matching term in Editor. Use capturing groups in the suggestions and messages in your custom term rules using the term match regular expression. Share favorite rules with the team: define a folder oxygen-term-checker in the root of your project and terms will be automatically loaded, without defining another terms directory in plugin's Preferences page. Match user defined custom terms at word level, character or write a regular expression. Insert suggestion value as plain-text or as XML fragment. Set severity of custom incorrect terms. Configure highlight colors and decoration of matching terms. Quickly enable/disable add-on from the tool bar without restarting Oxygen. Version 1.0.1: Add-on highlights matched terms in the Author visual editing mode Right click the highlights to access various actions allowing you to replace each individual highlight with suggestions or to apply the same suggestion in multiple places in the opened document How to start: Load Vale terminology files or use the File / New dialog wizard to create a new Terminology File, edit that file and add mappings between matched terms and their suggested replacements Go to the Preferences / Plugins / Terminology Checker page and refer in the Terminology Folder text field to that folder where your terminology files are located The incorrect terms which have been previously configured should now be highlighted in current editor in the Author visual editing mode
Read More
Do
DocBook Validate and Completeness Check
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.0+
This add-on contributes a toolbar button that provides the ability to validate DocBook files. It reports issues such as broken internal and external links, problems with images, or profiling conditions that conflict with profiling preferences. For more details, see: https://github.com/oxygenxml/oxygen-docbook-validate-check-completeness
Read More
AS
ASD Simplified Technical English Specification Writing Style Guide Rules
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.0+
ASD Simplified Technical English Specification (ASD-STE100) Writing Style Guide Rules for the "Terminology Checker" add-on IMPORTANT! The "Terminology Checker" add-on must also be installed in order for this add-on to work. This add-on contributes ASD Simplified Technical English Specification (ASD-STE100) rules for the Terminology Checker add-on. This project is neither maintained nor endorsed by ASD. This repository contains a compatible implementation of the ASD Simplified Technical English Specification (ASD-STE100). Software from the following projects is included: ASD-STE100 Site: https://asd-ste100.org License: ASD Simplified Technical English, ASD-STE100, is a Copyright and a Trade Mark of ASD, Brussels, Belgium.
Read More
Sa
Saxon 12.4 XSLT and XQuery Transformer
by Syncro Soft
Version 12.4.0
Oxygen Version: 26.0+
This plugin installs an external Saxon 12.4 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 12.4. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possibilities to use Saxon 12.4 for validating XSLT: To set Saxon 12.4 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 12.4 (External) as the validation engine.. If you prefer to use Saxon 12.4 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 12.4 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 12.4 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 12.4 allows one to export the compiled form of a stylesheet as a JSON or as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possibilities to use Saxon 12.4 for validating XQuery: To set Saxon 12.4 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 12.4 (External) as the validation engine.. If you prefer to use Saxon 12.4 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 12.4 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 12.4 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon-sql-12.jar that is located in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Sa
Saxon 10.7 XSLT and XQuery Transformer
by Syncro Soft
Version 10.9.0
Oxygen Version: 26.0+
This plugin installs an external Saxon 10.9 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 10.9. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possibilities to use Saxon 10.9 for validating XSLT: To set Saxon 10.9 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 10.9 (External) as the validation engine.. If you prefer to use Saxon 10.9 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 10.9 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 10.9 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 10.9 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 10.9 for validating XQuery: To set Saxon 10.9 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 10.9 (External) as the validation engine.. If you prefer to use Saxon 10.9 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 10.9 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 10.9 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon-sql-10.jar that is located in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
JS
JSON Schema Documentation Generator
by Syncro Soft
Version 4.1.0
Oxygen Version: 25.0+
An Oxygen XML Editor plugin used to generate the documentation for JSON Schema. ...
Read More
Tr
Translator Helper
by Syncro Soft
Version 1.1.1
Oxygen Version: 21.0+
This add-on contributes a Translator Helper to Oxygen XML Editor/Author. Features: You can translate content using Google Translate or DeepL Translator to various languages: Select the content to translate in the Author visual editing mode. You can also select the contents of the entire document. Right-click, select "Translate", and choose the target translator and language. Copy the translated content from the open web page. Click Replace in the Translate using Google Translate or Translate using DeepL Translator dialog box that appears. The original content is replaced with the translated content while the original element structure and attributes remain unchanged. In addition, you can choose to show the original document content in the Translator Helper side view. This will allow you to correct the translation further by looking at the original text and the translated text side-by-side. You can have your original content displayed side-by-side with the content that you are editing by right-clicking anywhere in the Author visual editing mode and selecting the Show current content in side view action. This helps you to translate the content more accurately. What's new in version 1.1.1 Fixed an issue where translating text with characters such as '%' and '#' did not work. What's new in version 1.1.0 The plugin was updated to allow using the DeepL Translator in addition to Google Translate for translating content.
Read More
Wr
Writer Helper
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.1+
This add-on contributes a side-view named 'Writer Helper' that contains various small tools intended to help technical writers: Review - You can select folders or files in the Project view and start a review session for them. This is useful for reviewing a set of documents. Similar content - You can select folders or files in the Project view, then choose a list of elements to check for similarity. This is useful for finding possible elements that can be reused instead of being copy-pasted between documents. Read Aloud - You can select content in the current document and use the Play button to listen to how it is read by the operating system's narrator. This is useful for those who want to review content by listening to it. Tips - You can view a list of editing tips, tuned for technical writers. This is useful for discovering productivity tips to make your editing experience more efficient and productive. More details about the add-on's functionality
Read More
Op
OpenAPI Tester
by Syncro Soft
Version 1.2.1
Oxygen Version: 25.0+
This add-on contributes a view in Oxygen that can be used as a testing tool for OpenAPI files (https://spec.openapis.org/oas/v3.1.0.html). The tool provides capabilities to easily inspect OpenAPI request-responses, and to make sure they work as expected. It is available for OpenAPI 3.x in both JSON and YAML format. The tester loads the selected OpenAPI document and automatically fills the corresponding fields. After clicking the Send button, it presents the ...
Read More
Ja
Java Classes Generator
by Syncro Soft
Version 24.1.0
Oxygen Version: 24.1+
Contributes JAXB-XJC library to Oxygen which makes possible the generation of Java classes from XSD files. The XJC compiler transforms a source XSD to a set of JAXB content classes in the Java programming language. It generates a class for each complex type and an additional factory class to ease the creation of JAXBElement representations. ...
Read More
Sa
Saxon 10.3 XSLT and XQuery Transformer
by Syncro Soft
Version 23.1.0
Oxygen Version: 23.1
This plugin installs an external Saxon 10.3 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 10.3. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 10.3 for validating XSLT: To set Saxon 10.3 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 10.3 (External) as the validation engine.. If you preffer to use Saxon 10.3 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 10.3 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 10.3 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 10.3 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 10.3 for validating XQuery: To set Saxon 10.3 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 10.3 (External) as the validation engine.. If you preffer to use Saxon 10.3 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 10.3 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 10.3 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon-sql-10.0.jar that is located in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Sa
Saxon 10.6 XSLT and XQuery Transformer
by Syncro Soft
Version 24.0.0
Oxygen Version: 24.0
This plugin installs an external Saxon 10.6 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 10.6. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 10.6 for validating XSLT: To set Saxon 10.6 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 10.6 (External) as the validation engine.. If you preffer to use Saxon 10.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 10.6 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 10.6 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 10.6 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 10.6 for validating XQuery: To set Saxon 10.6 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 10.6 (External) as the validation engine.. If you preffer to use Saxon 10.6 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 10.6 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 10.6 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon-sql-10.0.jar that is located in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Sa
Saxon 9.7 XSLT and XQuery Transformer
by Syncro Soft
Version 24.1.0
Oxygen Version: 24.1+
This plugin installs an external Saxon 9.7 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 9.7. Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported. XSLT Validation After installing the plugin, there are two possiblities to use Saxon 9.7 for validating XSLT: To set Saxon 9.7 as the default XSLT validation engine, go to XSLT Preferences and select Saxon-EE 9.7.0.21 (External) as the validation engine.. If you prefer to use Saxon 9.7 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE 9.7.0.21 (External) as the engine and associate it with whichever stylesheet you like. XSLT Transformation Create a Transformation Scenario that uses Saxon-EE 9.7.0.21 (External) as the engine and associate it with the stylesheet. XSLT Compile Saxon 9.7 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT. XQuery Validation After installing the plugin, there are two possiblities to use Saxon 9.7 for validating XQuery: To set Saxon 9.7 as the default XQuery validation engine, go to XQuery Preferences and select Saxon-EE XQuery 9.7.0.21 (External) as the validation engine.. If you prefer to use Saxon 9.7 just for some specific stylesheets, then you should create either a Validation Scenario or a Transformation Scenario that uses Saxon-EE XQuery 9.7.0.21 (External) as the engine and associate it with whichever stylesheet you like. XQuery Transformation Create a Transformation Scenario that uses Saxon-EE XQuery 9.7.0.21 (External) as the engine and associate it with the XQuery file. Performing Transformations with Data Extracted from a Database This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this: Add a copy of the database connector that is compatible with your database in [OXYGEN_INSTALL_DIR]/lib/ or in [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Restart the application. Run the transformation scenario. If this does not work, try the following: Create a transformation scenario (see sections above) and click the Extensions button. Added the database connector that is compatible with your database. Add saxon9-sql.jar that is located in [OXYGEN_INSTALL_DIR]/lib/ or [PLUGIN_INSTALL_LOCATION]/lib/ (you can go to Options->Preferences->Plugins to see where the plugin is installed). Run the transformation scenario.
Read More
Ox
Oxygen Content Fusion Connector
by Syncro Soft
Version 5.5.0
Oxygen Version: 23.1+
This add-on allows you to upload tasks that contain documents to be reviewed on the Oxygen Content Fusion collaboration platform. Reviewers can then login to Oxygen Content Fusion to review, add comments, or contribute changes to the uploaded documents. You also have access to a Merge tool that allows you to automatically merge the changes back into Oxygen. After installing the add-on, a new toolbar button (Show Content Fusion Tasks Manager View) will be available and clicking that button displays the Content Fusion Tasks Manager view where you can create the tasks to be uploaded to Oxygen Content Fusion. For more information, go to http://www.oxygenxml.com/content_fusion.html. Release Notes 5.5 Added the possibility to specify the original location of a task created using documents stored on a remote server (so that other owner than the one that created the task to be able to integrate the changes). Release Notes 5.4 Fixed an issue where the Get Changes action fails for tasks created using documents stored on a remote server if they contained absolute references. Release Notes 5.3 Fixed an issue where the "Add To Review Task" action was not added to the contextual menu when the "Oxygen Writer Helper" add-on was installed in the editor. A "Mark as integrated" action was added in the contextual menu of the Content Fusion Task Manager view that allows users to mark a task as integrated, hiding it from the list of tasks. A "Close review" action was added in the contextual menu of the Content Fusion Task Manager view that allows users to block the review for a task. A "Reopen review" action was added in the contextual menu of the Content Fusion Task Manager view that allows the user to reopen the review for a closed task. The "Integrating" and "Review closed" states are now shown on task cards. Improved the text messages and labels in the "Connection status" dialog box. A "Due Date" section was added inside the "New Task" box where users can set a deadline for when the review must be finished. A "cf-file"​ protocol can be used when a customizer wants to either control the file content before it is sent to Content Fusion or when it is saved in the original files after the ​"​Get Changes​ User" action is performed. Fixed an issue where the default Java 'charset' was used when updating files after the "Get Changes" action was invoked. Fixed an issue where some task files were wrongly identified as deleted locally, after a local base path for the task was provided. Release Notes 5.2.1 A DITAVAL file can now be easily added as a filter in the Content Fusion Tasks Manager view by simply dragging and dropping it from the DITA Maps Manager to the DITA Context area. Release Notes 5.2 Added the option to upload referenced files when no context DITA map is specified when creating a new task. This option is present in the upload panel and if enabled it uploads files that are directly referenced from the files to be reviewed. Referenced files are detected by looking for "href", "conref" and "conrefend" attributes but we don't look for "conkeyref" attributes. Release Notes 5.1 Content Fusion task files that are locked by another user are opened in the editor as read-only. When a Content Fusion task file editor becomes active, Oxygen automatically tries to regain the file lock and makes the editor editable if it acquires it. Fixed an issue where the Undo action was enabled in a Content Fusion task file that was in a read-only state. Fixed an issue where the editor tab displayed the old name of a Content Fusion task file after using the "Save As" action. Improved the message displayed in the "Connection status" dialog box to offer more information about the state of the connection. Renamed the "Open context DITA map" action in the contextual menu to "Edit context DITA map" since it more accurately describes the resulting action. Release Notes 5.0 It is now possible to open a file directly from a Content Fusion task. The file's URL can be copied from the browser and pasted in the dialog box presented when using the "Open URL" action that is available on the toolbar and in the File menu. A "Open context DITA map" action was added in the Content Fusion Task Manager view's contextual menu and it opens the DITA map specified as the context map for a task. The content of the "Connection status" dialog box was updated to offer more clear information about the server status. Release Notes 4.3.1 Fixed an issue where the logging mechanism no longer worked (a "NoSuchMethodError" warning was displayed in the console and in the generated log files). Release Notes 4.3 The SLF4J API is now used for logging instead of Log4j 2.x. A notification dialog box is displayed when there are read-only files that could not be updated by the "Get Changes" operation. Release Notes 4.2 Always ignore external resource exceptions when getting task changes. Release Notes 4.1 Added an option in the Preferences page to activate an alternate way to upload tasks. This option uploads files that are directly referenced from the files to be reviewed and all the detected DITA maps (starting from the context map). Referenced files are detected by looking for "href", "conref" and "conrefend" attributes but we don't look for "conkeyref" attributes. Release Notes 4.0 Tested and validated the compatibility of the plugin with Oxygen XML Editor/Author 23.1. Fixed a problem where a connection opened to the server was not properly closed. Added an option in the plugin preferences page to skip activity checks when refreshing tasks (for performance improvements). When this option is activated, the "Get Changes" action is presented on the task box but no activity information (comments and changed files count) will be available. Release Notes 3.1 Ensured the compatibility of the plugin with Oxygen XML Editor/Author 23.0 Moved the "Add File to Review Task" from the Author page contextual menu inside the "Review" submenu Removed the plugin from the Oxygen XML Editor/Author kit. Added actions on the "Review" toolbar, DITA Maps Manager and Author page contextual menus that can be used to install the plugin Release Notes 3.0 Ensured the compatibility of the plugin with Oxygen XML Editor/Author 22.1. Before integrating the changes from a task that was created on the server, you must specify a folder where the task files can be saved. Updated the filter buttons tooltips from "Get Changes" dialog to be more accurate. Release Notes 2.0.1 Before integrating the changes from a task that was created on the server, you must specify a folder where the task files can be saved. Release Notes 2.0 Introductory screen about Content Fusion, with details about the review workflow. You can now specify a custom DITAVAL to be used for profiling in DITA tasks. Current DITAVAL is automatically set when a new DITA task is created. Added a mechanism that detects resource references within the files to review. You can choose to include the referred resources to the task. You can save new files added by reviewers on a task created from documents stored on a remote server. Fixed a problem where the editor blocked while using the Content Fusion connector. Updated the libraries used by the plugin. Release Notes 1.0.7 Modified the layout to allow changing the width of the tasks view to a smaller minimum value. Release Notes 1.0.6 Content Fusion is now compatible with SDL Tridion Docs (tested with version 13 SP2). The name of the context map is wrapped in the "New Task" view. Fixed uploading of a context map with space characters in its file name. Fixed icon size of the "Add file to review" action. Fixed "Get changes" action that failed when the context map was missing locally. Fixed action activation when hovering over a task. Release Notes 1.0.5 Detect and warn if none of the attached files are referenced by the specified context DITA map. Improvements for the mechanism that seeks for the proper enterprise server URL from an incorrect one. Present the task name in the delete task dialog. Fixed "Get Changes" dialog size on small screens. Release Notes 1.0.4 Fixed a problem where uploading a task failed because the temporary plugins folder was deleted by the operating system. You now have the ability to "Copy task link" directly from the contextual menu of the Tasks Manager in Oxygen, instead of having to open the task in your browser to retrieve the link. Improved the background color of the panel in the Tasks Manager where you choose the Oxygen Content Fusion server. Release Notes 1.0.3 Ensured the compatibility of the plugin with Oxygen XML Editor/Author 20.1. Release Notes 1.0.2 Fixed task rendering issue after the plugin reconnects to the server. Automatically adding "http://" protocol to the server address (if missing) before trying to establish a connection. Release Notes 1.0.1 Added a mechanism that tests the server address when trying to connect to a Content Fusion server. If that connection cannot be established, it attempts to find a valid similar address (for example, the same address without a port number).
Read More
Ox
Oxygen Emmet Plugin
by Syncro Soft
Version 24.1.1
Oxygen Version: 24.1+
Emmet is a toolkit for high-speed HTML, XML, XSL etc. coding and editing. The core of this plugin is a powerful abbreviation engine which allows you to expand expressions—similar to CSS selectors—into HTML code. For more details see: docs.emmet.io. What's new in version 24.1.1 Fixed CVE-2021-23358.
Read More
Li
Live Tutorials
by Syncro Soft
Version 1.1.0
Oxygen Version: 25.1+
This add-on allows end users to run live tutorials and learn to use Oxygen inside the application. Once the Live Tutorials add-on is installed, the Tutorials view is available by selecting it from the Window > Show View menu. The add-on comes bundled with a set of tutorials for learning to work with the DITA XML standard and you also have the ability to create your own tutorials. Each tutorial contains one or more missions. A mission consists of initial file content that is opened in the application and a set of steps and hints for guidance. The mission is considered complete when the initial content is changed by the end user to match an expected result. For more information, go to Live Tutorials Add-on Documentation.
Read More
Fl
Fluenta Dita Translation
by Syncro Soft
Version 3.0.0
Oxygen Version: 24.1+
Fluenta is a tool designed to simplify the translation of DITA projects. It parses a DITA map, resolves the references to all topics and subtopics, and prepares a unified XLIFF file that you can send to your Language Service Provider. The Fluenta DITA Translation add-on allows you to manage the Fluenta translation workflow directly from within Oxygen XML Editor. What's new in version 3.0.0 The internal version of Fluenta has been updated to Fluenta 3.3.0. What's new in version 2.0.0 The internal version of Fluenta has been updated to Fluenta 3.2.0, it contains various improvements, the most important being: Allowed selection of working folders for projects and memories. Switched to JSON format for storing project and memory data. Updated OpenXLIFF Filters to version 2.10.0. Added support for Lightweight DITA(XML). Improved DITAVAL handling. Added a preferences page where you can save the folder where the projects and translation memories are stored, as well as the possibility to choose some target languages ​​to be prefilled when creating a new Fluenta project.
Read More
DI
DITA Prolog Updater
by Syncro Soft
Version 1.0.0
Oxygen Version: 22.1+
This add-on contributes a preferences page that includes various options for updating the "prolog" section of a DITA topic/map. For more details, see: https://github.com/oxygenxml/oxygen-dita-prolog-updater What's new in version 1.1.2 Added a new option for controlling where to store the options from the add-on preferences page (either in global options or in project-level options). Fixed an issue where the prolog element was inserted in documents that do not allow it. What's new in version 1.1.1 Fixed an issue where a 'contributor' author was inserted instead of a 'creator' author for newly created documents that have whitespaces in the path. What's new in version 1.1.0 Added a new option to customize the value of the type attribute for the author element that is inserted to allow you to specify the primary ( creator ) author. #20 Added a new option to customize the value of the type attribute for the author element that is inserted to allow you to specify an additional author ( contributor ). #20 Improved the process so that an additional author ( contributor ) cannot be added if they are already specified as the primary ( creator ) author. #21 Fixed an issue where a warning message was reported even though prolog updating was disabled. #15
Read More