- oXygen-user - www.oxygenxml.com

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

[ANN] Webinar: Introducing Oxygen Content Fusion 6.0 Beta (July 26, 2023)
by Alin Belu 18 Jul '23

18 Jul '23

Hello, With the release of the Beta version of Oxygen Content Fusion 6.0, we aimed to enhance the DITA documentation review and publishing processes for the advanced online collaboration platform. As we approach the full release, we highly value your feedback and invite you to actively participate in shaping the final version of Oxygen Content Fusion 6.0, as your insights will play a crucial role in refining this cutting-edge collaboration platform. Thus, next week, on the *26th of July*, join us for the exclusive webinar titled*Introducing Oxygen Content Fusion 6.0 Beta*, where Cristian Talau (project manager at Syncro Soft) will showcase the significant improvements and features of Oxygen Content Fusion 6.0 Beta. The topics of this webinar will focus on the following features and improvements of Oxygen Content Fusion 6.0 Beta: * *Projects:* Seamlessly integrate with Git repositories to track reviewers feedback on dedicated branches for each review task. * *Enhanced Publishing Capabilities:* Effortlessly generate WebHelp or PDF outputs with new publishing features. Customize the output via the integrated Oxygen Styles Basket visual customization tool, providing easy and flexible customization options. * *Improved Review Workflow:* Review task owners now have the ability to close a review, allowing time to address feedback effectively. * *Optimized User Experience:* Alongside the introduction of numerous new features, Oxygen Content Fusion's user interface has undergone enhancements, now offering an improved and refreshed look and feel. This is a free event, but registration is required. You can register at https://www.oxygenxml.com/evs2023-9.html To stay in touch with us and discover what other events we have planned for you, please make sure to check https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Re: [oXygen-user] [OXYGEN-6406] The text in Oxygen is fuzzy with my new laptop
by Oxygen XML Editor Support (Adrian Buza) 07 Jul '23

07 Jul '23

Hi, I'm guessing this is v25.1 of Oxygen. Please specify if otherwise. The problem is most likely with the Windows scaling setting, probably different for each monitor. The old laptop probably had the same scaling for both (or a single setting system-wide). *Under Windows Settings > Display settings, check the display resolution and "scale and layout" for each monitor.* Currently Oxygen is only System DPI Aware, it is not Per-Monitor DPI Aware. So if you have two monitors (or laptop screen and monitor) with different DPI/scaling settings, it cannot change the scaling dynamically, if move it to another monitor. Oxygen uses the system wide scaling setting (the one of the primary display) detected at application startup, not the monitor-based scaling setting. * **Quick-fix to try, move Oxygen to the monitor you intend to use it on and restart Oxygen.* Regards, Adrian Adrian Buza oXygen XML Editor and Author Support On 06.07.2023 20:21, Roger L Costello wrote: > > Hi Adrian, > > Sorry, I should have provided the OS. I am running Windows 10. It is > the entire UI that is fuzzy. I should also mention that my laptop is > connected to a large monitor; I am viewing Oxygen on the monitor. No > fuzziness viewing Oxygen on the monitor from my old laptop. > > /Roger > > *From:*oXygen-user <oxygen-user-bounces(a)oxygenxml.com> *On Behalf Of > *Oxygen XML Editor Support (Adrian Buza) > *Sent:* Thursday, July 6, 2023 10:15 AM > *To:* oxygen-user(a)oxygenxml.com > *Subject:* [EXT] Re: [oXygen-user] [OXYGEN-6406] The text in Oxygen is > fuzzy with my new laptop > > Hello, On what OS is Oxygen running (macOS/Windows/Linux)? What > version and build of Oxygen are you using (Help > About)? Is the > entire Oxygen UI fuzzy, or just the text in the editor? Regards, > Adrian Adrian Buza oXygen XML Editor and Author > > Hello, > On what OS is Oxygen running (macOS/Windows/Linux)? > What version and build of Oxygen are you using (Help > About)? > Is the entire Oxygen UI fuzzy, or just the text in the editor? > Regards, > Adrian > Adrian Buza > oXygen XML Editor and Author Support > On 06.07.2023 14:45, Roger L Costello wrote: > > I got a new laptop. > > > > When I open a browser everything in the browser screen is sharp and clear. > > > > When I open an XML document in the Oxygen editor the text is fuzzy. Any suggestions on what to do to make the text sharp and clear? > > > > /Roger > > _______________________________________________ > > oXygen-user mailing list > > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> > > https://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com <mailto:oXygen-user@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

