March 2024 - oXygen-user - www.oxygenxml.com

Re: [oXygen-user] [OXYGEN-14072] Add custom catalog to OT build
by Oxygen XML Editor Support (Radu Coravu) 27 Mar '24

27 Mar '24

Hi Scott, As you seem to have a custom DITA OT installation inside your custom framework, why don't you also use it as a default engine for publishing in the Oxygen Preferences->DITA page? Other than that, the DITA OT needs to have a plugin containing extra catalogs (or as a hack you need to manually make changes to the "catalog-dita.xml" inside the DITA OT). There is no possibility to enforce an extra set of XML catalogs from the exterior when starting the DITA OT. At some point I wished there was such a way: https://github.com/dita-ot/dita-ot/issues/1515 Also Jarno Elovirta experimented at some point with a way to install plugins in the DITA OT without the need to change any files in the DITA OT folder itself, this pull request was abandoned though: https://github.com/dita-ot/dita-ot/pull/3152 Regards, Radu Radu Coravu Oxygen XML Editor On 3/27/24 02:08, Scott Prentice wrote: > I've got a custom framework that includes an OT installation that > provides our custom doctype files and custom plugins. Editing topics > that use this custom doctype is handled without problems, and using > transformation scenarios that are supported by the embedded OT also > works fine. But, I'd like to use an OT target that lives in the > default Oxygen OT installation. My Oxygen DITA settings still point to > the "built-in" OT, so when I set up a transformation scenario for the > Oxygen OT target, it starts to work, but fails when it can't find the > custom DTD. > > When I add a pointer from [OXYGEN]/org.dita.base/catalog-dita.xml that > references my custom catalog, the build completes fine. BUT .. I don't > want to modify the default Oxygen installation files. > > Some thoughts .. > > - I don't think there's a param that I can add to the transformation > scenario to reference my custom catalog .. is there? > > - I've tried adding my catalog in Settings > XML > XML Catalog .. but > that didn't seem to have any affect. > > Is there any way to add a custom catalog without editing the default > Oxygen files? > > Currently using Oxygen 25.1. > > Thanks! > > ...scott > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

Add custom catalog to OT build
by Scott Prentice 27 Mar '24

27 Mar '24

I've got a custom framework that includes an OT installation that provides our custom doctype files and custom plugins. Editing topics that use this custom doctype is handled without problems, and using transformation scenarios that are supported by the embedded OT also works fine. But, I'd like to use an OT target that lives in the default Oxygen OT installation. My Oxygen DITA settings still point to the "built-in" OT, so when I set up a transformation scenario for the Oxygen OT target, it starts to work, but fails when it can't find the custom DTD. When I add a pointer from [OXYGEN]/org.dita.base/catalog-dita.xml that references my custom catalog, the build completes fine. BUT .. I don't want to modify the default Oxygen installation files. Some thoughts .. - I don't think there's a param that I can add to the transformation scenario to reference my custom catalog .. is there? - I've tried adding my catalog in Settings > XML > XML Catalog .. but that didn't seem to have any affect. Is there any way to add a custom catalog without editing the default Oxygen files? Currently using Oxygen 25.1. Thanks! ...scott

1 0

[ANN] Version 26.1 of the Oxygen XML Suite of Products is Now Available!
by Alin Belu 25 Mar '24

25 Mar '24

