- oXygen-user - www.oxygenxml.com

[ANN] Introducing Oxygen Git Client add-on version 5.3.0!
by Alin Belu 21 Sep '23

21 Sep '23

Hello everyone, We are happy to introduce you to *version 5.3.0* of the *Oxygen Git Client add-on*, your trusted companion for Git-related tasks, making version control and collaboration smoother and more efficient! The newest release of our add-on comes with the following key improvements: * *Enhanced Oxygen project detection.* We've fine-tuned our Oxygen project detection to ensure it works more smoothly, saving you valuable time and effort. * *Submodule precision.* Now, when you check out a branch, submodules in parent repositories will be checked out at the index defined in the parent repository. This means your submodules will always reflect the precise state of the parent repository at that time, ensuring your projects stay in sync. For more information on the Oxygen Git Client add-on (including the installation steps), you can check the page below: https://www.oxygenxml.com/doc/ug-editor/topics/git-addon.html We hope that you will enjoy using the most recent release of the add-on as much as we enjoyed developing it. As always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Refactoring functionality
by Oudkerk, Judith 18 Sep '23

18 Sep '23

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<mailto:Judith.Oudkerk@elekta.com> | www.elekta.com<https://www.elekta.com/> Nucletron B.V., registered 2730 3235 Nucletron Operations B.V., registered 30129540 [cid:image290631.png@17E70B0A.561E8CC3] 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

1 0

[ANN] Get Ready for DITA-OT Day 2024! (February 11, Helsinki)
by Alin Belu 15 Sep '23

15 Sep '23

Hello everyone, We have some amazing news for you! *DITA-OT Day* is returning for its *8th edition*, taking place this time in *Helsinki, Finland*, on *February 11, 2024*! The full day conference dedicated to the DITA Open Toolkit project, the core of almost all DITA-based publishing solutions, is a free and in-person event. All you have to do to be a part of this event is to register for on-site participation, by filling out the form that is found on the DITA-OT Day 2024 event page - https://www.oxygenxml.com/events/2024/dita-ot_day.html#free-registration . Furthermore, it is important to note that DITA-OT Day coincides with the pre-conference day of DITA Europe, both taking place at the Scandic Park Helsinki hotel. The call for proposals is currently in progress, and we are actively seeking speakers who can address topics related to DITA-OT! Along with the usual updates on new features and plans, this year we want to focus on the people and teams using DITA-OT. Take a look at the Call for Proposals section for more information on how to submit your proposal and the deadline:https://www.oxygenxml.com/events/2024/dita-ot_day.html#call-for-pr… . We look forward to seeing you in Helsinki! PS: In case you missed the opportunity to attend prior events or if you simply want to refresh your memory, you can access the recordings from past DITA-OT Day conferences at: https://www.oxygenxml.com/events/2024/dita-ot_day.html#related-events -- Alin Belu Oxygen XML Editor

1 0

How to get Oxygen to generate an instance containing 100 child elements?
by Roger L Costello 06 Sep '23

06 Sep '23

Hello Oxygen team, I am using Oxygen to generate a sample XML instance from an XSD. Here's my simple XSD: <xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema> <xs:element name="test"> <xs:complexType> <xs:choice maxOccurs="unbounded"> <xs:element name="A" fixed="A"/> <xs:element name="B" fixed="B"/> <xs:element name="C" fixed="C"/> </xs:choice> </xs:complexType> </xs:element> </xs:schema> Notice the repeatable xs:choice. I then selected Tools >> Generate Sample XML Files ... I want the tool to repeat the xs:choice 100 times. I "think" that I have specified this correctly. See screenshot below. However, the tool only repeats the xs:choice 16 times. Why is that? How to get the tool to generate 100 child elements? [cid:image001.png@01D9E0D1.F71DEAE0]

1 0

[ANN] Join Oxygen XML at tcworld Conference 2023 (Stuttgart, 14-16 November)
by Alin Belu 22 Aug '23

22 Aug '23

