- oXygen-user - www.oxygenxml.com

XPath version in XPath toolbar?
by David Birnbaum 31 Oct '22

31 Oct '22

Dear oxygen-user(a)oxygenxml.com, If I select XPath version 3.1 in the XPath toolbar and evaluate an expression like: *//l => count()* in a document that contains *<l>* elements, it correctly returns the count of those elements. If I select XPath 1.0 and evaluate the same expression, it correctly raises an error because it doesn't understand the arrow operator, which is not part of XPath 1.0. If I select XPath 2.0 I also expect an error because the arrow operator is not part of XPath 2.0, but instead the result is the same as with 3.1. Am I mistaken in expecting 2.0 to raise an error here? Sincerely, David

2 1

Oxygen/Perforce connector?
by Scott Prentice 26 Oct '22

26 Oct '22

I have a client who is interested in using Oxygen with a Perforce repo. The only plugin/connector with Perforce I'm seeing is for Web Author .. am I missing something? Has anyone put together any sort of integration with Oxygen XML Editor and Perforce? This doesn't seem like an unreasonable expectation. Yes, Git is nice, but if your company has an existing Perforce installation, it's hard to get them to switch. Thoughts? Thanks! ...scott

3 3

[ANN] Version 5.0.1 of the Git Client add-on has been released!
by Alin Belu 18 Oct '22

18 Oct '22

Hello everyone, We are extremely proud to announce the release for *version 5.0.1* of the *Git Client add-on*! With the latest version of the Git Client Add-on, we expanded its functionality even further with various improvements, such as: * 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. * An option has been added that automatically detects Oxygen projects from opened working copies to quickly open them in the Project View. * Added a Squash merge "SELECTED_BRANCH" into "CURRENT_BRANCH" action in the contextual menu for local branches in the Git Branch Manager. This will add all changes from the "SELECTED_BRANCH" to the "CURRENT_BRANCH" in a single new commit. * By default, the History view presents commits from all branches (both remote and local). * Tags can be deleted even if they have already been pushed to the remote repository. * If the local branch has not been published yet, the push button will be decorated with a + symbol and will have a tool-tip to explain the context. * A more helpful message is displayed when pulling and the local branch doesn't track a remote. * In tree view mode, if there are no changes, the empty folder with the name of the repository will no longer be displayed. * The Git Staging view now has a busy cursor when an operation is in progress. * Fixed an issue when authentication tokens were lost from options. * Some dialogues have been improved to make them easier to understand. * Bug fixes and performance improvements. To install the add-on, follow this procedure: 1. Go to *Help > Install new add-ons* to open an add-on selection dialog box. Enter or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml in the *Show add-ons from* field or select it from the drop-down menu. 2. Select the *Git Client* add-on and click *Next*. 3. Read the end-user license agreement. Then select the *I accept all terms of the end-user license agreement* option and click *Finish*. 4. Restart the application. *Result:* The Git Staging view is now available. To open the view, select *Git Staging* from the *Window > Show View* menu (or select *Git Client* from the *Tools* menu). This view acts as a basic Git client integrated directly in Oxygen XML Editor, and it provides support for committing changes to a Git repository, comparing and merging changes, resolving conflicts, and other Git commands.*Git *menu is also contributed in the main menu bar that includes various Git actions. For more information, see the details for the Git Client add-on on the page below: https://www.oxygenxml.com/doc/ug-editor/topics/git-addon.html We hope that you will enjoy using the latest release of the Git Client add-on as much as we enjoyed developing it. As always, feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Table formatting: style attribute
by Michael Boudreau 18 Oct '22

18 Oct '22