Re: [oXygen-user] [OXYGEN-6406] The text in Oxygen is fuzzy with my new laptop
by Oxygen XML Editor Support (Adrian Buza) 06 Jul '23

06 Jul '23

Hello, On what OS is Oxygen running (macOS/Windows/Linux)? What version and build of Oxygen are you using (Help > About)? Is the entire Oxygen UI fuzzy, or just the text in the editor? Regards, Adrian Adrian Buza oXygen XML Editor and Author Support On 06.07.2023 14:45, Roger L Costello wrote: > I got a new laptop. > > When I open a browser everything in the browser screen is sharp and clear. > > When I open an XML document in the Oxygen editor the text is fuzzy. Any suggestions on what to do to make the text sharp and clear? > > /Roger > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

[ANN] Content Fusion version 6.0 Beta is now available for evaluation!
by Alin Belu 06 Jul '23

06 Jul '23

Hello, We are proud to announce the immediate availability of the *Beta* version for *Oxygen Content Fusion 6.0*, the web collaboration solution for structured documents! *Oxygen Content Fusion 6.0* introduces a lot of interesting and substantial improvements for the online collaboration platform designed to improve the DITA documentation review and publishing processes. Note that this is currently a *Beta* version of the 6.0 release cycle, so user feedback is welcomed and considered especially helpful as we prepare for the full release. Some of the most interesting new features and improvements implemented in this version include: * 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' suggestions are tracked on a dedicated branch in the Git repository. * New publishing features help authors build *WebHelp and PDF outputs*. * Some built-in templates are available for adjusting the look and feel of the WebHelp or PDF output and the *Oxygen Styles Basket has been integrated* to make it very easy to customize the output using CSS styling. * Review task owners now have the *ability to close a review* to give them time to address feedback or make their own changes before integrating them back into the documentation project. * Numerous enhancements were made to the Content Fusion browser interface to make navigation easier and workflows more efficient. * Bug fixes and security enhancements were also implemented, and various internal components were updated. For more information about the Beta version for Oxygen Content Fusion 6.0 and more details of what was added in this version, see: https://www.oxygenxml.com/content_fusion/6_beta.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

The text in Oxygen is fuzzy with my new laptop
by Roger L Costello 06 Jul '23

06 Jul '23

I got a new laptop. When I open a browser everything in the browser screen is sharp and clear. When I open an XML document in the Oxygen editor the text is fuzzy. Any suggestions on what to do to make the text sharp and clear? /Roger

1 0

[Ann] New maintenance build available for oXygen 25.1 (2023070306)
by Oxygen XML Editor Support (Adrian Buza) 04 Jul '23

04 Jul '23

