November 2023 - oXygen-user - www.oxygenxml.com

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