- oXygen-user - www.oxygenxml.com

[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

"Lexical error" in applying Format & Indent to XQuery
by Joe Wicentowski 10 Aug '22

10 Aug '22

Dear oXygen Support, I encountered an unexpected error today when applying "Format & Indent" to a valid XQuery file. The error is: Cannot format the document. Lexical error at line 21, column 33. > Encountered: "]" (93), after : "" The XQuery is as follows, and line 21, column 33 corresponds to the nested array constructors [[]] : *xquery version* "3.1"; > > *declare namespace* *array*="http://www.w3.org/2005/xpath-functions/array" > ; > > *let* *$permArray* := *function*(*$myAr* *as* *array*(*)) > { > *let* *$extend* := *function*(*$ar* *as* *array*(*), *$mem* *as* *item* > ()*) > { > *array*{ > *for* *$i* *in* 1 *to* (*array:size*(*$ar*) +1) > *return* > *array:insert-before*(*$ar*, *$i*, *$mem*) > } > }, > *$extendAllSubArrays* := *function*(*$zero* *as* *array*(*), *$mem* > *as* *item*()*) > { > *array:join*( > *for* *$i* *in* 1 *to* > *array:size*(*$zero*) > *return* *$extend*(*$zero*( > *$i*), *$mem*) > ) > } > *return* > *array:fold-left*(*$myAr*, [[]], *$extendAllSubArrays*) > } > *return* *$permArray*([1, 2, 3]) => *serialize*(*map* { *"method"*: "json" > }) > The query was shared on the XML.com Slack at https://xmlcom.slack.com/archives/C011NLXE4DU/p1659114945879269?thread_ts=1… . Using the XQuery debugger, oXygen returns the expected results: [[3,2,1],[2,3,1],[2,1,3],[3,1,2],[1,3,2],[1,2,3]] But for some reason oXygen is unable to perform "format & indent" on the source XQuery. Could you please investigate this "lexical error"? Thank you, Joe

2 3

subjectSchemes and ditavals
by Oudkerk, Judith 10 Aug '22

10 Aug '22

Hi Oxygen experts, I use Oxygen within the Ixiasoft Eclipse environment. For conditional values we have to use a Ditaval. Is it possible to use a subjectscheme that does not require a Ditaval file? A temp hire created a subjectscheme once, but you still have to use a ditaval as well. I thought that when you use a subjectscheme, the ditaval would no longer be necessary. Please let me know if you have any advice. Thanks. Kind regards, Judith Restricted Information and Basic Personal Data Judith Oudkerk | Technical Writer ELEKTA | Nucletron P.O. Box 930, 3900 AX, Veenendaal, The Netherlands Visiting Address: Waardgelder 1, 3905 TH Veenendaal Judith.Oudkerk(a)elekta.com | www.elekta.com Nucletron B.V., registered 2730 3235 Nucletron Operations B.V., registered 30129540 This message is confidential and may be legally privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system; you must not copy or disclose the contents of this message or any attachment to any other person. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Elekta. Elekta may monitor email traffic data.

2 2

Sometimes the format and indent button doesn't work
by Roger L Costello 09 Aug '22

09 Aug '22

Hi Folks, Sometimes the format and indent button doesn't work. I found a workaround: copy the document you want indented, open a new empty XML tab, paste the document in there. Now the document will be formatted. Below are two screenshots. The first shows a document that is unformatted and the Oxygen format and indent button refuses to format it. The second screenshot shows the document formatted after copying and pasting. Oxygen folks, can you fix this problem please? /Roger [cid:image001.png@01D89DA1.CBD04870] [cid:image002.png@01D89DA1.CBD04870]

3 2

[ANN] DITA-OT Day 2022 - November 13, Rotterdam
by Radu Coravu 05 Aug '22

05 Aug '22

Hello everyone, We have some amazing news for you! DITA-OT Day is returning for its 7th edition, taking place this time in Rotterdam, Netherlands, on November 13, 2022! The full day conference dedicated to the DITA Open Toolkit project, the core of almost all DITA-based publishing solutions, is a free and in-person event. All you have to do to be a part of this event is to register for on-site participation, by filling out the form that is found on the DITA-OT Day 2022 event page - https://www.oxygenxml.com/events/2022/dita-ot_day.html#free-registration . Also, it is important to know that DITA-OT Day is taking place on the pre-conference day of ConVex Europe that is also taking place at the same location (nhow Rotterdam). As we are still in the process of setting up the agenda, we want to let you know that we are looking for speakers on anything related to DITA-OT! Along with the usual updates on new features and plans, this year we want to focus on the people and teams using DITA-OT. To take a look at the list of sample topics and to find out more about how to submit your proposal and the deadline information, we invite you to take a look at the Call for Proposals section - https://www.oxygenxml.com/events/2022/dita-ot_day.html#call-for-proposals . We look forward to seeing you in Rotterdam! P.S.: By accessing the link below, you can find a collection of the recordings from prior DITA-OT Day events in case you missed the opportunity to attend or if you simply want to refresh your memory: https://www.oxygenxml.com/events/2022/dita-ot_day.html#related-events Regards, Radu Radu Coravu Oxygen XML Editor

1 0

[ANN] DITA-OT Day 2022 - November 13, Rotterdam
by Alin Belu 05 Aug '22

05 Aug '22

Hello everyone, We have some amazing news for you! *DITA-OT Day* is returning for its *7th edition*, taking place this time in *Rotterdam, Netherlands, *on*November 13, 2022*! The full day conference dedicated to the DITA Open Toolkit project, the core of almost all DITA-based publishing solutions, is a free and in-person event. All you have to do to be a part of this event is to register for on-site participation, by filling out the form that is found on the DITA-OT Day 2022 event page - https://www.oxygenxml.com/events/2022/dita-ot_day.html#free-registration . Also, it is important to know that DITA-OT Day is taking place on the pre-conference day of ConVex Europe that is also taking place at the same location (nhow Rotterdam). As we are still in the process of setting up the agenda, we want to let you know that we are looking for speakers on anything related to DITA-OT! Along with the usual updates on new features and plans, this year we want to focus on the people and teams using DITA-OT. To take a look at the list of sample topics and to find out more about how to submit your proposal and the deadline information, we invite you to take a look at the Call for Proposals section - https://www.oxygenxml.com/events/2022/dita-ot_day.html#call-for-proposals . We look forward to seeing you in Rotterdam! P.S.: By accessing the link below, you can find a collection of the recordings from prior DITA-OT Day events in case you missed the opportunity to attend or if you simply want to refresh your memory: https://www.oxygenxml.com/events/2022/dita-ot_day.html#related-events -- Alin Belu Oxygen XML Editor

1 0

[ANN] DITA-OT Day 2022 - November 13, Rotterdam
by Alin Belu 05 Aug '22

05 Aug '22

Hello everyone, We have some amazing news for you! *DITA-OT Day* is returning for its *7th edition*, taking place this time in *Rotterdam, Netherlands, *on*November 13, 2022*! The full day conference dedicated to the DITA Open Toolkit project, which is the reference DITA implementation and the core of almost all DITA-based publishing solutions, is a free and in-person event. All you have to do to be a part of this event is to register for on-site participation, by filling out the form that is found on the DITA-OT Day 2022 event page - https://www.oxygenxml.com/events/2022/dita-ot_day.html#free-registration . Also, it is important to know that DITA-OT Day is taking place on the pre-conference day of ConVex Europe that is also taking place at the same location (nhow Rotterdam). As we are still in the process of setting up the agenda, we want to let you know that we are looking for speakers on anything related to DITA-OT! Along with the usual updates on new features and plans, this year we want to focus on the people and teams using DITA-OT. To take a look at the list of sample topics and to find out more about how to submit your proposal and the deadline information, we invite you to take a look at the Call for Proposals section - https://www.oxygenxml.com/events/2022/dita-ot_day.html#call-for-proposals . We look forward to seeing you in Rotterdam! P.S.: By accessing the link below, you can find a collection of the recordings from prior DITA-OT Day events in case you missed the opportunity to attend or if you simply want to refresh your memory: https://www.oxygenxml.com/events/2022/dita-ot_day.html#related-events -- Alin Belu Oxygen XML Editor

1 0

[ANN] Version 4.0.0 of the Oxygen Terminology Checker add-on is now available!
by Alin Belu 01 Jul '22

01 Jul '22

Hello everyone, We are excited to announce the release of *version 4.0.0* of the *Oxygen Terminology Checker add-on*! The latest version of the add-on brings the following useful new features: - The ability to define simple XPath expressions for particular defined rules to match or skip specific elements.* - By introducing an experimental 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). - You now have the option to set in the terminology configuration file the phase in which the incorrect terms are applied. There are 3 such phases: always (default), when the document is edited in Author Editing Mode or when the document is validated from a Validation Scenario. - The performance is now improved when checking files. *Important*: The features marked with "*" are available from Oxygen 24.1 build 2022062007 and newer. 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.xml in 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