- 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

[ANN] Oxygen Content Fusion version 6 and Oxygen Feedback version 4 are now available!
by Alin Belu 01 Nov '23

01 Nov '23

Hello everyone, We are proud to announce the immediate availability of *Oxygen Content Fusion version 6*, as well as *Oxygen Feedback version 4* (for both the *Cloud* and *Enterprise* editions). *Oxygen Content Fusion 6* introduces the new *Projects* feature, which allows you to *manage a DITA project hosted in a Git repository* while maintaining full compatibility with existing workflows and tools. New publishing features are also available to help authors *build WebHelp and PDF deliverables* and the Oxygen Styles Basket has been integrated to let users *visually customize the output*. A big focus for the release of *version 4* of *Oxygen Feedback* was to implement various advanced search functionalities, such as *Semantic Search* and *Faceted Search*, that can be used when searching WebHelp Responsive output. These advanced search functions are made possible by configuring the *Oxygen Feedback Search Engine* to be the engine used by WebHelp. ============================================================================= *What's New in Oxygen Content Fusion 6* With *version 6*, *Oxygen Content Fusion* introduces a lot of interesting and substantial improvements for the flexible and intuitive documentation platform where content authors can publish content and collaborate with subject matter experts in their documentation review process. The new *Projects* feature provides a way to *manage a DITA project hosted in a Git repository* while maintaining full compatibility with your existing workflows and tools without the need for any type of migration. *Authors can create review tasks inside a project *and *reviewers' feedback is tracked on a dedicated branch* in the Git repository. Additionally, this newest version brings new publishing capabilities for creating *WebHelp and PDF deliverables*. Users can also leverage a range of *built-in templates to adjust the look and feel of these deliverables*, and the Oxygen Styles Basket has been integrated to provide a way for the users to *visually customize the output*. Furthermore, review task owners now have the *option to close reviews* temporarily, giving them time to address feedback and make necessary changes before integrating content into the project. Enhancements were also made to the Content Fusion user interface to improve navigation and streamline workflows. The release also includes bug fixes, security enhancements, and updates to various internal components. For more information, see: https://www.oxygenxml.com/content_fusion/whats_new.html ============================================================================= *What's New in Oxygen Feedback 4* *Version 4* of *Oxygen Feedback* offers new enhancements for both its *Cloud* and *Enterprise* editions of the solution that empowers content by elevating community engagement. A big focus for this release was to implement various advanced search functionalities that can be used when searching WebHelp Responsive output. These advanced search functions are made possible by configuring the *Oxygen Feedback Search Engine* to be used as the search engine for your WebHelp output. One of the advanced functions that can be utilized is *Semantic Search*, an advanced search technique that improves the accuracy and relevance of search results by analyzing the context of the search query, rather than relying solely on keyword matching. Additionally, publishers can configure *Faceted Search* functionality in the WebHelp output, enabling users to refine their search results by applying multiple filters that correspond to different facets of the information that they are seeking. The introduction of *Labels* in the WebHelp output makes it effortless to find topics with the same label. Furthermore, the integration with the *Oxygen Feedback Search Engine* supports advanced query syntax, giving users the ability to create complex and flexible queries that generate precise search results. Additionally, site admins can conveniently view the number of positive and negative votes received for a specific page directly in the output. A new ratings information page within the admin interface displays the number of votes and messages for each documentation page, including the content of each message. Also, site admins can easily navigate to the ratings information page directly from their email notifications. Furthermore, a new checkbox can be displayed in the output when a user provides negative feedback, indicating their preference to be contacted by email for additional information if needed. This version also includes various component updates and bug fixes. For more information about the Oxygen Feedback Cloud edition, see: https://www.oxygenxml.com/oxygen_feedback_cloud/whats_new.html For more information about the Oxygen Feedback Enterprise edition, see: https://www.oxygenxml.com/oxygen_feedback_enterprise/whats_new.html ============================================================================= *DITA-OT Day 2024* On the *11th of February, 2024*, Oxygen XML Editor organizes the 8th edition of the *DITA-OT Day conference in Helsinki, Finland*, a full day, in-person event dedicated to the DITA Open Toolkit project, which is the reference DITA implementation and the core of almost all DITA-based publishing solutions (Oxygen included). Find out more details and registration information at https://www.oxygenxml.com/events/2024/dita-ot_day.html ============================================================================= We hope you will enjoy our latest releases! 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