Is Oxygen supposed to heed the ‘style’ attribute on <th> and <td> elements in the JATS table model when it’s rendering tables? It doesn’t appear to be doing so. I’m using Oxygen 25.0 on macOS X 12.6. I’m creating tables using the JATS table model in a framework that uses CSS files copied from the JATSKit framework. When I add a style attribute like this— <td align="center" valign="bottom" style="border-bottom: solid thin black; border-right: solid thin black">X</td> —the rules I hope to see on the cell don’t appear. (For background: I’m creating tables in the JATS model by converting tables from the OASIS model. In the OASIS model, the <entry> element has ‘colsep’ and ‘rowsep’ attributes to make a rule appear on the right or bottom edge of the table cell. Since there are no direct analogues of those attributes in the JATS model <th> and <td> elements, I’m using the ‘style’ attribute instead.) -- Michael R. Boudreau Electronic Publishing Technology Manager The University of Chicago Press 1427 E. 60th Street Chicago, IL 60637 www.journals.uchicago.edu<http://www.journals.uchicago.edu>

2 3

[ANN] Oxygen XML Editor version 25 has just been released!
by Alin Belu 13 Oct '22

13 Oct '22

Hello everyone, We are incredibly proud to announce the immediate availability of *version 25* of the industry-leading XML suite of products: *Oxygen XML Editor*,*Author*,*Developer*,*Web Author*,*Publishing Engine*,*WebHelp*,*PDF Chemistry*, and *Oxygen XML Scripting*! This release provides a platform to work both with XML and XML-related resources by further 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. Furthermore, users now have the ability to generate *Google Structured Data* in *WebHelp* output, and for PDF publishers this version includes support for a variety of useful *new CSS properties* to *customize the **CSS-based PDF output*. The *JSON feature* was improved by adding support for editing and validating using the latest JSON Schema version. The visual *JSON Schema diagram* was also updated and comes with new search and refactoring actions. For this release, we also focused our efforts to bring lots of improvements to some of the popular *add-ons*, such as the *Git Client*, *Batch Documents Converter*, and *Terminology Checker*. A new command-line script can be used to *validate files or directories*, and as usual, version 25 includes new *API* entry points, various bug fixes, and component updates. *Oxygen XML Web Author*, the cutting-edge web-based XML authoring tool, now features even more improvements and updates. This major release offers enhancements to the general *user interface*, new *DITA* authoring features, more customization possibilities, refinements to *concurrent editing* sessions, and *performance* tweaks. ============================================================================= *Oxygen XML Editor version 25.0* provides numerous new features, updates, and improvements that focus on productivity, performance, efficiency, advanced customization, and simplicity. This major release introduces a lot of productivity enhancements for *DITA* authors and publishers. *DITA maps* are now automatically saved whenever a modification is made in the DITA Maps Manager, various improvements were added to make referenced *DITA-compatible resources (Word, Excel, OpenAPI, HTML, Markdown)* be treated similar to DITA resources when inserting references, validating DITA maps, or publishing content. *Referenced content* (topic or map references within DITA maps or content references in topics) can be *expanded on demand* in the Author visual editing mode, thus increasing the performance when opening files with many references, a new toolbar button in the DITA Maps Manager generates a *DITA Metrics report* with useful information about the current map, *profiling attribute groups* can now be defined in a subject scheme map, and new *inline actions* are available for *inserting topic references* in DITA maps, *setting the note type*, and *setting the language for code blocks* in DITA topics. A button was added for each deliverable in *DITA-OT Project* files to make it easy to *publish that deliverable individually*, while a publish button was also added at the top of the document to *publish all deliverables* specified in the DITA-OT project file. You now have the ability to generate *Google Structured Data* in *WebHelp* output, there is also a new *Questions and Answers topic type* that can be used during the publishing phase for creating the Google Structured Data in the output, and a new action makes it possible to insert an intent question within a DITA topic. Many of the *JSON* features and tools were updated to support the latest *JSON schema version (2020-12)*. This includes *validating JSON schemas* according to the 2020-12 specification, *validating JSON or YAML documents* against a 2020-12 schema, *content completion* proposals were updated, new components were added in the *Palette view*, and you can *convert older JSON schemas to the latest version*. The*JSON Schema Documentation Generator*, *JSON Instance Generator*, and *JSON Schema Generator* tools were also updated to support the 2022-12 schema version. New *search and refactoring actions* were also integrated into the JSON Schema Design mode, and containers are now automatically created when dragging components from the Palette view to the JSON Schema Design editor. The *OpenAPI* standard is becoming more and more popular and our developers implemented various features and tools to support these types of documents. New *document templates* are available, you can *edit OpenAPI documents in Text or Author mode* taking advantage of *automatic validation* and *content completion* proposals, while the *OpenAPI Documentation Generator* and *OpenAPI Tester* tools were also improved. Additionally, support was also included for editing *AsyncAPI*, *JSON-LD*, and *OpenAPI test scenario* documents. The built-in *Saxon XSLT/XQuery processor* was updated to the latest version, *11.4*. It brings new functionality and support for new extension functions, as well as other features for *XSLT and XQuery transformations and debugging*. Other improvements include validation and transformation support for *XSLT 4.0 documents*, and content completion for XSLT 4.0 elements, attributes, and XPath 4.0 functions. *Add-ons* were another focus of this release, with some of the most popular ones receiving lots of updates. *Validation features* were added in the *Git Client*, enabling automatic validation of files before performing the commit or push actions. The *Batch Documents Converter* now has an option for *converting OpenAPI specification* files encoded in JSON or YAML formats into *DITA* documents and many of the other types of conversions received various improvements. The *Terminology Checker* add-on now has the ability to control on which elements a rule is applied using simple XPath expressions, the users can now specify the phase (editing/validation/always) in which incorrect terms are detected, and it is possible for Oxygen add-on to contribute terminology files to be used by the Terminology Checker. Other features and improvements include editing support and syntax highlighting for *PowerShell* files, performance was improved for the *XPath in Files* feature, shortcuts were added for *controlling indentation in code blocks*, and as usual, this release includes new *API entry points*, various *bug fixes*, and *component updates*. For more information, see: https://www.oxygenxml.com/xml_editor/whats_new.html ============================================================================= *Oxygen XML Scripting version 25.0* offers updates and improvements for some of the scripts that are available to provide a variety of functions that can be scheduled or triggered using a command-line tool on Windows, Linux, or macOS. This release added a new *Validate Command Line Script* that can be used for validating files or directories and generating reports in several formats (text, XML, JSON, or an HTML visual format). Also, the *Batch Converter* script now includes the option to *convert multiple documents from OpenAPI to DITA*. For more information, see: https://www.oxygenxml.com/xml_scripting/whats_new.html ============================================================================= *Oxygen Publishing Engine version 25.0* encompasses the improvements and additions implemented in *Oxygen XML WebHelp* and *Oxygen PDF Chemistry*. This latest release offers a variety of new customization possibilities, transformation parameters, properties, component updates, and bug fixes for both WebHelp and PDF publishers. For *Oxygen XML WebHelp* publishers, this release added the ability to *generate Google Structured Data* in the output and to *control the search support*. New transformation parameters were included to specify a custom search engine, to change the default search engine, or to replace the main page with a custom page. Customization possibilities were added for displaying a custom title in the search results page or for implementing custom search filters. Some of the most interesting improvements offered with the latest version of *Oxygen PDF Chemistry* include support for a variety of *new CSS properties* to help users *control how page, column, or region breaks behave*, to force or avoid *line breaks at hyphens*, to omit the header or footer from tables when a page break occurs, or to *display watermark images* in the foreground. Also, new transformation parameters can be used to make documents archive-able (*PDF/A compliant*) or to *filter the glossary*, and it is now possible to define exception elements for hyphenation dictionaries. For more information, see: https://www.oxygenxml.com/publishing_engine/whats_new.html ============================================================================= *Version 25.0.0* of *Oxygen XML Web Author* continues to bolster the innovative web-based XML authoring tool with more enhancements and additions. This major release offers improvements to the general user interface, new DITA authoring features, more customization possibilities, refinements to concurrent editing sessions, performance tweaks, as well as various bug fixes and component updates. For awhile now, the DITA support has benefited from an image map editor and that was also extended to define and edit*image maps for XHTML* documents, and in general, the image map support can now be easily added for any other XML vocabulary. When editing online, it is possible to lose the connection to the server. Once the connection is restored, the *concurrent editing* support now resumes seamlessly. Inserting DITA new topics and topic references in DITA maps is made easier by a new CSS style that provides *inline actions to insert topic references* when editing DITA map documents in the visual editor. Other interesting enhancements added in this version of Web Author include actions to *select an element, its content, or its parent*, actions to insert links were added to the floating toolbar, easier methods for controlling indentation and setting the *syntax highlight language in code blocks*, and the *Outline pane* is now also available for *DITA maps*. For more information, see: https://www.oxygenxml.com/xml_web_author/whats_new.html ============================================================================= *DITA-OT Day 2022* On the *13th of November, 2022,* Oxygen XML Editor organizes the 7th edition of the *DITA-OT Day conference in Rotterdam*, Netherlands, a full day in-person event dedicated to the DITA Open Toolkit project, which is the reference DITA implementation and the core of almost all DITA-based publishing solutions, Oxygen included. Find out more details and registration information at https://www.oxygenxml.com/events/2022/dita-ot_day.html ============================================================================= We hope you will enjoy our latest release of the Oxygen XML suite of products! As always, thank you for your support and don't forget that feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Auto-insert element with cc_config
by Scott Prentice 12 Oct '22

