November 2020 - oXygen-user - www.oxygenxml.com

[Ann] Webinar: Automate XML processing with Oxygen XML Scripting
by Alin Belu 27 Nov '20

27 Nov '20

Hello, Next Wednesday, on December 2, our weekly live event series returns in full force with the “Automate XML processing with Oxygen XML Scripting” webinar! As you might know, continuous integration (CI) can be efficiently used to run automated scripts to validate changes as soon as they are saved to a remote repository. To make things easier for you, Alex Jitianu, DITA evangelist and development lead at Syncro Soft, will introduce you to Oxygen XML Scripting, a bundle of command line tools that can be executed inside these continuous integration and deployment pipelines. This way, you can make sure that your project is valid and ready to be deployed at any time! During this event, we will go over topics, such as: * DITA validation and checking for completeness - a tool that checks DITA maps and topics to see if they are valid and if all of the relationships between them are working. * Translation Package Builder - a tool for detecting changes, sending them to translation, and applying the translated files. * Examples on how to integrate these command line tools into integration servers, like Github Actions or Netlify. This is a free event and you can register at http://www.oxygenxml.com/evs2020-17.html Make sure to check the full list of our upcoming Events: https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

The Wellformed XML Scanner validator tried to connect to: 209.250.6.226:80
by Patrick Durusau 22 Nov '20

22 Nov '20

Greetings! I'm trying out Oxygen XML Editor 22.1 on Debian and I'm getting this persistent message: ***** The Wellformed XML Scanner validator tried to connect to: 209.250.6.226:80 The host 209.250.6.226:80 is not in the list of trusted hosts. Do you want to allow the connection to this host? ***** I checked the forum, the documentation, even searched the Internet and have not found this message elsewhere. The host in question, 209.250.6.226, just displays a Testing 123 page to show an Apache HTTP server is working. I keep denying it access but there's no persistent block that I can find. Thoughts? Suggestions? Thanks! Patrick PS: I've run whois and written to the technical contact but the popup makes it sound like I'm originating the request. PPS: No, I haven't seen this message until installing the trial version of Oxygen XML. -- Patrick Durusau patrick(a)durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

3 3

[Ann] Oxygen XML Suite Version 23 Release
by Alin Belu 19 Nov '20

19 Nov '20