Read only section of Xml
by Karl Stubsjoen 01 Nov '23

01 Nov '23

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

Re: [oXygen-user] [OXYGEN-9712] Why is the size limit so low for comfortably editing files in text mode in scripts such as Tamil?
by Oxygen XML Editor Support (Adrian Buza) 27 Oct '23

27 Oct '23

Hello, Tamil is a script that requires "special characters" support in text mode. When you open in Oxygen a document that contains such script (with default options) you are prompted to Enable/Disable support for bidirectional text and special characters. When this support is enabled, the performance is affected significantly. Larger documents incur a more significant performance penalty. By default *this support is disabled for files larger than 300KB, but performance can be acceptable for up to 800KB.* https://www.oxygenxml.com/doc/versions/26.0/ug-editor/topics/bidirectional-… > if I edit in text mode a file containing the equivalent of 60 pages > (which has a *size of 693 kB*), I can no longer trust what I see and > have to enter the Tamil text without paying attention to the position > of the cursor, which is far to the right side of the actual insertion > position. > > Why is that the case? To answer your question, if you have the default limit of 300k in Oxygen and are editing a file that is larger, the "special characters" support is disabled without notification. With the support disabled, it is normal for the cursor positioning and editing to be "off". If you want to have it enabled, go to Options > Preferences, Editor > Open/Save and in the section "Support for Special Characters" *configure the 'Disable special characters support for documents larger than (characters)' limit to 800k*. If you feel confident it will hold, you could clear the Disable box (so that it never gets disabled), but be aware that the larger the document, the more it will slow down, up to making it appear as hanged. If you disable the limit, I would advise to at least set it to "Prompt for each document", so you can disable it yourself when it's not needed. > Why is a text editor such as Notepad++ capable of doing what oXygen > cannot do, with respect to rendering text containing complex scritps > such as Tamil? Oxygen XML Editor is a Java application and at least for the text mode it uses the support that Java implements for rendering texts and managing cursor positions. When dealing with large file sizes and special scripts, the Java implementation struggles to efficiently handle the text rendering and cursor positioning due the complexity and nuances of the script that is not handled natively. On the other hand, text editors like Notepad++, which are solely built for handling text files, might perform better with large files and complex scripts because they use native methods (OS support) to render and manage cursor positions in the text. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support On 24.10.2023 23:41, Jean-Luc Chevillard wrote: > Dear list, > > I have often wondered why the size limit so low for comfortably > editing files in text mode in scripts such as Tamil? > > I am currently editing an ancient Portuguese-Tamil dictionary > and as soon as the file size reaches a certain size, I can no longer > trust the cursor position. > > To give an example, > if I edit today in text mode a file containing the equivalent of one > page, which has a size of 23 kB, I can trust the position of the cursor > on screen to show me where the next Tamil character will be inserted. > > HOWEVER, if I edit in text mode a file containing the equivalent of 60 > pages (which has a size of 693 kB), I can no longer trust what I see > and have to enter the Tamil text without paying attention to the > position of the cursor, which is far to the right side of the actual > insertion position. > > Why is that the case? > > Why is a text editor such as Notepad++ capable of doing what oXygen > cannot do, with respect to rendering text containing complex scritps > such as Tamil? > > Am I doing something wrong? > > I would like to know > > Thanks for any solution provided > > -- Jean-Luc Chevillard > > https://htl.cnrs.fr/equipe/jl-chevillard/ > > > P.S. The problem does not occur in Author mode, but one does not > always want to define a .CSS > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

[ANN] Webinar: What's New in Oxygen XML Web Author 26 (November 1)
by Alin Belu 26 Oct '23

26 Oct '23