Hello everyone, Between the *14th* and the *16th of November*, the Oxygen XML team will exhibit and present at the *tcworld Conference 2023*, the event that brings together participants, speakers, students, and exhibitors in "technical communication" from all over the world to the largest industry meeting place – once again in *the ICS of Messe Stuttgart*! There, you will get the chance to meet a part of the Oxygen team in-person (*George Bina*, *Radu Coravu*,*Alex Jitianu*,*Octavian Nadolu,***and *Sorin Carbunaru*) and discuss with them ideas related to the Oxygen products and supported technologies, or see a demo tuned to match your specific use-cases. Of course, similar to the previous years, we prepared for you a great agenda that looks like this: *Wednesday, November 15, 10:45 – 11:15 AM (CET)** **The AI revolution - What's in it for the DITA writers? (DITA Arena) - Sorin Carbunaru* /ChatGPT took the world by storm. While some took shelter, others chose to spread their wings, ride the winds of change, and explore the new possibilities. So where exactly did these winds take the little DITA finch?// //In this presentation, we'll see what new prospects were opened up by AI for DITA content creators, as they are an excellent fit for AI adoption. Why? Because they can use it to boost their productivity, while also keeping the control in their hands by ensuring the content they deliver to the end-users is accurate./ *Wednesday, November 15, 11:30 – 12:15 (CET)** **Harnessing the Power of AI: Enhancing Technical Content Creation with Intelligent Prompts (Presentation) - Alex Jitianu* /In the past few years, the integration of Artificial Intelligence (AI) into various software development tools has witnessed remarkable growth, like the creation of GitHub Copilot software developer assistant. However, the potential of AI extends far beyond code completion. In this presentation, we will explore how AI can revolutionize content creation. We will delve into ways in which AI-powered prompts can serve as valuable writing companions./ *Thursday, November 16, 11:30 – 12:15 (CET)** **Practical Git Workflows for Tech Docs (Presentation) - Radu Coravu* /In this presentation, our main focus will be on the practical aspects and workflows of using Git as a version control system for technical documentation with the DITA XML standard. We will explore how a DITA XML documentation project can be stored on a Git repository along with common settings.// //Throughout the presentation, we will discuss the common editing and collaboration workflows for technical writers utilizing Git repositories. We'll also address storing shared editing and publishing settings, ensuring seamless updates, edits, content commits, and conflict resolution./ For more informations regarding Oxygen XML's participation at tcworld Conference 2023, check out the following link: https://www.oxygenxml.com/events/2023/tcworld_conference_2023.html We can't wait to see you all in Stuttgart! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

How to prevent Format and Indent from modifying the content of specific elements?
by Roger L Costello 14 Aug '23

14 Aug '23

I have an XML document with elements that contain JSON code, e.g., <schema> "$schema": https://json-schema.org/draft/2020-12/schema, "type": "object", "properties": { "password": {"type": "string", "writeOnly": true} } </schema> When I click on the Format and Indent icon, I do not want that content to be changed. Is there a way to instruct Oxygen, "Hey, don't change the content of the <schema> element."? /Roger

2 1

Re: [oXygen-user] [OXYGEN-6052] Why is the JSON Schema $anchor not supported?
by Oxygen XML Editor Support (Florin Nica) 08 Aug '23

08 Aug '23

Hi Roger, The library is called /json-sKema/. You can check its GitHub repository for more details: https://github.com/erosb/json-sKema. Regards, Florin On 08/05/23 2:18 PM, Roger L Costello wrote: > > Florin Nica wrote: > > * We plan to provide full support for JSON Schema /Draft 2020-12/ in > the near future by using another library. > > Would you mind telling me what library (JSON Schema validator tool) > that you will be adding into Oxygen? (I can understand if you do not > wish to tell me.) > > /Roger > > *From:*oXygen-user <oxygen-user-bounces(a)oxygenxml.com> *On Behalf Of > *Oxygen XML Editor Support (Florin Nica) > *Sent:* Tuesday, June 27, 2023 4:01 AM > *To:* oxygen-user(a)oxygenxml.com > *Subject:* [EXT] Re: [oXygen-user] [OXYGEN-6052] Why is the JSON > Schema $anchor not supported? > > Hi Roger, Thank you very much for the feedback. We use a third-party > library for JSON Schema validation and, unfortunately, it does not > support the "$anchor" and "$dynamicAnchor" keywords. This is mentioned > as a limitation in our user-guide, > > ZjQcmQRYFpfptBannerStart > > Hi Roger, > > Thank you very much for the feedback. > > We use a third-party library for JSON Schema validation and, > unfortunately, it does not support the "$anchor" and "$dynamicAnchor" > keywords. This is mentioned as a limitation in our user-guide > <https://www.oxygenxml.com/doc/versions/25.1/ug-editor/topics/json-validatin…>, > but, indeed, the message displayed for "$anchor" is not accurate at all. > > We plan to provide full support for JSON Schema /Draft 2020-12/ in the > near future by using another library. I will let you know when this > support is ready. > > Regards, > Florin > > On 6/22/2023 9:25 PM, Roger L Costello wrote: > > When I add "$anchor" to my JSON Schema, the Oxygen editor gives this error message: > > The keyword "$anchor" is not part of > > JSON Schema Draft 2020-12 specification. > > Therefore, it is ignored by the validation engine. > > But that's not true. See section 8.2.2 of the 2020-12 specification (https://json-schema.org/draft/2020-12/json-schema-core.html#section-8.2.2) > > Using JSON Pointer fragments requires knowledge of the structure of the schema. When writing schema documents with the intention to provide re-usable schemas, it may be preferable to use a plain name fragment that is not tied to any particular structural location. This allows a subschema to be relocated without requiring JSON Pointer references to be updated. > > The "$anchor" and "$dynamicAnchor" keywords are used to specify such fragments. They are identifier keywords that can only be used to create plain name fragments, rather than absolute URIs as seen with "$id"... > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > > https://www.oxygenxml.com/mailman/listinfo/oxygen-user > > -- > Florin Nica > <oXygen/> XML Editor > www.oxygenxml.com <http://www.oxygenxml.com> > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user -- Florin Nica <oXygen/> XML Editor www.oxygenxml.com