Hello everyone, We are incredibly proud to announce the immediate availability of *version 26.1* of our industry-leading XML suite of products: *Oxygen XML Editor*, *Author*, *Developer*, *Web Author*, *Publishing Engine*, *WebHelp*, *PDF Chemistry*, *Scripting*, and *JSON Editor*. The *Enterprise edition* of Oxygen XML Editor/Author/Developer becomes *AI-ready*, offering access without the need for an additional subscription to the *Oxygen AI Positron Assistant Enterprise* add-on which allows direct connection to OpenAI accounts or to the Microsoft Azure OpenAI Service. Version 26.1 introduces new functionality tailored for *DITA users*, *XSLT/XQuery developers*, and *JSON/YAML developers*, enhancing productivity and versatility across various workflows. The Oxygen Publishing Engine include float support and new CSS properties, providing users with greater control over their PDF output customization. Oxygen Web Author brings support for DITA-OT project files to manage the editing context and improved handling of DITAVAL filters. Additionally, version 26.1 introduces the JSON Schema Validator add-on, facilitating seamless validation of JSON documents against JSON schema. Moreover, the Batch Documents Converter add-on now includes XSD to JSON Schema conversions, expanding its utility. ====================================================================== *What's New in Oxygen XML Editor 26.1* Oxygen XML Editor is an incremental release of the industry-leading bundle of tools for content authors, developers, collaborators, and publishers. Starting with this version, *DITA authors* can now convert sections to new topic files while preserving the DITA topic type, saving time and effort while ensuring that content remains properly structured. When editing DITA topics, several actions listed as proposals are accessible from the content completion window to help make it easier to insert content references and key references. A new option is also available to control whether or not non-DITA resources are automatically converted to DITA when inserting topic references in the DITA Maps Manager, yet another time saving improvement. *DITA publishers* that use the Zendesk Help Center transformation scenario will be happy to know that it now automatically creates and publishes a table of contents and also supports publishing to a subsection. For CSS-based PDF transformations, the new support for prepress print layout ensures that your PDFs are print-ready. The PDF transformation now also automatically fixes some incorrect values for the units of measurement detected in the width/height of images. When running DITA transformations, the real-time progress is constantly updated in the status bar to keep users informed of the current publishing step being processed. *Author mode* improvements include the content completion's Split action now automatically adding required first child elements inside the newly created element, removing extra steps from the editing process. Also, the spell checker now detects spelling errors for text inside two consecutive inline elements without a space in between them, helping to keep content error-free by preventing words from being incorrectly merged together. Some quality of life improvements were also added when using *Markdown*. The Smart Paste mechanism converts Markdown content that is pasted within XML documents in Author mode into the target vocabulary. Syntax highlights are now displayed for other languages embedded within Markdown, making it easy to identify and edit code snippets in different languages. The DITA preview pane now presents colors and filters for profiling attributes, allowing users to visualize their filtered content with ease. *JSON users* now have the power to transform JSON documents using *XSLT transformation scenarios*, unlocking a myriad of new possibilities. The content completion for JSON offers proposals even when no schema is associated and the JSON Outline view can help increase productivity as it now displays the number of child elements in each array's label and also supports drag and drop. Furthermore, basic text editing support was added for*JSON5* documents, and a new *JSON Schema Validator add-on* is available to provide support for validating JSON documents against JSON schema version 2020-12. The *AI Positron Assistant* continues to get impressive updates. A separate Enterprise version of the Oxygen AI Positron Assistant add-on is now available for users who want to connect directly to OpenAI accounts or Microsoft Azure OpenAI Service. New document templates are available to help easily create AI Positron custom actions, unlocking personalized AI solutions. A new AI action is also available to translate content into any desired language. The AI Positron Refactoring action makes it easier than ever to refactor and optimize AI projects and it now works when applied on remote resources. In addition, the chat pane now uses XML syntax highlighting for XML code to make it easier to visualize and understand the AI response. Other features and improvements were added as well. One such feature is the ability to execute Quick fix proposals in bulk, which allows users to resolve multiple issues at once. The latest engines are available for the Saxon XSLT and XQuery Transformer add-on and XProc 3.0 schemas were added to offer support for content completion and validation for XProc 3.0 files. Unique values are now automatically generated for ID-type attributes that are inserted using the Content Completion Assistant, saving time by eliminating the need to manually add them. Also, schema files and new file templates were added to support editing DocBook 5.2 documents and SVG 1.2 Tiny documents. This release also implements a variety of performance improvements, security enhancements, API and component updates, and various bug fixes. For more information, see: https://www.oxygenxml.com/xml_editor/whats_new.html ====================================================================== *What's New in Oxygen JSON Editor 26.1* The JSON support added in Oxygen XML Editor/Developer is also available in the Oxygen JSON Editor version 26.1. JSON users now have the power to transform JSON documents utilizing *XSLT transformation scenarios*, access to content completion for JSON even when no schema is associated, JSON Outline view that displays the number of child elements in each array label and also supports drag and drop, basic text editing for *JSON5* documents, and the new *JSON Schema Validator add-on* provides support for validating JSON documents against JSON schema version 2020-12. Furthermore, this release also sees the implementation of various performance improvements, security enhancements, API and component updates, and bug fixes. For more information, see: https://www.oxygenxml.com/json_editor/whats_new.html ====================================================================== *What's New in Oxygen XML Scripting 26.1* The *DITA Validate and Check for Completeness* script received important performance enhancements, significantly reducing the time it takes for the script to finish when using DITAVAL filters. For more information, see: https://www.oxygenxml.com/xml_scripting/whats_new.html ====================================================================== *What's New in Oxygen XML Web Author 26.1* This release has some interesting new features for DITA users, introducing *support for DITA-OT project files* and providing better handling of DITAVAL filters. The DITA Map pane allows users to specify a DITA-OT project file and choose between the contexts defined within it. Users may also easily switch profiling conditions, and there is the option to hide or present as grayed out content that is excluded by the current filter in the document, DITA Maps pane, and in the Outline pane. The AI Positron Assistant's feature for previewing changes was improved to allow choosing which of the AI's proposed changes will be incorporated into users' documents. When dragging a node within the Outline pane, the outline tree automatically scrolls along with the movement to make it easier to precisely drop the node where needed. The Unicode support was improved to better support surrogate characters (e.g. emoji characters) and the text mode is available as read-only mode for concurrent editing sessions. When Markdown content is pasted within DITA, DocBook, TEI, or XHTML documents, it is automatically converted to the target vocabulary by the smart paste functionality. If users develop Web Author customizations, the new CSS Inspector lets them see the styles of the selected element and the process of uploading a framework now includes validation to keep customized frameworks error-free. Server logs are available from the Administration Page to help troubleshoot issues with the Web Author server and some new URL parameters are also available to impose a DITAVAL filter or a DITA-OT project context for filtering the document. Version 26.1 also brings a variety of performance improvements, security enhancements, API and component updates, and bug fixes. For more information, see: https://www.oxygenxml.com/xml_web_author/whats_new.html ====================================================================== *What's New in Oxygen Publishing Engine 26.1* *Oxygen Publishing Engine version 26.1* adds basic float support, automatic fixes for incorrect values for width or height properties, and new CSS properties are available for configuring the PDF output. Additionally, the Zendesk Help Center transformation scenario now automatically creates and publishes a table of contents and supports publishing to a subsection. Furthermore, several performance improvements, component updates, and bug fixes were implemented. For more information, see: https://www.oxygenxml.com/publishing_engine/whats_new.html ====================================================================== *Oxygen XML Users Meetup @ XML Prague 2024* Between the 6th and the 8th of June, 2024, the XML Prague Conference makes its return, offering a unique opportunity for developers, markup enthusiasts, information managers, and students to come together in person. Continuing its tradition, the Oxygen XML team announces its presence at the conference, hosting yet another *Oxygen XML Users Meetup* on *June 6th*. This meetup has become a cornerstone of the event, providing attendees with firsthand insights into the latest developments straight from the dedicated individuals behind the Oxygen XML suite of products. To find out more about this opportunity to connect, collaborate, and stay at the forefront of XML innovation, the event page is available here: https://www.oxygenxml.com/events/2024/oxygen_user_meetup_Prague.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