Hello, Next Wednesday, on the *1st of November*, we continue our series of Oxygen XML live events with another 1-hour long webinar titled: *What's New in Oxygen XML Web Author 26*! During this webinar, Mihaela Calotescu (senior software developer at Syncro Soft) will be your guide on the journey to discover the new features included in the latest releases of the Oxygen XML Web Author, with a special focus on version 26.0, related to security, concurrent editing, profiling attributes and much more. You'll also see how the new Oxygen AI Positron Assistant side-view provides you with various ways to use ChatGPT while editing or reviewing content. This tool offers a comprehensive interface for AI actions and options, empowering you to leverage the full capabilities of AI technology, thus enhancing your productivity. It allows you to receive helpful hints for your next writing steps, enhance the readability of your content, correct grammar errors, generate index terms, translate content, create marketing-related material, or even restructure your entire document. Here are some of the topics that will be covered during this event: * Using the Shared Editing Session feature in a two-servers high availability Web Author deployment. * The new security options available in the Administration page. * Utilizing the Oxygen AI Positron Assistant Side View. * Editing profiling attributes in DITA. * How to efficiently use and edit Mermaid diagrams. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-12.html We would also like to invite you to join us for our next upcoming webinars: * November 8, 2023 - Introducing Oxygen JSON Editor - The Ultimate Solution for JSON Editing ( https://oxygenxml.com/evs2023-13.html ) * 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

Why is the size limit so low for comfortably editing files in text mode in scripts such as Tamil?
by Jean-Luc Chevillard 24 Oct '23

24 Oct '23

Dear list, I have often wondered why the size limit so low for comfortably editing files in text mode in scripts such as Tamil? I am currently editing an ancient Portuguese-Tamil dictionary and as soon as the file size reaches a certain size, I can no longer trust the cursor position. To give an example, if I edit today in text mode a file containing the equivalent of one page, which has a size of 23 kB, I can trust the position of the cursor on screen to show me where the next Tamil character will be inserted. HOWEVER, if I edit in text mode a file containing the equivalent of 60 pages (which has a size of 693 kB), I can no longer trust what I see and have to enter the Tamil text without paying attention to the position of the cursor, which is far to the right side of the actual insertion position. Why is that the case? Why is a text editor such as Notepad++ capable of doing what oXygen cannot do, with respect to rendering text containing complex scritps such as Tamil? Am I doing something wrong? I would like to know Thanks for any solution provided -- Jean-Luc Chevillard https://htl.cnrs.fr/equipe/jl-chevillard/ P.S. The problem does not occur in Author mode, but one does not always want to define a .CSS

1 0

Re: [oXygen-user] [OXYGEN-9608] Re: Oxygen 26.0 giving a "java.security.AllPermission" error -- What to do about it?
by Oxygen XML Editor Support (Teo Timplaru) 23 Oct '23

23 Oct '23

1 0

Re: [oXygen-user] [OXYGEN-9493] Load external data into form control?
by Oxygen XML Editor Support (Radu Coravu) 20 Oct '23

20 Oct '23

Hi Scott, If you just configure using the CSS a combo box to edit the values of an attribute, by default those values will be gathered either from the DTDs (if you have defined a choice of values for the attribute in the DTDs) or from our content completion configuration file which can use XSLT to gather values from another location. Maybe this blog post by my colleague Alex will help: https://blog.oxygenxml.com/topics/controlledAttributeValues2.html Regards, Radu Radu Coravu Oxygen XML Editor On 10/19/23 03:06, Scott Prentice wrote: > > I'm refining some metadata form controls for a custom framework, and > it would be ideal if I was able to load the values and labels for a > combobox from an external file (XML or preferably, JSON) rather than > hard-coding these values into the CSS. It seems that this may be > possible with xpath_eval(). Is anyone aware of any examples of this, > or am I heading down a rabbit hole? > > I'll keep poking at this, but thought I'd see if anyone had thoughts > on this effort. > > Thanks! > ...scott > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Oxygen 26.0 giving a "java.security.AllPermission" error -- What to do about it?
by Roger L Costello 20 Oct '23

20 Oct '23

[cid:image001.png@01D9FCE0.0E72AAD0]

3 3

Web Author and git submodules
by Jirka Kosek 19 Oct '23

19 Oct '23

Hi, is it possible to use submodules in WebAuthor with GitLab on-premise? I don't see similar option for enabling them as in configuration for generic Git client. Many thanks in advance. 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 ------------------------------------------------------------------

2 2

Load external data into form control?
by Scott Prentice 19 Oct '23

19 Oct '23

I'm refining some metadata form controls for a custom framework, and it would be ideal if I was able to load the values and labels for a combobox from an external file (XML or preferably, JSON) rather than hard-coding these values into the CSS. It seems that this may be possible with xpath_eval(). Is anyone aware of any examples of this, or am I heading down a rabbit hole? I'll keep poking at this, but thought I'd see if anyone had thoughts on this effort. Thanks! ...scott

1 0

Re: [oXygen-user] [OXYGEN-9425] Association Rules in frameworks
by Oxygen XML Editor Support (Radu Coravu) 18 Oct '23

18 Oct '23

Hi Scott, The "DITATopicCustomRuleMatcher" java class is where the magic happens :) It's quite hard to identify a DITA topic or map, it could use the base public IDs or it could refer to specialization DTDs, it could have various root element names, but the "DITATopicCustomRuleMatcher" Java class looks at various default attributes specified in the DTD like the "ditaarch:DITAArchVersion" attribute to decide if an opened XML document is actually a DITA topic or map. https://www.oxygenxml.com/InstData/Editor/SDK/javadoc/ro/sync/ecss/extensio… So with this extra rule added at the end of all other rules, our base "DITA" and "DITA Map" frameworks will be applied on any kind of specialized DITA XML topic or map, without the end user having to create a special DITA framework extension to match their type of documents. But once people start to create DITA framework extensions (like you do) for special DTD public ID, this extra rule placed at the end would no longer be necessary to you because you know that your topics and maps refer to specific DTDs. So I think it's correct that you are only using some very specific association rules in your DITA framework customization which no longer include our "DITATopicCustomRuleMatcher" class. About this behavior: > but I think I'm seeing that after I remove all but the necessary rules > from a particular framework, after some time, additional rules are > added. When I close and save the framework, sometime later I go back > and there are rules that match on Root Local Name .. concept, task, > reference, etc. .. I'd swear I didn't add those. Do I have gremlins, > or is this a feature? This would be a bug, but we would need some way to consistently reproduce it. Regards, Radu Radu Coravu Oxygen XML Editor On 10/18/23 01:54, Scott Prentice wrote: > I've got two different DITA models that are similar, and each may be > edited at the same time in Oxygen. Their DTDs are different and use > different Public IDs. I'm developing a framework for each which > applies slightly different schematron validation and CSS styling. It's > my understanding that I should be able to target each model using the > Association Rules, and in general this seems to work fine. > > Since I'm trying to be very specific about which documents are to use > each framework, I thought I'd keep the Association Rules to a minimum, > basically just the specific Public IDs. It's my understanding that if > a document matches any one of these rules, the framework will be > applied .. so no need to include extra match rules .. right? > > One association rule that I see on many DITA frameworks is a Java > Class rule of .. > > ro.sync.ecss.extensions.dita.topic.DITATopicCustomRuleMatcher > > Can someone tell me what this does and is it needed in all cases? > > Also .. and I may be mistaken .. but I think I'm seeing that after I > remove all but the necessary rules from a particular framework, after > some time, additional rules are added. When I close and save the > framework, sometime later I go back and there are rules that match on > Root Local Name .. concept, task, reference, etc. .. I'd swear I > didn't add those. Do I have gremlins, or is this a feature? > > Thanks! > > ...scott > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Association Rules in frameworks
by Scott Prentice 17 Oct '23