12 Oct '22

I've added the following to my cc_config file .. *<elementProposals path="fig" insertElements="image" />* This properly inserts an <image> element when a <fig> is added, but the Insert Image dialog doesn't display. I tried including "insert.image" in the insertElements attribute, but that didn't do the trick. Is it possible to get an image to be added when a fig is inserted, but also provide the Insert Image dialog? Thanks! ...scott

2 2

[ANN] Version 4.1.0 of the Oxygen Terminology Checker add-on is now available!
by Alin Belu 07 Oct '22

07 Oct '22

Hello everyone, We are thrilled to share with you that *version 4.1.0* of the *Oxygen Terminology Checker add-on* is now available! The latest version of the add-on brings the following useful new features: * 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 the Results view. * Updated colors in the Terminology Checker view for a better experience with the Graphite theme. * Fixed an issue that caused the contextual menu to become overly big. * The issue that led to the Terminology Checker view expanding excessively has been fixed. * Security/Component Update: The SnakeYAML library was updated to version 1.31 - CVE-2022-25857. To manually install the add-on, follow these instructions: 1. Go to *Help > Install new add-ons* to open an add-on selection dialog box. 2. Enter or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xmlin the *Show add-ons from* field or select it from the drop-down menu. 3. Select the *Terminology Checker* add-on and click *Next*. 4. Select the *I accept all terms of the end user license agreement* option and click *Finish*. 5. Restart the application. For more information on the add-on, see the details for the Oxygen Terminology Checker on the page below: https://www.oxygenxml.com/doc/versions/24.1/ug-editor/topics/terminology-ch… We hope you will find this new version of our add-on useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Version 5.0.0 of the Oxygen Batch Documents Converter add-on has been released!
by Alin Belu 30 Sep '22