Re: [oXygen-user] [OXYGEN-13754] QuickFix and DITA default attributes
by Oxygen XML Editor Support (Radu Coravu) 14 Mar '24

14 Mar '24

Hello Jirka, As usually default attributes appear on elements in the Schematron schema and there is no way to know if they have been set in the schema or directly on the XML element. You can use a template to filter out the class attribute, something similar to this older forum thread: https://www.oxygenxml.com/forum/post54152.html#p54152 Regards, Radu Radu Coravu Oxygen XML Editor On 3/13/24 20:36, Jirka Kosek wrote: > Hi, > > I'm creating few small "refactoring actions" using Schematron and > QuickFix for DITA in oXygen. It works except that default attributes > are being copied when some element is copied using QuickFix. For > example the following QuickFix > > <sch:pattern> > <sch:rule context="p"> > <sch:report test="image and > following-sibling::*[1]/self::fig[not(image)]" > sqf:fix="wrap-image">Image is misplaced and not > enclosed by a figure.</sch:report> > > <sqf:fix id="wrap-image"> > <sqf:description> > <sqf:title>Move image into adjacent figure.</sqf:title> > </sqf:description> > <sch:let name="image" value="image"/> > <sqf:delete/> > <sqf:add match="following-sibling::*[1]" position="last-child" > select="$image"/> > </sqf:fix> > > </sch:rule> > </sch:pattern> > > Will move image > > <image href="media/image29.png"/> > > as > > <image class="- topic/image " href="media/image29.png" > placement="inline" > xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"/> > > I understand that this is perhaps because QuickFix is internally > implemented as XSLT transformation so default attributes are loaded > from DTD during the parsing. I can live with added @class and > @placement, but xmlns:ditaarch namespace declaration instantly > triggers validation error in oXygen which is inconvenient? Is this > something you can fix in next releases? > > For now I've workaround that is using XSLT for performing QuickFix > action and uses <xsl:copy copy-namespaces="no"> and I intentionally do > not copy @class attribute. But QuickFix is much more concise. > > Thanks and have a nice day, > > Jirka > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