Dear oXygen users, We announce the release of a new maintenance build (2023070306) for oXygen 25.1 (XML Editor, XML Developer, XML Author, XML WebHelp, 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#2023070306 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] The new Oxygen AI Positron Assistant brings chat history, editable entries, user-defined actions, and more!
by Alin Belu 03 Jul '23

03 Jul '23

Hello everyone, We are thrilled to introduce you to the newest version of the *Oxygen AI Positron Assistant* add-on! Version 0.9.3 comes with several exciting features, including a *chat history* so you can revisit previous chats and continue where you left off, *editable user entries* in chat to modify conversations and explore different paths, the introduction of *user-defined actions*, and the possibility to *provide project-specific details for more accurate AI responses*. The *AI Positron Chat* now provides an overall improved experience with the addition of the *History* drop down toolbar button that allows you to go back to previous conversations and continue them. You can also*edit prompts* in the chat discussion thread so you can change the conversation and continue from any point if you want to explore a different path. Additionally, the AI response appears incrementally, as soon as the AI starts generating it, and you now have the option to stop the generation of a response early if you do not consider it fit for your needs. Version 0.9.3 also introduces *user-defined AI actions*. The same approach used for defining built-in actions can now be used to specify actions on the client side through the usage of a JSON configuration file. It may even be linked to a project, making it simple to share actions with everyone who works on a certain project. The newest version of the add-on comes with the possibility to provide *additional options for an action*. To avoid creating too many related actions, it is now possible to specify different facets for an action that the user can choose. This can be best seen in the action that generates short descriptions, as it uses this customization to allow users in choosing different writing styles, such as clear or engaging, as well as setting the number of expected sentences that will be generated. The Oxygen AI Positron Assistant now enables you to *configure a context for all prompts* in the AI Positron Assistant Preferences page. This can be set to be project specific and it allows you to pass certain information to all the built-in actions, so that the AI model will generate better and more relevant results, as it becomes more knowledgeable about your context. It is also worth mentioning that the AI Positron *activity messages have been integrated into the AI Chat view* for a more streamlined and consolidated user experience, thus making the AI Activity View not needed anymore. For additional information on the *Oxygen AI Positron Assistant*, including the installation instructions, you can check out this article on the Oxygen XML Blog: https://blog.oxygenxml.com/topics/ai_positron.html For an in-depth presentation of the various features and use cases for the *Oxygen AI Positron Assistant*, you can view the recent recording of the *AI as a Tool for Technical Content Creation* webinar - https://oxygenxml.com/evs2023-7.html We want to remind you that we plan to frequently release new features and improvements, so please let us know what you think about the current version and stay tuned for exciting new versions of this add-on! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Webinar: Leveraging the Power of AI and Schematron for Content Verification and Correction (July 5, 2023)
by Alin Belu 29 Jun '23

29 Jun '23

Hello, Your journey into the world of AI continues next week, on the *5th of July*, with the *Leveraging the Power of AI and Schematron for Content Verification and Correction* webinar! During this 1-hour live event, Octavian Nadolu (project manager at Syncro Soft) will be exploring the application of AI in conjunction with Schematron and Schematron Quick Fix (SQF) for content verification and correction. He will begin with a comprehensive overview of AI before going on to highlight the potential advantages it brings and shed light on the challenges we may encounter when utilizing AI for these purposes. Don't miss this opportunity to gain valuable insights into the intersection of AI and content validation by exploring topics such as: * Artificial Intelligence (AI) * OpenAI/Generative Pre-trained Transformer * Schematron and Schematron Quick Fixes (SQF) * Implementing AI in Schematron and SQF * Examples of AI-driven Schematron and SQF Solutions * Benefits of Using AI in Schematron and SQF This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-8.html To stay in touch with us and discover what other events we have planned for you, please make sure to check https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Why is the JSON Schema $anchor not supported?
by Roger L Costello 22 Jun '23

22 Jun '23

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"...

1 0

[ANN] Webinar: AI as a Tool for Technical Content Creation (June 28, 2023)
by Alin Belu 15 Jun '23

15 Jun '23

Hello, On the *28th of June*, we invite you to join us for one of the most anticipated Oxygen XML live events - the *AI as a Tool for Technical Content Creation* webinar! In recent months, AI technology has advanced to the point where it is now applicable in a wide range of real-world situations. However, the AI-generated content is not always accurate, making it challenging to introduce this technology to end users. On the other hand, this is precisely why technical writers are an excellent fit for AI since they can serve as mediators between the AI and the end users, using it to boost their productivity while ensuring the content that they deliver is accurate. *Oxygen AI Positron Assistant* is a new plugin for the Oxygen XML tools that connects to the Open AI Chat GPT engine, introducing AI technology for supporting technical writing operations. To keep authors in control, the workflows are optimized to include preview of proposed AI changes and the possibility to refine the results. Custom AI interactions are also possible, and you can easily reuse them with support to save them as favorites. During this 1-hour live webinar, Sorin Carbunaru (senior software developer at Syncro Soft) will: * Show various use cases for the *Oxygen AI Positron Assistant*. * Explore the available actions and show how they can be invoked, refined, and the results previewed in the visual diff to analyze the document changes. * Demonstrate how you can define your own AI processing actions and mark them as favorites. * Highlight the tasks best suited for AI technology use. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-7.html To stay in touch with us and discover what other events we have planned for you, please make sure to check https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] New release of Oxygen AI Positron Assistant brings chat, preview, new actions, and more
by Alin Belu 29 May '23