30 Sep '22

Hello everyone, We are excited to announce that *version 5.0.0* of the *Oxygen Batch Documents Converter add-on* is now available! For the newest version of the add-on, our team of developers worked hard to bring you an impressive list of useful improvements: *** OpenAPI to DITA *** * 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 HTML/DITA *** * Improved the Word styles mapping configuration 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. * Improved the IDs generation on topics and sections by using the text from headings. * Improved the handling of tables by preserving header row information during the conversion. * Fixed a case where a list that contains content between list items was broken into multiple lists. * Fixed a case where multiple ordered lists were merged into one. * Fixed a case where the conversion failed when the document contained duplicate mappings between numberings and styles. * Fixed a case where WMF images were not handled by the converter. * Fixed a case where the DITA result contained an invalid MathML equation. * Fixed a case where the DITA result contained images wrapped in the 'b' element. * Fixed a case where the value edited in the Word Styles Mapping table from the preferences page was not saved. * Updated the Java-Mammoth library used for Word to HTML/DITA conversions to version 1.5.0. *** HTML to DITA *** * Improved the conversion of object elements from HTML by adding a proper 'outputclass' attribute in the DITA result. * Added an option in the conversion dialog box that allows you to decide whether or not the 'div' elements will be ignored. * Fixed a case where 'id' and 'class' attributes were lost when breaking paragraphs by processing the 'br' elements. *** Markdown to DITA *** * Added support for the Markdown abbreviations. * Improved the conversion to allow processing of headings specified as HTML in the Markdown documents. * Improved the handling of the local references. * Improved the handling of the HTML anchor elements in the Markdown documents. *** Other *** * The formatting of 'pre' elements is prevented when converting HTML to XHTML. * Fixed the layout of the preferences page because it was not entirely visible on low resolution screens. To manually install the add-on, please follow these instructions: 1. Go to Help > Install new add-ons to open an add-on selection dialog box. 2. Enter or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml in the Show add-ons from field. 3. Select the Batch Documents Converter add-on and click Next. 4. Read the end-user license agreement. Then select the I accept all terms of the end-user license agreement option and click Finish. 5. Restart the application. Result: A Batch Documents Converter submenu will now be available in the Tools menu and in the contextual menu. This submenu will contain a list of the various types of available conversions. Selecting one of the types of conversions will open a dialog box where you can configure options for the conversion. For more information on the Oxygen Batch Documents Converter add-on, you can check the page below: https://www.oxygenxml.com/doc/ug-editor/topics/batch-converter-addon.html We hope you will find this new release useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[Ann] New maintenance build available for oXygen 24.1 (2022092207)
by Oxygen XML Editor Support (Adrian Buza) 23 Sep '22