1 0

Re: [oXygen-user] [OXYGEN-6052] Why is the JSON Schema $anchor not supported?
by Oxygen XML Editor Support (Florin Nica) 05 Aug '23

05 Aug '23

Hi Roger, Thank you very much for the feedback. We use a third-party library for JSON Schema validation and, unfortunately, it does not support the "$anchor" and "$dynamicAnchor" keywords. This is mentioned as a limitation in our user-guide <https://www.oxygenxml.com/doc/versions/25.1/ug-editor/topics/json-validatin…>, but, indeed, the message displayed for "$anchor" is not accurate at all. We plan to provide full support for JSON Schema /Draft 2020-12/ in the near future by using another library. I will let you know when this support is ready. Regards, Florin On 6/22/2023 9:25 PM, Roger L Costello wrote: > When I add "$anchor" to my JSON Schema, the Oxygen editor gives this error message: > > The keyword "$anchor" is not part of > JSON Schema Draft 2020-12 specification. > Therefore, it is ignored by the validation engine. > > But that's not true. See section 8.2.2 of the 2020-12 specification (https://json-schema.org/draft/2020-12/json-schema-core.html#section-8.2.2) > > Using JSON Pointer fragments requires knowledge of the structure of the schema. When writing schema documents with the intention to provide re-usable schemas, it may be preferable to use a plain name fragment that is not tied to any particular structural location. This allows a subschema to be relocated without requiring JSON Pointer references to be updated. > > The "$anchor" and "$dynamicAnchor" keywords are used to specify such fragments. They are identifier keywords that can only be used to create plain name fragments, rather than absolute URIs as seen with "$id"... > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user > -- Florin Nica <oXygen/> XML Editor www.oxygenxml.com

2 1

[ANN] Discover what's new in Oxygen Git Client add-on version 5.2.0!
by Alin Belu 01 Aug '23

01 Aug '23

Hello everyone, We are thrilled to announce the release of *version 5.2.0* for the*Oxygen Git Client add-on*! This newest update brings an array of new features and improvements, the most important being the introduction of *Large File Support (LFS)* to the Oxygen Git Client. If you have installed LFS and specified which extensions represent large or binary files that should be uploaded through the LFS mechanism, they will be automatically detected and handled correctly. This ensures a smoother and more seamless handling of large files, improving your version control process overall. Additionally, version 5.2.0 offers *improved messages in the user interface* to provide clearer and more informative notifications, making your interaction with the Git Client more intuitive and user-friendly. It's also worth mentioning that now, when you clone a repository, the Git Client will automatically detect and open Oxygen project files. This feature simplifies the process of working with Oxygen projects that are stored in a Git repository. Other improvements added in version 5.2.0 of the Oxygen Git Client add-on include: * The absolute path to the working copy is now displayed in the tooltip of the Git Staging view's working copy combo box. * Enhanced remote change detection and refresh in History view for improved performance. * An issue has been fixed where untracked files were previously not being restored from a stash. * The integrated JGit library was upgraded to version 6.5. * Other bug fixes. For more information on the *Oxygen Git Client add-on* (including the installation steps), you can check the page below: https://www.oxygenxml.com/doc/ug-editor/topics/git-addon.html We hope that you will enjoy using the latest release of this add-on as much as we enjoyed developing it. As always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Version 5.2.0 of the Oxygen Batch Documents Converter add-on is now available!
by Alin Belu 24 Jul '23

24 Jul '23

Hello everyone, We are happy to announce that *version 5.2.0* of the *Oxygen Batch Documents Converter add-on* is now available! For the newest version of the add-on, our team of developers worked hard to bring you the following list of fixes and improvements to make sure that your document conversion process gets to be even smoother: *OpenAPI to DITA* * OpenAPI to DITA conversion now supports "*/*" MIME type documents. * Correct IDs are generated on topics with OpenAPI tags containing multiple words separated by spaces. * Preserve descriptions from responses during OpenAPI v2 conversion. *Word to HTML/DITA* * Tables from Word to HTML/DITA conversion now have 'frame', 'rowsep', and 'colsep' attributes. * No more duplicate IDs on resulting tables. * Default configuration for codeblocks in Word Styles Mapping table added. * Custom styles based on a normal style that don't have a Word style mapping are now properly reported as unknown. *Confluence to DITA* * Confluence to DITA conversion now handles duplicate IDs without errors. * Image paths no longer contain queries, preventing publishing errors. *Others* * Updated JTidy library to version 1.0.4. * Minimum required version of Oxygen increased to 25.1. * Removed the Jackson libraries as they are already available in Oxygen. 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