29 May '23

Hello everyone, We are excited to announce a new release for the *Oxygen AI Positron Assistant* add-on! Version 0.9.2 comes with a variety of exciting new features, including chat functionality, the ability to preview changes, AI-based quick fixes, AI-based XPath extension functions, and new AI actions for grammar corrections, content rewriting, and checking how your content responds to specific questions. The *AI Positron Chat* side-view provides a better user experience and more control when invoking AI actions, allowing you to see the response and preview its impact on the document using an action that triggers the visual XML-aware comparison. You can also further refine the responses by continuing the discussion with the *AI Positron* platform in the chat view. In a chat message, you can use editor variables that expand to the selected content or the entire document. These allow you to define flexible prompts, and the support to save favorites enables you to store and easily reuse the prompts you find useful. Along with the preview action for the AI responses, you can also use actions to insert the response into your document or copy the response to the system clipboard. Version 0.9.2 of the add-on improves the existing actions and contributes new AI actions: * *Correct Grammar* - Corrects the grammar and spelling of the selected content. * *Use Active Voice* - Converts the selected content from passive voice to active voice. * *Generate Questions* - Displays possible questions that the selected content or the entire document responds to. * *Answer Questions* - Displays AI responses to your questions found in either the selected content or the entire document. The add-on now also helps you with validation problems. If an error message provides a good description of the identified problem and eventually a hint on how to fix it, which is typically the case with Schematron errors, then you can take advantage of the *AI Positron Fix* quick-fix action that tries to find a solution to the validation problem. This action can be triggered from the contextual menu for the validation problems that are displayed in the application's Problems list. The add-on now also contributes two *XPath extension functions* that can be used from XSLT stylesheets, XQuery scripts, and from Schematron schemas to process content or to perform validation checks on existing content. Custom XML refactoring operations (based on XSLT or XQuery) can also take advantage of these AI functions, so you can apply batch processing on multiple documents. For additional information on the *Oxygen AI Positron Assistant* add-on, including the installation instructions, you can check out this article on the Oxygen XML Blog: https://blog.oxygenxml.com/topics/ai_positron.html We want to remind you that we plan to frequently release new features and improvements, so please let us know what you think of the current version and stay tuned for exciting new versions of this add-on! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] OpenAPI Documentation add-on version 2.2.0 is now available!
by Alin Belu 26 May '23

26 May '23

Hello everyone, We are excited to announce the release of *version 2.2.0* for the *OpenAPI Documentation add-on*! *Version 2.2.0* sees the implementation of useful upgrades, such as: * The addition of an option to transform the OpenAPI content into DITA output. * The "examples" element is now rendered when transforming to HTML output. * A detailed warning message is now displayed when the transformation’s target file has unsaved changes. For more information regarding the OpenAPI Documentation add-on, check out the following page from our documentation: https://www.oxygenxml.com/doc/versions/25.1/ug-editor/topics/openapi-docume… We hope you will find the newest version of our add-on useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

VBA to XSLT function conversion
by Sudhakara Allam 26 May '23

26 May '23