23 Sep '22

Dear oXygen users, We announce the release of a new maintenance build (2022092207) for oXygen 24.1 (XML Editor, XML Developer, XML Author, XML WebHelp, PDF Chemistry, Publishing Engine). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2022092207 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support

1 0

Relax NG validation messages
by David Birnbaum 19 Sep '22

19 Sep '22

Dear oxygen-user(a)oxygenxml.com, I have a question about the error messages <oXygen/> reports when validating a Relax NG rule that types an item as xsd:integer. My test XML is: <?xml version="1.0" encoding="UTF-8"?> <?xml-model href="n.rnc" type="application/relax-ng-compact-syntax"?> <stuff>1</stuff> and my test Relax NG is: start = stuff stuff = element stuff { xsd:integer {minInclusive = "1" maxInclusive = "1"} } As I expected, both "1" and "01" pass validation. Initially I (erroneously) expected "1.0" to pass because I thought validation cared only about the value space, and not the lexical space, and it didn't because I had misunderstood how integer was defined. Section 3.3.13 integer of https://www.w3.org/TR/xmlschema-2/ plainly says "disallowing the trailing decimal point", a limitation of the lexical space that automatically disallows the trailing zero. I am, though, puzzled by the error message that <oXygen/> displays for "1.0", which reads: character content of element "stuff" invalid; must be a decimal number without any significant digits after the decimal point I think that the wording of the error message suggests that "1." should pass, since the message seems to implies that the decimal point is fine, and the mistake was putting a zero after it. Yet validating "1." raises: character content of element "stuff" invalid; must be an integer This is consistent with the spec, as cited above, but also, I think, misleading because the *value* of "1.0" is an integer, and the prohibited trailing decimal point is about the lexical representation of the value. The error message doesn't distinguish value space from lexical space, although it could. Am I alone in thinking that these two error messages could be clearer because the error in both cases is the same: the lexical space of xsd:integer does not permit a decimal point? Neither of these messages fingers the decimal point as the invalid part of the content. Sincerely, David

2 1