Hello everyone, 2020 has certainly been a unique and challenging year for us all, but the Oxygen team persevered and is proud to announce the immediate availability of version 23 of its industry-leading XML editing suite of products, Oxygen XML Editor, Author, Developer, Web Author, WebHelp, PDF Chemistry, and the Oxygen Publishing Engine. In addition, Oxygen Feedback Enterprise, the self-managed edition of the commenting platform, was introduced in the recently released version 1.3 of Oxygen Feedback. This new release adds game-changing features like concurrent editing in Web Author for unrestricted collaboration, opening DITA maps in Author mode with the content from all referenced topics expanded and editable, the possibility to define or customize how Oxygen supports an XML language using a framework script, and support for editing JSON documents visually in Author mode. ============================================================================= Version 23 of Oxygen XML Editor boasts the most substantial and comprehensive set of new features, productivity enhancements, and customization possibilities in the history of the most powerful XML authoring and development tool available on the market. As always, a lot of attention was focused on the DITA community, to make the authoring experience even more efficient and dynamic. You can expect to discover a new dynamic floating toolbar that provides quicker access to common editing actions, it is now possible to edit submaps directly in the DITA Maps Manager view without needing to open them in their own tab, you can open DITA maps in Author mode with the content from all referenced topics expanded and editable directly in the editor, two new DITA-specific sample project templates are available to help you get more familiar with how to use projects in DITA, and if you want to experiment with the upcoming version of DITA, DITA 2.0 maps and topics can now be created from new document templates. On the DITA publishing side, you now have the ability to run multiple DITA-OT or Ant transformation scenarios simultaneously to shorten the time it takes to finish transforming large projects, image map numbers and shapes are now visible and clickable in CSS-based PDF output, and a lot of work was done on improving the Oxygen PDF Chemistry processor with various CSS property enhancements. Some of the general editing productivity enhancements include a new Find Action feature that provides a very quick way to find and trigger actions, it is now possible to copy selected XML content from Author mode to the system clipboard with the XML structure preserved, and you can now easily create a new project from an existing project template. The already robust JSON support was further enhanced. You can now edit JSON documents in Author mode with access to the various features available for XML documents, a handy tool was added for generating documentation for a JSON Schema file, and numerous improvements were made to the JSON to XML, XML to JSON, and JSON Schema Generator tools. Add-ons continue to be great for extending the functionality of Oxygen XML Editor since updates and additions can be implemented and made available in-between major Oxygen XML Editor versions. Major updates have been made to the Git Client and Batch Converter add-ons, while some of the new add-ons that have been released include a Terminology Checker, a Translator Helper, and a Vale Validation add-on. Some of the other exciting highlights for this version include the possibility of creating or customizing a framework through a script file rather than using the GUI, the capability of inserting and editing tables in JATS documents, the diff and merge support in the Eclipse plugin now incorporates the text-based mode that Oxygen users are familiar with, the content completion for XSLT 3.0 stylesheets now automatically inserts required attributes, speed optimization for documents that contain Hebrew characters, various new CSS properties, an option to batch convert HTML to well-formed XML structure, and some of the most popular command line scripts that are used for automating and running various utilities were enhanced, while other new scripts were added. As always, this release also includes various API additions, bug fixes, and component updates. For more information, see: https://www.oxygenxml.com/xml_editor/whats_new.html ============================================================================= Version 23 of the Oxygen XML Web Author continues to bolster the innovative web-based authoring tool. This release brings a lot of exciting new features, productivity enhancements, and customization possibilities to the online XML authoring community. One of the most requested features that Web Author users have asked for in recent years is concurrent editing. You now have the possibility of sharing your editing session by sending its URL to other collaborators and then you and your colleagues can edit and review the same document simultaneously. DITA users now have the ability to open a DITA map with all referenced topics expanded and editable in one single document. his allows you to perform rapid changes both at topic and map level, thus speeding-up the edit and review process in the context provided by the entire document. With the review process in mind, you can also download and print a PDF snapshot of the current document. You can also look forward to a new dynamic floating toolbar that provides quicker access to common editing actions, copy content from Web Author and paste it into an external application with the HTML structure preserved, Bitbucket server is now supported, and enhancements to the Git commit workflow were implemented. New customization possibilities and features for integrators include an option to implement Single Sign On for a CMIS server by using a service account and some new loading options and URL parameters, for example, to enable in-place editing of the content of referenced topics within a DITA map, to have topic titles resolved and displayed when opening a DITA map, or to enable multiple children of a folded element to remain visible. As usual, this release also includes various API additions, bug fixes, and component updates. For more information, see: https://www.oxygenxml.com/xml_web_author/whats_new.html ============================================================================= Version 23 of the Oxygen Publishing Engine benefits from all the improvements and new features implemented in Oxygen XML WebHelp and Oxygen PDF Chemistry. Oxygen XML WebHelp offers the option to link the WebHelp output to your own installation of Oxygen Feedback Enterprise, a self-managed edition specially designed for organizations that prefer to install the software on their own server for better data control. Several new transformation parameters were also added for this release. Oxygen PDF Chemistry provides more improvements and new possibilities for the CSS Paged Media processor used for obtaining PDF output from HTML or XML documents simply by styling them with CSS. For more information, see: https://www.oxygenxml.com/publishing_engine/whats_new.html We hope you will enjoy Oxygen 23! As always, any feedback on it is welcomed. Best regards! -- Alin Belu Oxygen XML Editor

1 0

Git submodules in frameworks
by Wendell Piez 16 Nov '20

16 Nov '20

oXygen friends, Frameworks in oXygen make up a fantastic feature set. Git is a very nice way to manage versioning in a distributed way. I am looking at making a framework that uses libraries from Github. Presently I am thinking of pointing to those libraries from my framework as git submodules and maintaining them that way. Is this a bad idea? If my framework is eventually distributed from Github, is this likely to be nice, or not so nice? Thanks - a git user for years now, but still a novice -- Cheers, Wendell -- ...Wendell Piez... ...wendell -at- nist -dot- gov... ...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org... ...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...

3 2

Format and indent the document on open
by Franz-Josef Knelangen 13 Nov '20

13 Nov '20

Hi there, really like this option - saves me a lot of Shift+Ctrl+P presses - but have a problem that this marks all files as dirty and after saving they will be displayed "changed" when committing the results to our VCS. Is there a way to work around this or do I have to disable that option? TIA, Franz-Josef AKG Software Consulting GmbH Franz-Josef Knelangen Uhlandstra?e 12 79423 Heitersheim Germany Tel.: +49 (0)7634 5612-611 Fax: +49 (0)7634 5612-300 E-Mail: fjk(a)akgsoftware.de Internet: www.akgsoftware.de<http://www.akgsoftware.de> Gesch?ftsf?hrer: Dipl.-Ing. Artur K. G?nther, Dipl.-Ing. Arno Br?ggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens G?nther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg)

3 3

[Ann] Oxygen Terminology Checker add-on version 2.0
by Alin Belu 12 Nov '20

12 Nov '20