1 0

QuickFix and DITA default attributes
by Jirka Kosek 13 Mar '24

13 Mar '24

Hi, I'm creating few small "refactoring actions" using Schematron and QuickFix for DITA in oXygen. It works except that default attributes are being copied when some element is copied using QuickFix. For example the following QuickFix <sch:pattern> <sch:rule context="p"> <sch:report test="image and following-sibling::*[1]/self::fig[not(image)]" sqf:fix="wrap-image">Image is misplaced and not enclosed by a figure.</sch:report> <sqf:fix id="wrap-image"> <sqf:description> <sqf:title>Move image into adjacent figure.</sqf:title> </sqf:description> <sch:let name="image" value="image"/> <sqf:delete/> <sqf:add match="following-sibling::*[1]" position="last-child" select="$image"/> </sqf:fix> </sch:rule> </sch:pattern> Will move image <image href="media/image29.png"/> as <image class="- topic/image " href="media/image29.png" placement="inline" xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"/> I understand that this is perhaps because QuickFix is internally implemented as XSLT transformation so default attributes are loaded from DTD during the parsing. I can live with added @class and @placement, but xmlns:ditaarch namespace declaration instantly triggers validation error in oXygen which is inconvenient? Is this something you can fix in next releases? For now I've workaround that is using XSLT for performing QuickFix action and uses <xsl:copy copy-namespaces="no"> and I intentionally do not copy @class attribute. But QuickFix is much more concise. Thanks and have a nice day, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------

1 0

Re: [oXygen-user] [OXYGEN-13700] cross references in reusable content
by Oxygen XML Editor Support (Radu Coravu) 13 Mar '24

13 Mar '24

