- oXygen-user - www.oxygenxml.com

[ANN] Oxygen AI Positron Assistant 2.0 adds Vision support and new productivity actions!
by Alin Belu 23 Apr '24

23 Apr '24

Hi everyone, We are proud to announce *version 2.0* of *Oxygen AI Positron Assistant*, the powerful tool that helps users increase their productivity by providing support for using AI-generated content within the Oxygen tools - Oxygen XML Editor/Author/Developer, Oxygen XML Web Author, and Oxygen Content Fusion! Version 2.0 adds support for *Vision* models, allowing the AI to read and interpret images that can be easily added by users to the prompts entered in the Chat window, thus supporting more use cases. A new action called *Generate Documentation Draft* is available that can be used to create a draft DITA topic. This feature provides users with control over the draft generation process, allowing them to specify the context for the new topic, instructions, and images. Furthermore, this version also introduces an action that enables users to get a proposal for updating a DITA topic after they update the images referenced in that topic, by having the AI analyze the new images and propose content changes. Two new variables that can be applied on content with tracked changes were introduced and they can be used to write prompts, enabling users to provide the AI with both the original and modified text and ask the AI engine to analyze the change. Additionally, users now have the ability to filter the list of AI actions and some of the most frequently used actions (e.g. Correct Grammar, Improve Readability, Use Active Voice) are now available as Quick Assist fixes. The Oxygen XML Enterprise edition license for Oxygen XML Editor, Author, and Developer products now includes access to the Oxygen AI Positron Assistant Enterprise add-on at no extra cost (provided their version is 26.0 or later). Moreover, the Enterprise version of the add-on allows users to connect directly to *Anthropic Claude* (in addition to the existing options for OpenAI and Microsoft Azure OpenAI Service). Additionally, from this release forward, Oxygen XML Web Author users also have access to the new Oxygen AI Positron Assistant Enterprise plugin for Web Author. 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

Add full stop to list item in Reusable content
by Oudkerk, Judith 22 Apr '24

22 Apr '24

Hi All, I was wondering if there’s a way to add a full stop to the final list item of reusable content. We have a list of items that are reusable, but each manual may use different list items. Therefore, the final list item may differ per manual. Since our Style guide dictates that only the final list item should have a full stop, it’s quite difficult to manage this list. Is there a way to add a full stop to the end of a list item outside the reusable content? I tried putting the list items in both <p> and <lines> elements, but then the full stop is placed on a new line in the output PDF: XML: PDF: [cid:image001.png@01DA949C.8EB2EA30] [cid:image003.png@01DA949C.C9088A00] Do you have any other ideas or suggestions? Thanks. 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:image717166.png@15A8DF8A.F1E27249] 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

2 2

[ANN] Oxygen XML Users Meetup @ XML Prague 2024
by Alin Belu 18 Apr '24

18 Apr '24

Hi everyone, The XML Prague Conference will take place between the 6th and the 8th of June, 2024, offering a unique opportunity for developers, markup enthusiasts, information managers, and students to come together in person. Continuing its tradition, the Oxygen XML team will be present at the conference, hosting an *Oxygen XML Users Meetup* on *June 6th*. This meetup provides attendees with firsthand insights into the latest developments straight from the dedicated individuals behind the Oxygen XML suite of products. We extend a warm invitation to all of you to join us at this event and discover the cutting-edge solutions and tools we've been developing. Don't miss this opportunity to meet the Oxygen XML team and stay at the forefront of XML innovation! To find out more about the *Oxygen XML Users Meetup* @ XML Prague 2024, you can check the published full agenda, here: https://www.oxygenxml.com/events/2024/oxygen_user_meetup_Prague.html All the best, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Webinar: What's New in Oxygen XML Web Author 26.1 (April 24th, 2024)
by Alin Belu 16 Apr '24

16 Apr '24

Hello, Starting next week, on *April 24th*, we kick off our brand-new series of Oxygen XML live webinars! Join us for our first exciting event where we will unveil the latest enhancements in Oxygen XML Web Author 26.1! In the *What's New in Oxygen XML Web Author 26.1* webinar, Bogdan Dumitru (software developer at Syncro Soft) will showcase a range of new features designed to enhance your authoring experience. Here's a sneak peek at some of the highlights that he'll be covering: - *User Authentication*: Enable secure access to Web Author, adding an extra layer of protection to content access and editing. - *AI Positron Assistant*: Experience the power of artificial intelligence with our enhanced Positron Assistant Side View. - *DITA Profiling improvements*: Easily manage and control your content by selectively showing or hiding specific sections based on DITAVAL filters, ensuring that only relevant content is displayed. - *DITA Project File and Context Filtering*: Set a DITA project file and context to filter document content. - *CSS Inspector Pane:* Check and fine-tune the styling and formatting of your content with the new CSS Inspector Pane. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2024-1.html We would also like to invite you to join us for our next upcoming webinars: * May 8, 2024 - Oxygen AI Positron: Your Helper in All Stages of Content Creation - https://oxygenxml.com/evs2024-2.html * May 22, 2024 - Web Author Customizations - Getting Started - https://oxygenxml.com/evs2024-3.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] Oxygen Content Fusion 6.2 is Now Available!
by Alin Belu 09 Apr '24

09 Apr '24

Hello everyone, We are proud to announce the immediate availability for *Oxygen Content Fusion version 6.2*, the web-based collaboration platform for content creation! The focus of this release was to redesign the user interface after analyzing the possible workflows, updating the layout to include more information and making the relevant actions at each step easily accessible, as well as updating the embedded visual editor that is based upon the Oxygen XML Web Author technology. The new layout adjusts the fonts and spacing to include more information on each page, provides intuitive navigation controls and, in some cases, it extends the working area to take advantage of the full width of the page. Users now have the ability to easily find the tasks they want to focus on by filtering the list of review tasks based on the task name. Task management actions can now be performed directly from the task list, so you can delete a task or mark it as integrated directly from the list of your tasks. The task activity view focuses on the changes made in each user interaction, but also provides actions to compare the selected version of the file with the latest version or open the latest version. Content Fusion's visual editor was updated to integrate the latest changes implemented in *Oxygen XML Web Author 26.1.0*. Some of the interesting new features added for the visual editor include the ability for DITA users to easily switch profiling conditions and choose whether to hide the excluded content or show it as grayed out, and the Outline pane also now distinguishes nodes filtered by a DITAVAL file. When Markdown content is pasted within DITA, DocBook, TEI, or XHTML documents, it is automatically converted to the target vocabulary by the smart paste functionality. The Unicode support was improved to better support surrogate characters (e.g. emoji characters) and the text mode is now available in read-only mode for concurrent editing sessions. Additionally, the Split action now automatically inserts required first child elements. When developers create customizations for the Web Author visual editor, they can now use the new CSS Inspector to easily view the styles applied to the selected element. Additionally, a validation process for uploading frameworks was introduced, ensuring that customized frameworks remain error-free. To enhance the filtering capabilities, a new loading option is available that allows plugin developers to control whether content excluded by a DITAVAL filter is displayed as grayed out or completely hidden. Furthermore, a new API that enables the addition of a toolbar in a side view empowers developers to better customize the layout of the side-views contributed by their plugins. For more information, see: https://www.oxygenxml.com/content_fusion/whats_new.html We hope you will enjoy our latest release! 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-14072] Add custom catalog to OT build
by Oxygen XML Editor Support (Radu Coravu) 27 Mar '24

27 Mar '24

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

2 1

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

27 Mar '24

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

1 0

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

25 Mar '24

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

1 0

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

14 Mar '24

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

1 0

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

13 Mar '24

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

1 0