Hi, I am trying to convert xslt with msxls vbscript generated out of MS Access application to xslt only file by converting VBScript functions to xslt native functions. Does Oxygen have this functionality? It may not have to be automated, however, beneficial if it could. Please let me know. Regards, Sudhakar

1 0

Schematron doesn't respect the full path in the test attribute.
by Danny MacMillan 18 May '23

18 May '23

Hello, Consider the following XML: <?xml version="1.0"?> <root> <relevant> <element relevant-attribute="this attribute exists only on elements under relevant"/> </relevant> <irrelevant> <element/> </irrelevant> </root> And the following Schematron: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> When I validate the XML with the Schematron, Oxygen prints a warning that an empty sequence is not allowed as the second argument to map:contains, which I've determined is because it is testing the "element" elements under "irrelevant". I know this because if I add a second such element, the error prints twice. If I have 9, the error prints 9 times. But why is it testing that element? I deliberately used xpath that navigates via the parent because I want to include only elements under that parent, but it seems that it's looking at all elements, anywhere in the document, named 'element'. Is this expected? I can silence the warning if I explicitly check for the presence of the attribute: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[@relevant-attribute and map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> But not if I precede the broken rule with a rule that should equivalently prevent the broken rule from firing on those elements: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[not(@relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> <rule context="/*/relevant/element[map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> Thanks, -- Danny MacMillan Sent with [Proton Mail](https://proton.me/) secure email.

3 4

Schematron validation of documents using XInclude succeeds when it should fail.
by Danny MacMillan 12 May '23

12 May '23

Hello, I'm going through the Schematron book by Erik Siegel and one of his examples improperly passes validation in Oxygen XML while it correctly fails validation using SchXslt. The code for the book is here: [https://github.com/xatapult/schematron-book-code](https://github.com/xatapu… I open both examples/additional-features/subdocuments-1.sch and data/subdocuments-master.xml from that project in Oxygen and select the tab with the XML file. Then I click the dropdown on the Validation button on the toolbar and click Validate with... and then I select the subdocuments-1.sch file using the dropdown. When I proceed Oxygen says it passes. This is the same approach I have used for all other examples in the book. But I created an explicit validation scenario for this also and it behaves the same way. Note that if you want to test this you should clone the repository because the subdocuments-master.xml file incorporates other files in the repository by reference using XInclude and this is indeed what seems not to be working in Oxygen. By contrast if I run the same validation using the schxslt-cli.jar I get the following, expected result. [invalid] /home/user/task/schematron-book-code/data/subdocuments-master.xml [invalid] /home/user/task/schematron-book-code/data/subdocuments-master.xml failed-assert /Q{}document[1]/Q{}p[1] The class brightred is forbidden (file:/home/user/task/schematron-book-code/data/subdocuments-2.xml)! I am using the latest Oxygen: <oXygen/> XML Editor 25.1, build 2023042509 Thanks, -- Danny MacMillan Sent with [Proton Mail](https://proton.me/) secure email.

3 4

MSXML4 Not found on windows
by Karl Stubsjoen 03 May '23

03 May '23

Is there a guide to download and install the latest MSXML engine for Windows/Oxygen? My Oxygen is failing to transform using MSXML4, the error is: Could not create the 'MSXML2.DOMDocument.4.0' object. Make sure that MSXML version 4.0 is correctly installed on the machine. Karl.. Karl Stubsjoen (602) 845-0006

1 0

[ANN] Boost your productivity with the new Oxygen AI Positron Assistant plugin!
by Alin Belu 03 May '23

03 May '23

Hello everyone, In the recent months, AI technology reached a point where it became useful in many real life scenarios. However, the AI generated content is not 100% accurate, which makes this technology difficult to deploy directly to end users that expect to only receive correct information. On the other hand, users who understand that AI-generated content is only a starting point, a hint, or a suggestion, and that they are in control of the final form, will experience an increase in productivity because the AI generated content will speed up many of their tasks. The new *Oxygen AI Positron Assistant* plugin provides the bridge between AI and Oxygen users, helping them access AI-enabled tools to speed up content creation. The plugin contributes helper actions that can be used to *generate content*: * You can start typing a phrase and use the *Continue writing* action to get a suggestion for continuing the phrase. * You can write instructions for content that you want to be generated and use the powerful and flexible *Follow instructions* action to add the generated content in the document. A group of *translation actions* will try to preserve the XML markup structure while translating the content to *French*, *German*, *Japanese*, or *English*. To obtain *overview* information, you can use an action to *summarize* the selected content or to get *readability* suggestions. *DITA Topic Tools* actions allow you to perform DITA-aware tasks, such as: * Automatically create the *short description* for a topic, summarizing its content. * Generate *index terms* in the prolog section of a topic by analyzing the topic content and extracting relevant terms. * Turn a phrase that enumerates some options into a list with the *Itemize* action. * Flatten a list into content that enumerates the options from the list with the *Join Items* action. * *Generate a new DITA topic* from a title or a short description by expanding the content. * Replace content with a version that*improves its readability*. The Oxygen AI Positron Assistant plugin contributes its actions to the main menu, contextual menu, and in the *AI Positron Assistant* view. When invoking an action, you can monitor its progress and see the results in the *AI Positron Activity* view. To enable the AI features, you need to connect the plugin to the *Oxygen AI Positron* service platform that now uses the Open AI API to access models like Chat GPT, GPT-4, etc. The initial release of the Oxygen AI Positron Assistant plugin is currently in an experimental phase, enabling users to perform up to 250 actions per month, but we expect to provide subscription options in the near future. We anticipate releasing new features and updates often, so please share your feedback about the current version and stay tuned for exciting new versions of this plugin. For additional information on the *Oxygen AI Positron Assistant* plugin, including the installation instructions, you can check out the following article written by Radu Coravu for the Oxygen XML Blog: https://blog.oxygenxml.com/topics/ai_positron.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[Ann] New maintenance build available for oXygen 25.1 (2023042509)
by Oxygen XML Editor Support (Adrian Buza) 26 Apr '23

26 Apr '23

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

Webhelp search: jump to result when opening a found topic?
by Franz-Josef Knelangen 24 Apr '23

24 Apr '23

Hi there, if a user searches our webhelp and finds the one result, say, in a large reference topic, after clicking on that topic it shows the beginning of the file. How could I achieve that the display jumps to the highlighted search word instead? 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.)

2 1

Improve the schema that gets created with Tools -> Generate/Convert Schema
by Danny MacMillan 20 Apr '23

20 Apr '23

Hello, I work with a third party application that produces a large number of XML files. The third party does not make a schema for these files available to me. All I can do is use Oxygen to infer a schema by pointing it at a population of these files. I need to read and manipulate the XML files in Kotlin code. I have been using Tools -> Generate/Convert Schema to create a schema, then processing that schema with JAXB as you ordinarily would. The schemas that Oxygen produces are completely reasonable, but there are some things I'd like to change. In one case I have an element named 'de' that occurs twice. The Generate/Convert Schema tool assumes (or seems to) that these elements describe the same kind of data and it merges their definitions. In fact though, the elements represent entirely different kinds of data. There's no overlap of attributes between the 'de' elements in the first place and the 'de' elements in the second place. So Oxygen doesn't mark any of the attributes as required, when in fact, they're all required in their proper context. The schema also uses anonymous complex types for each element and I'd rather it used named types. I can and will have to edit the schema Oxygen creates to take care of a few things, but I'd like to minimize the amount of manual editing I have to do, because I'll have to repeat this process in the future as the third party software version increases and/or I have to deal with new XML files created from different environments that happen to include elements I haven't yet encountered. What affordances are there for customizing the behaviour of the generate schema tool? The dialog box doesn't have much on it. Alternately, are there other tools I could use to post-process the schema in an automated fashion to get it closer to what I want? I see there's a flatten schema feature but it didn't do much other than re-order the attributes. Thanks, -- Danny MacMillan

1 0