Hi Judith, With pleasure, maybe you can start a discussion with the Ixiasoft side about this. Regards, Radu Radu Coravu Oxygen XML Editor On 3/13/24 09:51, Oudkerk, Judith wrote: > > > Hi Radu, > > Thanks for your quick and extensive reply. Unfortunately, the trick > doesn’t work in our Eclipse/CMS web environment ☹. It did work in my > Oxygen stand alone version, so I did something right… > > Kind regards, > > Judith > > 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 <https://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. > > * > * > > * > > Restricted Information and Basic Personal Data > > From:* oXygen-user <oxygen-user-bounces(a)oxygenxml.com> *On Behalf Of > *Oxygen XML Editor Support (Radu Coravu) > *Sent:* Tuesday, March 12, 2024 9:59 AM > *To:* oxygen-user(a)oxygenxml.com > *Subject:* Re: [oXygen-user] [OXYGEN-13700] cross references in > reusable content > > Hello Judith, > > An internal link inside a reused component should look like this: > > <div id="reusable"> > <table id="myTable"> > <tgroup cols="1"> > <tbody> > <row> > <entry></entry> > </row> > </tbody> > </tgroup> > </table> > <p> > Paragraph <xref href="#./myTable"/> > </p> > </div> > > So: > > <xref href="#./myTable"/> > > That "#." part is called a self link, there are some examples of it here: > > https://www.oxygenxml.com/dita/1.3/specs/langRef/base/xref.html > > So the "<xref href="#./myTable"/>" should properly resolve in the > HTML/PDF no matter where the entire reusable component will be used. > > But this depends also on the publishing offered by Ixiasoft which we > do not control. > > About how you can insert "<xref href="#./myTable"/>" constructs, > Ixiasoft in general allows only inserting keyref links but in this > case such a relative href link would need to be inserted in order for > the link to work. If Ixiasoft's Oxygen integration does not offer you > the way to insert such a link in the Author page, you can try to > insert it in the Text editing mode and ask Ixiasoft to take such an > use case into account for a future version. > > About this remark: > > Do you offer DITA or Oxygen courses for technical authors who > would like to learn a bit more about how these kind of things work? > > We do not offer training/courses. Even if we would, it would not help > you much because you are using Oxygen with Ixiasoft which controls > what actions and functionality the editor offers, the workflows are > controlled by the CMS. > > The DITA 1.3 specification is quite an useful set of resources about > what the DITA standard can and cannot do. > > We also have a set of videos for learning DITA with Oxygen (but they > are with Oxygen desktop which has more functionality than the Oxygen > products which are embedded and customized by Ixiasoft): > > https://blog.oxygenxml.com/topics/learnDita.html > > Hope this helps! > > Regards, > > Radu > > Radu Coravu > Oxygen XML Editor > > > Restricted Information and Basic Personal Data > > On 3/12/24 10:26, Oudkerk, Judith wrote: > > Hi All, > > A colleague of mine would like to use cross references within > reusable content. For example, he created a reusable content topic > with <p> elements and <table> elements. In the <p> elements, he > created an <xref> to the <table> element, but in the PDF, this > does not result in a correct link. Is there a way to incorporate > <xref> elements in reusable content? I would think it’s possible > with conkeyrefs, but I can’t figure out how to implement this. Any > suggestion would be appreciated. > > We work with Oxygen embedded in Ixiasoft Eclipse / Madcap IXIA > CCMS Web. > > Thank you. > > Kind regards, > > Judith > > PS. Do you offer DITA or Oxygen courses for technical authors who > would like to learn a bit more about how these kind of things work? > > 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 <mailto:Judith.Oudkerk@elekta.com> > > > > | > > > > www.elekta.com <https://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. > > Restricted Information and Basic Personal Data > > > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com > > https://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Re: [oXygen-user] [OXYGEN-13700] cross references in reusable content
by Oxygen XML Editor Support (Radu Coravu) 13 Mar '24

13 Mar '24

Hello Judith, An internal link inside a reused component should look like this: > <div id="reusable"> > <table id="myTable"> > <tgroup cols="1"> > <tbody> > <row> > <entry></entry> > </row> > </tbody> > </tgroup> > </table> > <p> > Paragraph <xref href="#./myTable"/> > </p> > </div> So: > <xref href="#./myTable"/> That "#." part is called a self link, there are some examples of it here: https://www.oxygenxml.com/dita/1.3/specs/langRef/base/xref.html So the "<xref href="#./myTable"/>" should properly resolve in the HTML/PDF no matter where the entire reusable component will be used. But this depends also on the publishing offered by Ixiasoft which we do not control. About how you can insert "<xref href="#./myTable"/>" constructs, Ixiasoft in general allows only inserting keyref links but in this case such a relative href link would need to be inserted in order for the link to work. If Ixiasoft's Oxygen integration does not offer you the way to insert such a link in the Author page, you can try to insert it in the Text editing mode and ask Ixiasoft to take such an use case into account for a future version. About this remark: > Do you offer DITA or Oxygen courses for technical authors who would > like to learn a bit more about how these kind of things work? We do not offer training/courses. Even if we would, it would not help you much because you are using Oxygen with Ixiasoft which controls what actions and functionality the editor offers, the workflows are controlled by the CMS. The DITA 1.3 specification is quite an useful set of resources about what the DITA standard can and cannot do. We also have a set of videos for learning DITA with Oxygen (but they are with Oxygen desktop which has more functionality than the Oxygen products which are embedded and customized by Ixiasoft): https://blog.oxygenxml.com/topics/learnDita.html Hope this helps! Regards, Radu Radu Coravu Oxygen XML Editor On 3/12/24 10:26, Oudkerk, Judith wrote: > > Hi All, > > A colleague of mine would like to use cross references within reusable > content. For example, he created a reusable content topic with <p> > elements and <table> elements. In the <p> elements, he created an > <xref> to the <table> element, but in the PDF, this does not result in > a correct link. Is there a way to incorporate <xref> elements in > reusable content? I would think it’s possible with conkeyrefs, but I > can’t figure out how to implement this. Any suggestion would be > appreciated. > > We work with Oxygen embedded in Ixiasoft Eclipse / Madcap IXIA CCMS Web. > > Thank you. > > Kind regards, > > Judith > > PS. Do you offer DITA or Oxygen courses for technical authors who > would like to learn a bit more about how these kind of things work? > > > 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 <https://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. > > > Restricted Information and Basic Personal Data > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Re: [oXygen-user] [OXYGEN-8414] Refactoring functionality
by Oxygen XML Editor Support (Radu Coravu) 12 Mar '24

