- oXygen-user - www.oxygenxml.com

[ANN] Webinar: Exploring Oxygen's YAML Support (November 22, 2023)
by Alin Belu 16 Nov '23

16 Nov '23

Hello, On the *22nd of November*, you are invited to a 1-hour webinar, during which we will delve into the robustness of Oxygen's YAML support and showcase the exciting new features introduced in Oxygen 26. In the *Exploring Oxygen's YAML Support* live event, Octavian Nadolu (project manager at Syncro Soft) will guide you through a variety of features and improvements, providing a comprehensive understanding of Oxygen's capabilities when working with YAML documents. Don't miss this opportunity to enhance your knowledge! Some of the topics of the webinar will include: - How to effortlessly create YAML documents based on a schema, ensuring consistency and adherence to standards. - The way Oxygen enables you to check if your YAML documents are well-formed, avoiding potential syntax errors. - Exploring the powerful validation capabilities of Oxygen, which allow you to validate YAML documents using JSON Schema, giving you confidence in the integrity of your data. - The intelligent content completion in YAML documents and how it leverages the schema to enhance your productivity. - How to make your YAML documents visually appealing and easy to navigate. - Gaining insights into the seamless conversion capabilities of Oxygen, allowing you to transform YAML into other popular formats such as JSON and XML. - How Oxygen effectively supports OpenAPI and AsyncAPI specifications in YAML format, opening up new possibilities for working with APIs. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-15.html We would also like to invite you to join us for our upcoming webinar: November 29, 2023 - Discover the Power of Diff with Change Tracking https://oxygenxml.com/evs2023-16.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[Ann] New maintenance build available for oXygen 26.0 (2023111306)
by Oxygen XML Editor Support (Adrian Buza) 15 Nov '23

15 Nov '23