17 Oct '23

I've got two different DITA models that are similar, and each may be edited at the same time in Oxygen. Their DTDs are different and use different Public IDs. I'm developing a framework for each which applies slightly different schematron validation and CSS styling. It's my understanding that I should be able to target each model using the Association Rules, and in general this seems to work fine. Since I'm trying to be very specific about which documents are to use each framework, I thought I'd keep the Association Rules to a minimum, basically just the specific Public IDs. It's my understanding that if a document matches any one of these rules, the framework will be applied .. so no need to include extra match rules .. right? One association rule that I see on many DITA frameworks is a Java Class rule of .. ro.sync.ecss.extensions.dita.topic.DITATopicCustomRuleMatcher Can someone tell me what this does and is it needed in all cases? Also .. and I may be mistaken .. but I think I'm seeing that after I remove all but the necessary rules from a particular framework, after some time, additional rules are added. When I close and save the framework, sometime later I go back and there are rules that match on Root Local Name .. concept, task, reference, etc. .. I'd swear I didn't add those. Do I have gremlins, or is this a feature? Thanks! ...scott

1 0

[ANN] Webinar: Oxygen AI Positron - Transforming Technical Content Creation through AI-Powered Writing (October 25)
by Alin Belu 16 Oct '23

16 Oct '23