Hello, We are glad to announce version 2.0 of our Terminology Checker add-on is now available in the *Oxygen XML* default add-on repository! The add-on is free and is compatible with any Oxygen XML Editor or XML Author version 20.0 and newer. To install the add-on, follow these instructions: 1. Go to *Help > Install new add-ons...* to open an add-on selection dialog box. 2. Select "Default Update Site" (or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml <https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml>) in the *Show add-ons from* field. 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. Version 2.0 of the add-on brings these useful new features: * Partial support to load Vale <https://github.com/errata-ai/vale> rules and use them to highlight problems. Supported Vale scopes: /heading/, /table.header/, /table.cell/, /list/, /paragraph/, /code/,/strong/, /emphasis/. Supported Vale extension points: /Existence/, /Substitution/, /Occurrence/. For example, you can download the Microsoft style guide yaml rules <https://github.com/errata-ai/Microsoft/tree/master/Microsoft> and add them to the terminology folder configured in the *Preferences->Plugins / Terminology Checker* page. * The new *Terminology Helper* side view gives an overview of the terminology problems. Clicking in the side view on the incorrect term will focus the matching term in editor area. * Share favorite rules with the team: define a folder /oxygen-term-checker/ in the root of your project and terms are automatically loaded from it. * Use capturing groups in the suggestions and messages in your custom term rules using the term match regular expression. * Match user defined custom terms at word level, character level or with a regular expression. * Insert replacement suggestion value as plain-text or as XML fragment. * Set problem severity (info, warning or error) for each matched term. * Enable/disable add-on from the tool bar without restarting *Oxygen*. We hope you will find the plugin useful and as always any feedback is welcomed. Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Master files?
by David Birnbaum 10 Nov '20

10 Nov '20

Dear oxygenxml.com, Thank you, Gerrit and Octavian, for the quick and helpful responses. Thanks to your advice, which helped me understand when and how <oXygen/> updates the dependencies when using master files, I realized both why the problem was happening and—alas!—that in an effort to simplify the description when I wrote for advice, I had unwittingly omitted a decisive detail. Octavian writes: The master files graph is updated automatically when you save a file from the editing area. Therefore, when you add the "xsl:import" instruction in the master file, the module should be added in the graph and validated correctly. If a module is not detected correctly, you can also try to refresh the Master Files folder from the Project view. For this you can use the "Refresh" action from the Project view contextual menu. I described my workflow as having a master file (a.xsl) that imports a library of functions (lib.xsl) and some subsidiary files that contain only templates (b.xsl, c.xsl, etc.). The issue was that the template files use functions declared in lib.xsl, but the template files do not import lib.xsl directly. Since the template files are intended to be used only as imports into a.xsl, and a.xsl imports lib.xsl, this means that the library functions are available when I run a real transformation. The problem I reported was that when I created a new template file to be imported, <oXygen/> was raising errors about unknown functions in it, although older template files that used the same functions did not raise those errors. This led me to understand that <oXygen/> was able to learn about the dependency hierarchy, but that that didn't happen automatically and completely whenever I created a new template file to be imported. What I left out, because I did not recognize its importance at the time, is that the import is mediated; a.xsl imports only lib.xsl and an auxiliary file (let's call it aux.xsl), which consists entirely of <xsl:import> instructions to import b.xsl, c.xsl, etc. The intermediary step is based on https://www.oxygenxml.com/archives/xsl-list/201510/msg00002.html; I want to import everything in the modules directory without having to mention them all explicitly, so I run a preprocessing XSLT script that creates aux.xsl, and a.xsl then imports that. This means, I now realize (funny how obvious things can be in retrospect!), that of course 1) I have to rerun the preprocessing script to update aux.xsl every time I create a new template file to be imported, and 2) <oXygen/> will not know that this file has been imported if it is not watching it. Keeping it open in <oXygen/> and ensuring that it reloads/refreshes each time I rerun the preprocessing script fixes the problem. This all makes perfect sense ... er ... in retrospect. Best, David djbpitt(a)gmail.com

1 0

Master files?
by David Birnbaum 09 Nov '20

09 Nov '20

Dear oxygen-user list, I've configured an XSLT transformation using master-file support, where there is one master XSLT file (a.xsl), which imports (with <xsl:import>) a file of functions (lib.xsl) and a set of files that contain only templates (b.xsl, c.xsl, etc.). The imported template files use functions defined in lib.xsl but don't import those functions directly. Since the imported template files are never run on their own, and used only by being imported into a.xsl, the functions from lib.xsl are available to the imported template files when they are used, and the transformation runs successfully. I have specified a.xsl as a master file, and <oXygen/> validates it successfully. For the most part (the four scariest words in debugging!) the imported template files do not raise real-time validation errors about unknown functions, even though they would have access to the functions they use only because both they and those functions are imported into a.xsl together. So far, so good. My issue is that when I create a new template file to be imported into a.xsl, <oXygen/> doesn't seem to know that it should be validated with the understanding that it is being imported into a.xsl, which is also importing lib.xsl. This means that when I create a new template file, <oXygen/> raises real-time validation errors about unknown functions, even though it does not raise those errors for other imported template files that use similar function calls. At some point <oXygen/> seems to learn that the new imported template files should be checked with access to master-file information, that is, that they will have access to the functions in question when they are used, at which point the imported template files no longer raise validation errors when I have them open in <oXygen/>. I have not, however, been able to identify what exactly enables <oXygen/> to learn this about new imported files as I am creating them, or how to notify <oXygen/> explicitly about them when I first begin to author them. Can someone please advise? Thanks, David djbpitt(a)gmail.com

3 2