Dear oXygen users, We announce the release of a new maintenance build (2023111306) for oXygen 26.0 (XML Editor, XML Developer, XML Author, JSON Editor, 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#2023111306 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

[ANN] Oxygen AI Positron Version 1.0 is Now Available!
by Alin Belu 13 Nov '23

13 Nov '23

Hello, We are excited to announce version 1.0 of *Oxygen AI Positron*, a solution that harnesses the power of artificial intelligence to assist technical documentation writers at every step of their content creation journey! The Oxygen AI Positron service seamlessly integrates with the Oxygen tools - Oxygen XML Editor/Author/Developer and Oxygen XML Web Author. It is accessed through the Oxygen AI Positron Assistant plugin, making it a natural extension of the user's writing environment. Once the *Oxygen AI Positron Assistant* plugin is installed, writers can utilize AI-generated content to perform repetitive tasks, review grammar, generate structure and text, or propose changes to improve readability. It always *keeps the writer in control*, offering a visual diff comparison to help quickly identify proposed changes and understand how the AI-generated content will appear in the document. Users also have the ability to continue the chat with the AI to refine the proposals. For complex tasks that the AI may not be able to accurately complete without assistance, there is the option to *record a set of instructions* for the AI to follow and the final result can be saved as a custom AI action or as a favorite prompt that can be easily shared with other project members. Oxygen AI Positron Assistant offers intelligent support to help *resolve document validation problems* with an innovative variant of a quick-fix called *AI Positron Fix* that asks the AI engine to find a solution for a validation problem and applies its suggestion. Furthermore, a set of *AI-based XPath functions* can be accessed to enable the use of AI from any programming language that uses XPath expressions such as XSLT, XQuery, and Schematron. For example, it is possible to create XSLT-based XML refactoring actions that can batch process multiple documents, applying AI functionality on them, or to define Schematron Quick-Fixes that utilize the AI functions. To start benefiting from Oxygen AI Positron, users have the option of a free trial period. Additionally, there are several subscription plans to choose from to align with specific usage needs. For more information, see: https://www.oxygenxml.com/ai_positron_assistant.html 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-10335] Re: Keyscopes
by Oxygen XML Editor Support (Radu Coravu) 10 Nov '23

10 Nov '23

Hi Judith, Sure, once you have a sample you can either email it to us (support(a)oxygenxml.com) or upload it using the tech support form: https://www.oxygenxml.com/techSupport.html We'll also attend Tekom next week so maybe you can drop by our Oxygen XML stand to say hello :) Regards, Radu Radu Coravu Oxygen XML Editor On 11/9/23 17:53, Oudkerk, Judith wrote: > > > Hi Radu, > > Thanks for your quick reply. Unfortunately, I didn’t have time today > to prepare a file for you. Next week I’ll go the TC World Conference > in Stuttgart. So I will prepare something when I return to the office > on Monday 20 November. > > 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:* donderdag 9 november 2023 13:34 > *To:* oxygen-user(a)oxygenxml.com > *Subject:* Re: [oXygen-user] Keyscopes > > Dear Judith, > > To what format are you publishing DITA XML? Plain HTML5, PDF, WebHelp > responsive? > > If you can put together a small and valid sample DITA project on which > the publishing does not work according to your needs, zip it and send > it to us (support(a)oxygenxml.com) I can take a look at it. Other than > that just by looking at some code samples it's hard for me to pinpoint > a problem or investigate a problem. > > Also I do not know precisely what DITA OT version Ixiasoft uses on the > CMS side, maybe this would also be some useful information. Have you > considered asking Ixiasoft about this publishing problem as you are > publishing from the CMS side? > > Regards, > > Radu > > Radu Coravu > Oxygen XML Editor > > > Restricted Information and Basic Personal Data > > On 11/9/23 14:20, Oudkerk, Judith wrote: > > Dear Oxygen support specialist, > > I have a question concerning keyscopes. We recently introduced > DITA 1.3 into our CCMS (Ixiasoft), and the keyscope function > works on my test chaptermap, but it doesn’t work on the actual > chaptermap in which I want it to work. I’m wondering if I’m > doing something wrong, or if the structure of the chaptermap > obstructs the use of keyscopes like this. > > Could you perhaps have a look and let me know if there’s > something I need to change? See the two examples below. > > Thank you. > > Test chaptermap > > > > Actual chaptermap > > <?xml version="1.0" encoding="UTF-8"?> > > <!DOCTYPE map PUBLIC "-//ELEKTA//DTD ELEKTA DITA Map//EN" > "../../system/dtd/client/elekta-map.dtd"> > > _<__map_id="ikp1699477418947"xml:lang="en-us"> > > <title>Chapter 3 - Test Keyscope</title> > > <topicrefnavtitle="Chapter 3 - Test Keyscope"type="concept.xml"> > > <topicrefnavtitle="Cleaning"type="concept.xml"> > > <topicrefhref="vxp1630917783705.dita"ixia_locid="85"/> > > <topicgroupkeyscope="2"> > > <keydefkeys="clean_min"> > > <topicmeta> > > <keywords> > > <keyword>2 times</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <topicrefhref="txv1699477418166.xml"type="task"/> > > </topicgroup> > > <topicgroupkeyscope="3"> > > <keydefkeys="clean_min"> > > <topicmeta> > > <keywords> > > <keyword>3 times</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <topicrefhref="omv1699477418619.xml"type="task"/> > > </topicgroup> > > </topicref> > > </topicref> > > _</__map__>_ > > > > <?xml version="1.0" encoding="UTF-8"?> > > <!DOCTYPE map PUBLIC "-//ELEKTA//DTD ELEKTA DITA Map//EN" > "elekta-map.dtd"> > > _<__map_id="akc1628845911899"xml:lang="en-us"> > > <titleixia_locid="68">87790677 MDR Reprocessing</title> > > <maprefformat="ditamap"href="lkw1678273641906.ditamap"ixia_locid="69"/> > > <topicrefhref="gcu1628846582143.xml"ixia_locid="70"> > > <topicrefhref="rgj1632320614159.xml"ixia_locid="82"/> > > <topicrefhref="rxa1632466864947.xml"ixia_locid="71"/> > > <topicrefhref="mqk1698654265149.xml"/> > > <topicrefhref="auy1693229525780.xml"ixia_locid="73"> > > <topicrefhref="ddc1631019051495.xml"ixia_locid="74"/> > > <topicrefhref="vaj1571303228111.xml"ixia_locid="75"/> > > </topicref> > > <topicrefhref="vha1602860748443.xml"ixia_locid="55"> > > <topicrefhref="vxp1630917783705.dita"ixia_locid="85"/> > > <topicgroupkeyscope="1"> > > <keydefkeys="clean_min"> > > <topicmeta> > > <keywords> > > <keyword>2 times</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefkeys="rinse_min"> > > <topicmeta> > > <keywords> > > <keyword>10 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="6"keys="second_rinse_min"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="7">30 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="8"keys="min_temp"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="9">110 °C (230 °F) maximum</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="10"keys="disinfectant_ml"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="11">50 ml</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="12"keys="thoroughly_rinse_min"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="13">1 minute / 10 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <topicrefhref="myx1698060324132.xml"/> > > </topicgroup> > > <topicgroupkeyscope="2"> > > <keydefkeys="clean_min"> > > <topicmeta> > > <keywords> > > <keyword>3 times</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefkeys="rinse_min"> > > <topicmeta> > > <keywords> > > <keyword>30 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="6"keys="second_rinse_min"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="7">30 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="8"keys="min_temp"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="9">110 °C (230 °F) maximum</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="10"keys="disinfectant_ml"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="11">50 ml</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <keydefixia_locid="12"keys="thoroughly_rinse_min"processing-role="resource-only"> > > <topicmeta> > > <keywords> > > <keywordixia_locid="13">1 minute / 10 seconds</keyword> > > </keywords> > > </topicmeta> > > </keydef> > > <topicrefhref="nfc1698060338844.xml"ixia_locid="43"/> > > </topicgroup> > > </topicref> > > <topicrefhref="jaq1698050013557.xml"ixia_locid="76"/> > > <topicrefhref="tdk1667203793446.xml"ixia_locid="36"/> > > <topicrefhref="oqa1602753018500.xml"ixia_locid="89"/> > > <topicrefhref="ths1698049512795.xml"ixia_locid="78"> > > <topicrefhref="wci1647331763195.xml"ixia_locid="79"/> > > <topicrefhref="vuk1698065329525.xml"ixia_locid="80"/> > > </topicref> > > <topicrefhref="pdw1632819049142.xml"ixia_locid="81"/> > > <topicrefhref="gpr1698066787673.xml"ixia_locid="90"/> > > </topicref> > > _</__map__>_ > > 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 <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

1 0

[ANN] Webinar: Discover the New Search Enhancements of Oxygen Feedback 4.0 (November 15, 2023)
by Alin Belu 09 Nov '23

09 Nov '23

Hello, Next Wednesday, on the *15th of November*, join us for an exciting webinar as we dive deep into the new features of *Oxygen Feedback 4.0*! In this 1-hour live event, Alin Balasa (senior software developer at Syncro Soft) will explore the app's newest features, such as faceted search, advanced query capabilities, content labeling, and semantic search. To find out more about how to elevate your website's search functionality, join our webinar where we'll be addressing the following topics: - How to seamlessly integrate Oxygen Feedback into your WebHelp Responsive output. - Enabling content indexing and empowering efficient server-side search functionality. - Leveraging the power of a DITA Classification Map to enhance your documentation with customizable facets. - Harnessing the potential of faceted search to refine and pinpoint your search results effectively. - Enhancing your DITA topics by adding custom labels. - The shared labels and how they can facilitate your search for various topics. - Mastering the art of crafting advanced search queries to fine-tune and optimize your search results. - Elevating your WebHelp output with the activation of semantic search, delivering more contextually relevant results. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-14.html We would also like to invite you to join us for our next upcoming webinars: * November 22, 2023 - Exploring Oxygen's YAML Support ( https://oxygenxml.com/evs2023-15.html ) * November 29, 2023 - Discover the Power of Diff with Change Tracking ( https://oxygenxml.com/evs2023-16.html ) Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Re: [oXygen-user] [OXYGEN-10249] ANT transformation scenarios .. ?
by Oxygen XML Editor Support (Radu Coravu) 08 Nov '23

08 Nov '23

Hello Scott, I think this is a bug which I fixed in our code about a month or two ago, Oxygen 26 should no longer have this bug so you can give it a try. Probably we'll also release an Oxygen 25.1 minor bug fix release containing this bug fix and a couple of other bug fixes as well in a couple of weeks. Regards, Radu Radu Coravu Oxygen XML Editor On 11/7/23 21:23, Scott Prentice wrote: > > Hi... > > In O23 (maybe O24) and earlier, there was the ability to add ANT > transformation scenarios to a framework .. but in O25, that doesn't > seem to work. Am I missing some switch or setting to enable this? > > If I open a framework in O25 that was created in O23, I can edit > existing ANT scenarios, but just can't add them. > > Settings > Document Type Associations > [select/edit framework] > > Transformation tab .. > > - Use "+" button at bottom and select "ANT transformation" > > I get nada. Is anyone else seeing this? Same for O25.0 and O25.1 .. > haven't tested O26 yet. > > Is it just me or are others seeing this? > > Thanks! > ...scott > > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

ANT transformation scenarios .. ?
by Scott Prentice 07 Nov '23

07 Nov '23

Hi... In O23 (maybe O24) and earlier, there was the ability to add ANT transformation scenarios to a framework .. but in O25, that doesn't seem to work. Am I missing some switch or setting to enable this? If I open a framework in O25 that was created in O23, I can edit existing ANT scenarios, but just can't add them. Settings > Document Type Associations > [select/edit framework] > Transformation tab .. - Use "+" button at bottom and select "ANT transformation" I get nada. Is anyone else seeing this? Same for O25.0 and O25.1 .. haven't tested O26 yet. Is it just me or are others seeing this? Thanks! ...scott

1 0

Re: [oXygen-user] [OXYGEN-10021] Read only section of Xml
by Oxygen XML Editor Support (Radu Coravu) 06 Nov '23

06 Nov '23

Hi Karl, What XML vocabulary are you using? DITA, DocBook, TEI, something else? Are you editing the XML content in the Text mode or in the Author visual editor mode? When editing XML in the Author visual editor mode you have a specific CSS property which can be set to prohibit editing in certain elements: https://www.oxygenxml.com/doc/versions/26.0/ug-editor/topics/dg-editable-cs… If you are editing XML in the Text mode, it gets more complicated, you would need to build some kind of Oxygen Java based plugin which prohibits editing in certain places... Regards, Radu Radu Coravu Oxygen XML Editor On 11/1/23 07:40, Karl Stubsjoen wrote: > Hello Group! > > I'm wondering if there is a way to markup a section of xml as readonly > and then for Oxygen to honor this by either blocking or warning you of > making changes within this section. > > Scenario is simple. You have current content in some Xml node and > then you stash historical content in some other Xml node that you > intend to keep around but not to edit. > > This would be useful to me because I'll take the current information > in my Xml and stuff it into the historical section of my Xml as I roll > into a new season. The issue I am having is accidentally changing > content in the historical section of my Xml but I intended to make > those changes in the current Xml node. > > This is not mission critical, but would be a nice feature. > > Karl.. > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

1 0

[ANN] Webinar: Introducing Oxygen JSON Editor - The Ultimate Solution for JSON Editing (November 8)
by Alin Belu 02 Nov '23

02 Nov '23

Hello, Whether you're an experienced developer in search of a specialized tool or just beginning your journey with JSON, the all-new Oxygen JSON Editor is designed to meet all your JSON editing needs. Mark your calendars for next Wednesday, the *8th of November*, as you're invited to acquaint yourself with this comprehensive solution that offers a range of powerful features meant to enhance your productivity and streamline your JSON editing processes. Join us for the *Introducing Oxygen JSON Editor - The Ultimate Solution for JSON Editing* webinar, where Octavian Nadolu, project manager at Syncro Soft, will be your guide. In this live event, you'll discover how the Oxygen JSON Editor can transform your JSON development workflow by delving into its key features: * Editing JSON and JSON Schema documents with various editing modes including Text, Grid, and Author. * A dedicated Design mode that enables you to easily create and modify JSON Schema files ensuring accuracy and structural integrity of your JSON data. * The intuitive interface that simplifies navigation and comprehension of complex JSON documents. * The various tools that can assist you with converting, generating, and documenting your JSON, JSON Schema, YAML, and OpenAPI documents. * A wide range of supported technologies such as YAML, HTML, CSS, LESS, Python, Text, Shell, and more. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-13.html We would also like to invite you to join us for our upcoming webinars: * November 15, 2023 - Discover the New Search Enhancements of Oxygen Feedback 4.0 ( https://oxygenxml.com/evs2023-14.html ) * November 22, 2023 - Exploring Oxygen's YAML Support ( https://oxygenxml.com/evs2023-15.html ) * November 29, 2023 - Discover the Power of Diff with Change Tracking ( https://oxygenxml.com/evs2023-16.html ) Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Re: [oXygen-user] Read only section of Xml
by Peter Shauger 01 Nov '23

01 Nov '23

Sorry, I'm resending without the word "spam" in the subject! -----Original Message----- From: Peter <pshauger(a)tomsawyer.com> To: oxygen-user <oxygen-user(a)oxygenxml.com> Date: Wednesday, 1 November 2023 4:11 PM EDT Subject: Re: {Spam}[oXygen-user] Read only section of Xml Hi Karl! I don't know if this is exactly what you want, but what if you... 1, Create a new XML file that you will only use as the source for a conref 2, Move your historical content into a <section> or a <div> element within that new XML file 3, Place a condition on the <section> or <div> element containing the historical content, like product="historical" or maybe deliveryTarget="historical" 4, Define that condition in your DITAVAL file, for example, <prop action="exclude" att="deliveryTarget" val="historical"/> 5, In the current file, insert a conref to the historical content Because the information is in a conref, the content will be read only when you are in the current/parent file (unless you double-click it to open it). Because the content is marked with a "historical" condition, and "historical" is defined to be excluded, it will not show up in the output. -Peter From: Karl <kstubs(a)gmail.com> To: oxygen-user <oxygen-user(a)oxygenxml.com> Date: Wednesday, 1 November 2023 1:42 AM EDT Subject: {Spam}[oXygen-user] Read only section of Xml Hello Group! I'm wondering if there is a way to markup a section of xml as readonly and then for Oxygen to honor this by either blocking or warning you of making changes within this section. Scenario is simple. You have current content in some Xml node and then you stash historical content in some other Xml node that you intend to keep around but not to edit. This would be useful to me because I'll take the current information in my Xml and stuff it into the historical section of my Xml as I roll into a new season. The issue I am having is accidentally changing content in the historical section of my Xml but I intended to make those changes in the current Xml node. This is not mission critical, but would be a nice feature. Karl..

1 0