Hello, The introduction of OpenAI's ChatGPT has unlocked a world of possibilities for revolutionizing technical content creation. In our upcoming webinar, taking place on the *25th of October*, Alex Jitianu (Software Architect at Syncro Soft) will explore how AI can be a game-changer in content creation and introduce you to the great functionalities of the *Oxygen AI Positron Assistant* add-on, your trusted writing companion. In this 1-hour live session, a range of exciting topics will be covered, including: * *Various scenarios and workflows* made possible by the Oxygen AI Positron Assistant, showcasing how AI can enhance your content creation processes. * Exploring the *wide range of available actions* and showcasing how these actions can be invoked, refined, and previewed using the visual diff feature to easily understand the document changes. * How to *define and share your AI processing*, granting you greater customization and flexibility in your writing projects. * How to*improve AI understanding and accuracy* by providing examples in the editing area, ensuring consistent and correct responses from the AI. * The availability of *Oxygen AI Positron Assistant in the Web Author platform*, bringing AI assistance directly to your web-based content creation. Don't miss this opportunity to explore the future of content creation with AI! This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-11.html We would also like to invite you to join us for our next upcoming webinars: * November 1, 2023 - What is new in Oxygen XML Web Author 26 ( https://oxygenxml.com/evs2023-12.html ) * November 8, 2023 - Introducing Oxygen JSON Editor - The Ultimate Solution for JSON Editing ( https://oxygenxml.com/evs2023-13.html ) * 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

[ANN] Version 26 of the Oxygen XML Suite of Products is Now Available!
by Alin Belu 11 Oct '23

11 Oct '23

Hello everyone, We are incredibly proud to announce the immediate availability of *version 26* of our industry-leading XML suite of products: *Oxygen XML Editor*, *Author*, *Developer*, *Web Author*, *Publishing Engine*, *WebHelp*, *PDF Chemistry*, and *Scripting*, as well as the launch of its newest product, *Oxygen JSON Editor,* an affordable subscription-based application designed specifically for editing JSON and JSON Schema documents. This release introduces the exciting new *Oxygen AI Positron Assistant*, an add-on that provides a powerful tool to help writers *increase their productivity* by performing repetitive tasks, reviewing grammar, generating structure and text, or proposing changes to improve readability. It always *keeps the writer in control*, offering a visual diff comparison to help quickly understand what changed and the ability to continue the chat with the AI to refine the proposals. There is new functionality available for *DITA users*, *XSLT/XQuery developers*, as well as for *JSON/YAML developers*. It is now possible to generate *comparison results as documents containing change tracking highlights* to allow the changes to be rendered visually in the resulting documents, making it easy to review, accept, or reject them. This feature is also available via scripts to enable automation. Some of our popular*add-ons* were updated such as *Git Client*, *Batch Documents Converter*, and *OpenAPI Documentation Generator*. As always, this release also provides various important component updates, such as *DITA-OT* and *Saxon*, bug fixes, and security enhancements. *Oxygen XML Web Author version 26* provides a preview of *Oxygen **AI Positron Assistant* on the Web Author demo server, allowing users to experiment with a variety of AI-powered actions meant to improve their overall productivity. It will be available for Web Author on-premise installations very soon. Web Author also received component updates and improvements related to *file comparisons*, *DITA editing*, and *security*. ============================================================================= *What's New in Oxygen XML Editor 26* One of the most anticipated and innovative additions in Oxygen 26 is the *Oxygen AI Positron Assistant*, an add-on that provides a powerful tool to help writers use AI-generated content to *enhance their overall productivity* while keeping them in *full control of the changes* made to the documents, allowing them to see exactly what is modified using the powerful visual XML-aware diff comparison tool provided by Oxygen. Users benefit from a set of fine-tuned predefined actions that enable them to: * *Generate content* such as DITA topics, document fragments, short descriptions, and index terms. **Improve existing content* in terms of grammar, readability, and the use of active voice. * *Get various insights* to understand how readable the content is and how it responds to questions. * *Translate**to various languages* while preserving the XML structure. * *Write better marketing messages* with support for generating press releases, marketing posts, or applying marketing frameworks. Users can define their own *custom AI actions* or *favorite prompts* and easily share them 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-fix* that asks the AI engine to find a solution for a validation problem and applies its suggestion. For complex and repetitive tasks that the AI may not be able to accurately complete without assistance, it is possible 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. Furthermore, the AI functionality is made available via two *XPath AI functions* that enable the use of AI from any 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. *DITA authors* can take advantage of a simplified process of extracting and organizing parts of a document into separate topics with the ability to *extract a selection of content into a new DITA topic*, better *i18n support*, and the use of the existing DITAVAL filter files to automatically apply colors and styles to render the content in the editor. *JSON developers* can more easily navigate through large documents since the JSON diagram editor now has its own *dedicated outline view*. When *changing a property in the JSON diagram editor*, all the references to that property are now automatically updated, saving the user time and effort by eliminating the need to manually update the schema and preventing any inconsistencies or errors. Additionally, if no JSON schema is associated with a JSON document, Oxygen can now *learn the document structure* by parsing the document internally and using that as an inferred schema to provide content completion and validation. *YAML developers* now have full support for creating, editing, and validating YAML documents. They have access to new actions, such as the *go to the definition action* that allows for easy navigation to the definition of the current property and another action to *easily open the associated schema for the YAML document*. When creating new YAML documents, the new document wizard now includes a *Customize* option that enables users to configure the generation of new YAML documents based on a specified JSON Schema, ensuring consistency and adherence to predefined rules. For *XSLT and XQuery users*, the built-in Saxon processor used for*transformations and debugging* was updated to version 12.3. Oxygen's support has been enhanced to handle the latest extension functions supported by Saxon. The *Extract Function* refactoring action was improved to better handle XPath expressions. Additionally, two new AI-based extension functions (contributed by the Oxygen AI Positron Assistant add-on) that can be used to rephrase content and to perform validation checks on the existing content are available in the content completion for XSLT, XQuery, XPath, and Schematron. The support to generate *comparison results as documents containing change tracking highlights* is available for both document and directory comparison tools, allowing the changes to be rendered visually in the resulting documents, making it easy to review, accept, or reject them, or enabling the users to publish them and highlight the modified content. These tools are also available as *scripts* for those who are interested in automating these processes, using the Oxygen XML Scripting license. Some of the most popular add-ons were updated. The *Git Client* add-on now comes with integration of *Large File Support (LFS)*, among many other new additions. The *Batch Documents Converter* add-on received various improvements when converting OpenAPI to DITA, Word to HTML/DITA, or Confluence to DITA, and the *OpenAPI Documentation Generator* add-on now has the option to transform the OpenAPI content into DITA output, along with several other enhancements. Other improvements include enhanced coverage for *HTTPS certificate validation in corporate environments by utilizing trusted root certificates from the Windows certificate store*, improved syntax highlighting for *Markdown documents containing LaTeX equations* that allows for more efficient editing and seamless integration of mathematical expressions, and as usual, this release includes several important *component updates*, *bug fixes*, and *security enhancements*. This short video highlights the most important additions to Oxygen XML Editor version 26: https://youtu.be/fWvqYpGtJmw For more information, see: https://www.oxygenxml.com/xml_editor/whats_new.html ============================================================================= *Introducing a New Product: Oxygen JSON Editor* JSON developers will be thrilled with the launch of the new *Oxygen JSON Editor*. This specialized product is *designed for editing JSON and JSON Schema documents*, as well as other JSON-related technologies. What sets the Oxygen JSON Editor apart is its *affordable subscription-based pricing option*. Now, developers can *access powerful JSON editing capabilities at a reasonable cost, without compromising on quality*. For more information, see: https://www.oxygenxml.com/json_editor/whats_new.html ============================================================================= *What's New in Oxygen XML Web Author 26* One of the most exciting new features is the preview of the new *Oxygen AI Positron Assistant* plugin that provides a powerful tool to help writers *use AI-generated content*, available now on the Web Author demo server (https://www.oxygenxml.com/oxygen-xml-web-author/app/oxygen.html) and soon to be available for Web Author on-premise installations. The plugin contributes a side pane that offers a variety of *AI-powered actions* with the goal of *improving productivity*. Actions are available to provide helpful hints for the next writing steps, enhance the readability of existing content, correct grammar errors, generate index terms, translate content, create marketing-related material, or even restructure parts of a document. Interface improvements make it *easier to insert special characters*, users can now *edit Mermaid diagrams in the editor*, tracked changes are more visible when renaming elements, and static text labels are now translated properly for the Chinese language. The ability to *merge changes when comparing two documents* is now available to ensure a more accurate and efficient collaboration on documents and users can now trigger comparisons of specific document versions directly from the Version History dialog box. The *Concurrent Editing* feature now works with a *high availability deployment* consisting of two servers to help mitigate the possibility of losing connections, while also providing a higher capacity, as it can accommodate more users. DITA authors now have multiple convenient ways to *edit profiling attributes* within the editor or in the Attributes side-pane and it is now much *easier to create and insert topic references* when editing DITA maps. This short video highlights the most important additions to Oxygen XML Web Author version 26: https://youtu.be/IQKzB3pJnXY For more information, see: https://www.oxygenxml.com/xml_web_author/whats_new.html ============================================================================= *What's New in Oxygen Publishing Engine 26* *Oxygen Publishing Engine version 26 *encompasses the improvements and additions implemented in *Oxygen XML WebHelp* and *Oxygen PDF Chemistry*. This latest release offers some exciting new search features for WebHelp publishers, new customization possibilities for PDF publishers, and the bundled DITA-OT distribution was updated to version 4.1.1. Various other component updates and bug fixes were implemented as well. *Oxygen XML WebHelp version 26* introduces some exciting advanced search features that were implemented in conjunction with the upcoming 4.0 release of *Oxygen Feedback*. Once *Oxygen Feedback 4.0* will be released, WebHelp publishers will have access to *Semantic Search*, which will enhance the accuracy of search results for the end user and they will be able to configure *Faceted Search* functionality in the WebHelp output, enabling users to refine their search results by applying multiple filters that correspond to different facets of the information they are seeking. The introduction of *Labels* in the WebHelp output will make it effortless to search for topics with the same label. Furthermore, the integration with the *Oxygen Feedback Search Engine* will support advanced query syntax, giving users the ability to create complex and flexible queries that generate precise search results. *Oxygen PDF Chemistry version 26* is the latest release for the CSS Paged Media processor used for obtaining PDF output from HTML or XML documents through CSS styling. This version brings the possibility of setting the *width* property on top or bottom page margin boxes to better customize documents when displaying page numbers, publication titles, or other artwork and XPath expressions can be used inside SVG templates to insert dynamic text when creating the PDF output. For more information, see: https://www.oxygenxml.com/publishing_engine/whats_new.html ============================================================================= *DITA-OT Day 2024* On the *11th of February, 2024*, Oxygen XML Editor organizes the 8th edition of the *DITA-OT Day conference in Helsinki, Finland*, a full day, in-person event dedicated to the DITA Open Toolkit project, which is the reference DITA implementation and the core of almost all DITA-based publishing solutions (Oxygen included). Find out more details and registration information at https://www.oxygenxml.com/events/2024/dita-ot_day.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

Webhelp from DITA sources: Control tooltip display in glossary links
by Franz-Josef Knelangen 27 Sep '23

27 Sep '23

Hi there, we have glossary links in our topics, and hovering over them shows them as tooltip. That's fine as long as these entries are not too long. [cid:image001.png@01D9F11C.2B0E5C40] If the glossentry contains a table with a format description, it's no fun to read it: [cid:image002.png@01D9F11C.2B0E5C40] I tried to put the table in an element outside "glossterm" and "glossdef" = "glossBody/glossUsage" but that didn't change anything - still the whole entry is displayed as tooltip. Is there a way to control this? Do you have any workarounds or tips dealing with this situation? TIA and Greetings, Franz-Josef Franz-Josef Knelangen Leiter Dokumentation Main: +49 7634 5612-0 Facebook<https://www.facebook.com/akgsoftware/> | Xing<https://www.xing.com/pages/akgsoftware> | LinkedIn<https://www.linkedin.com/company/18590571> | YouTube<https://www.youtube.com/c/AKGSoftware-infrastructure> [cid:image002_01fef2d4-1f7d-4ea5-9727-748ef31e8852.png] AKG Software Consulting GmbH Uhlandstr. 12 D-79423 Heitersheim www.akgsoftware.de<https://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 i. Br.)

1 0