12 Mar '24

Hello Judith, Oxygen has the ability to create custom XML refactoring actions based on XSLT or XQuery and to apply such actions on multiple files from the local disk. We also have a predefined "Wrap element content" XML refactor action which would probably help in this case: https://www.oxygenxml.com/doc/versions/25.1/ug-editor/topics/predefined-ref… But unfortunately as the files are on the Ixiasoft CMS our XML refactoring actions cannot run over the files from the Ixiasoft storage. If for example you export the project to the local disk you could use the Oxygen desktop application's "XML Refactoring" tool. I think you should also consider adding a Schematron custom validation check in your Oxygen DITA framework customization to report such problems so that people will be notified when they insert text in cells without wrapping it in pargraphs. Regards, Radu Radu Coravu Oxygen XML Editor On 9/18/23 12:55, Oudkerk, Judith wrote: > > Hello, > > I was wondering if you can use the refactoring functionality do the > following: > > Replace all <entry>TEXT</entry> elements with > <entry><p>TEXT</p></entry>. In other words, add a <p> element to all > entry elements that already contain text (without a <p> element). > > I’m using Oxygen XML with Eclipse (and the Ixiasoft CCMS Web 6.3 version). > > I’ve been looking into the refactoring functionality, but I can’t find > a way to do this. > > Thanks in advance for your help. > > 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 <https://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. > > > Restricted Information and Basic Personal Data > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 9

[ANN] DITA-OT Day 2024 Helsinki Recordings
by Alin Belu 07 Mar '24

07 Mar '24

Hi everyone, Last month, Oxygen XML Editor hosted in Helsinki the DITA-OT Day conference, the full day conference dedicated to the DITA Open Toolkit project. We want to properly express our gratitude to everyone who contributed to making the 8th edition of the DITA-OT Day conference a success! From the DITA-OT main developers to our attendees, to the dedicated presenters and generous supporters such as Comtech, Antenna House, and Miramo, we extend our sincerest thanks for your participation and support. We're grateful for your continued involvement in shaping the future of the DITA Open Toolkit project. As we look forward to future editions with anticipation, we invite you to relive the insightful discussions and presentations by accessing the complete library of recordings and slides from this year's DITA-OT Day through the following link: https://www.oxygenxml.com/events/2024/dita-ot_day.html All the best, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Version 6.0.0 of the Oxygen Batch Documents Converter add-on is now available!
by Alin Belu 06 Mar '24

06 Mar '24

Hello everyone, We are happy to announce that *version 6.0.0* of the *Oxygen Batch Documents Converter add-on* is now available! With this update, users can now seamlessly convert XSD to JSON Schema (version 2020-12). Additionally, we have implemented enhancements related to the processing of custom-styled lists for Word to HTML/DITA conversions. Furthermore, to optimize performance and reliability, we have updated the Apache POI library, utilized for conversions from Word (only ".doc" format) and Excel, to version 5.2.5. For more information on the Oxygen Batch Documents Converter add-on (including the installation steps), you can check the page below: https://www.oxygenxml.com/doc/ug-editor/topics/batch-converter-addon.html We sincerely hope you will find this add-on helpful, and as usual, we appreciate your feedback! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0