March 2018 - oXygen-sdk - www.oxygenxml.com

[Ann] New maintenance build available for oXygen 20.0 (2018032903)
by Adrian Buza 30 Mar '18

30 Mar '18

Dear oXygen users, We announce the release of a new maintenance build (2018032903) for oXygen 20.0 (XML Editor, XML Developer, XML Author, XML WebHelp). 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#2018032903 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 Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

[Ann]New Oxygen XML Editor version 20 release
by Radu Coravu 19 Mar '18

19 Mar '18

Hi everybody, I'm glad to announce that we released a new version of Oxygen XML Editor, version 20. The new added API is listed here: https://www.oxygenxml.com/xml_editor/whatisnew20.0.html#20.0API Among the most important additions we added the possibility to add decorator icons to the Oxygen project view and we also added the possibility to provide translations for a new language for Oxygen's UI via a plugin. As another important change Oxygen 20's Java code is now compiled using Java 1.8 so Oxygen can no longer be run using Java 1.6. As always we tried to keep the API changes fully backward compatible so if you test your plugins or framework with Oxygen 20.0 and notice any problems please tell us. Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com

1 0

[Ann] New maintenance build available for oXygen 19.1 (2018022209)
by Adrian Buza 05 Mar '18

05 Mar '18

Dear oXygen users, We announce the release of a new maintenance build (2018022209) for oXygen 19.1 (XML Editor, XML Developer, XML Author). 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#2018022209 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 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

DITA: 'Refresh references' of a topic with nested conrefs, removes the first character of the text content of this element (node) with the conref attribute
by Pascal Beutels 01 Mar '18

01 Mar '18

Hi, When diving deeper into our custom variable resolver, we found an issue with resolving of nested conrefs (which affects our custom variable resolver which can have nested variables or nested conrefs). Below an example case with standard DITA files (not from our repository, nor customized) and standard Oxygen XML Author to explain the issue: We have a topic with a ph element that has some text inside the element (simple_topic.dita -> <ph conref="...">Text content inside ph element that has the conref attribute.</ph>) This ph element has a conref attribute to a ph inside conref_niv_1.dita. This ph element in conref_niv_1.dita, contains another ph with a conref to conref_niv_2.dita. The example topics at the end of the e-mail (and attached) make it more clear. The issue is that with every refresh of the references (Oxygen menu: DITA -> Refresh references), a character is removed from the text content of the ph element in simple_topic.dita, change the content of this topic... We noted this when improving our custom 'variable' resolving which is based on the Oxygen DITAConRefResolver (package ro.sync.ecss.extensions.dita.conref -> DITAConRefResolver.java). We do an override of: public SAXSource resolveReference( AuthorNode node, String systemID, AuthorAccess authorAccess, EntityResolver entityResolver) And while debugging, we notice that in the incoming AuthorNode parameter (node) this character is already removed. This can be seen when: * getting the text of all the content nodes using node.getTextContent(), there the first character is already gone. * converting the node to an AuthorElement (which it is) and creating an AuthorDocumentFragment from it and then serialize it using AuthorDocumentController.serializeFragmentToXML, the text content of that element is also already stripped. Code sample/snippet: if (node instanceof AuthorElement) { AuthorElement element = (AuthorElement) node; .... AuthorDocumentController documentController = authorAccess.getDocumentController(); AuthorDocumentFragment fragFromNode = documentController.createDocumentFragment(element, true); xml = documentController.serializeFragmentToXML(fragFromNode); ... * using your suggested approach using a AuthorElementDomWrapper created from this AuthorElement. We found this for Oxygen 19.1, we can also reproduced on Oxygen 17.1 Kind regards, Pascal Example topics: simple_topic.dita <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="simple_topic"> <title>Simple Topic</title> <body> <ph conref="conref_niv_1.dita#conref_niv_1/id_conref_niv_1">Text content inside ph element that has the conref attribute.</ph> </body> </topic> conref_niv_1.dita <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="conref_niv_1"> <title>Conref niv 1</title> <body> <ph id="id_conref_niv_1">Content from conref_niv_1, followed by nested conref from niv 2: <ph conref="conref_niv_2.dita#conref_niv_2/id_conref_niv_2"/></ph> </body> </topic> conref_niv_2.dita <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="conref_niv_2"> <title>conref niv 2</title> <body> <ph id="id_conref_niv_2">Content from conref_niv_2 </ph> </body> </topic> www.sdl.com SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: SDL PLC, New Globe House, Vanwall Business Park, Vanwall Road, Maidenhead, SL6 4UB, U.K.

2 1