- oXygen-user - www.oxygenxml.com

Going from FrameMaker to oXygen / FM Structure View vs. oXy Outline View / Feature request
by Frank Dissinger 09 Jan '23

09 Jan '23

Hi Alan, Thank you for your reply. I fully agree with what you wrote about FM's Structure View. An excellent tool. It would be great if oXygen could enhance its Outline View and make it work in a similar way. I am especially missing the following features: * Allow users to place the cursor between tags, or at the beginning/end of the element contents, and indicate the position * Display attributes: Toggle between all/all with a value/none (no need to waste room on the screen for a separate Attributes window) * Expand/collapse complete tree of elements or attributes in one go (Shift-click) * Element content should not be repeated for empty wrapping elements, this is confusing (show it only once) For exmaple, for <li><p>Text..., the "Text" is shown both for <li> and <p>. It should only be shown for <p>. Can I add this as feature request? I have now switched to the oXygen Users Mailing List and will post any further oXygen-related issues there. Regards, Frank ------------------------------------------------------------------------ Am 04.01.2023 um 22:05 schrieb Alan Houser: > Chiming in a bit late here. Longtime structured FrameMaker and oXygen > user... > > *Frank mentions the FrameMaker structure view. IMO, this is the best > and most distinctive part of the FrameMaker structured authoring > interface. Easy access to any part of the document. Expand/collapse at > any level of the document hierarchy; locally or globally (e.g. > expand/collapse "this" section; expand/collapse all sections). Full > navigation capabilities. Visual feedback (and shortcut control) over > cursor location -- beginning, middle, or end of an element. > Configurable and interactive attribute display.* > * > * > *While most XML editors provide some sort of outline view, I've never > seen one as full-featured and useful as the FrameMaker structure view.* > > I occasionally use the oXygen Outline View for quick navigation in > larger XML documents. And the "folding" feature in the edit window to > expand/collapse content. But these don't fully replace what one can do > with the FrameMaker structure view. > > I think you will find that oXygen provides more and different features > than Structured FrameMaker, many of which you will come to appreciate. > I suggest (as you are doing) learning how to be most productive with > the oXygen features and workflow. And be prepared to miss the > FrameMaker structure view. 🙁 > > -Alan > -- > Alan Houser > Group Wellesley, Inc. > Consultant and Trainer, Technical Publishing > arh on Twitter > 412-450-0532 > > > >> On Dec 8, 2022, at 10:37 AM, Frank Dissinger >> <frank.dissinger(a)cgs-oris.com> wrote: >> >> Thank you, >> >> Chris >> Radu >> Stefan >> Thomas >> Yves >> >> for your replies, this valuable information and for offering me your >> help. >> >> I have already made some initial progress. I have successfully >> created a custom framework with my own CSS file and are getting my >> topic editor window panel look more and more the way I like (using >> the 'print-ready' display style). >> >> I'll try to dig a bit deeper into this matter and will collect the >> questions and issues as I get on with this. I'll then come back to you. >> >> Best regards, >> >> Frank >> >> ------------------------------------------------------------------------ >> Am 06.12.2022 um 17:42 schrieb Frank Dissinger: >>> Hi all, >>> >>> Are there any passionate long-term structured FrameMaker users who >>> have changed to oXygen as a DITA editor? Has anybody tried to set up >>> the oXygen authoring environment as close as possible to >>> FrameMaker's WYSIWYG view? Or at least in a way that makes the >>> switch as painless as possible for a FrameMaker user? >>> >>> I've been using FrameMaker V11+DITA-FMx as a DITA editor for many >>> years -- until recently also as a PDF transformation engine, which I >>> have now replaced with MiramoPDF. I have used oXygen for a few years >>> only and mostly as a transformation engine. With FM I am stuck with >>> an old DITA implementation and the DITA-FMx plug-in is not developed >>> any further. This is why I would like to use oXygen as a DITA editor >>> instead. But I find it very hard to make the switch: The way DITA >>> maps, topics, tags, structures... are presented is so different and >>> I haven't the time to learn oXygen properly and in full detail. It's >>> such a powerful tool with tons of features. So I thought there may >>> be someone who can help me getting started -- at least with setting >>> up the user interface and authoring environment. >>> >>> A few examples of things I am struggling with right away when I look >>> at how oXygen presents my DITA files: >>> >>> * It seems that a DITA map loads all the referenced submaps and >>> displays all of these maps in a single window panel (as if this >>> was a single file). In FM I see only the references and open the >>> submaps as separate files by double-clicking on them. >>> * I feel lost in these maps. There are lots of big fonts, frames, >>> colored backgrounds, icons... Can I customize the appearance? >>> For example, by defining CSS-like styles for the DITA elements >>> displayed on the screen? >>> * The Outline view is a bit similar to FM's Structure View. But I >>> am used to setting the cursor into the Structure View to >>> precisely define the point where to insert an element. This does >>> not work in oXygen. >>> * I'd like to see text and images without any tags in one window >>> panel and the DITA structure with elements and attributes in a >>> separate panel. I know I can switch off tags and use the Outline >>> view, but I am not sure if this really gives me full control >>> over everything... >>> * How does oXygen visualize conditionalized content >>> (included/excluded via a ditaval file)? >>> * Can I define a fixed page size in oXygen? I'd like to set a page >>> width (height is not important) to make sure that images fit on >>> the page and that table columns are not too narrow (in PDF >>> deliverables). Setting an image resolution is also important. >>> * ... >>> >>> Regards, >>> >>> Frank >> -- >> *Frank Dissinger* >> Documentation Manager >> .................................................................... >> *CGS Publishing Technologies International GmbH* >> *Email*frank.dissinger(a)cgs-oris.com|*Web*www.cgs-oris.com >> <http://www.cgs-oris.com/> >> *Address*Kettelerstr. 24 | D-63512 Hainburg | Germany >> *Phone*+49 6182 9626-27 |*Fax*+49 6182 9626-99 >> *Commercial register*Offenbach, HRB no. 21495 >> *Managing directors*Bernd Rückert, Christoph Thommessen >> >> https://www.cgs-oris.com/Signatur.png <https://www.cgs-oris.com/signatur> >> _._,_._,_ >> ------------------------------------------------------------------------ > > _._,_._,_ > ------------------------------------------------------------------------ > Groups.io Links: > > You receive all messages sent to this group. > > View/Reply Online (#47170) > <https://dita-users.groups.io/g/main/message/47170> | Reply To Group > <mailto:main@dita-users.groups.io?subject=Re:%20Re%3A%20%5Bdita-users%5D%20Going%20from%20FrameMaker%20to%20oXygen> > | Reply To Sender > <mailto:arh@groupwellesley.com?subject=Private:%20Re:%20Re%3A%20%5Bdita-users%5D%20Going%20from%20FrameMaker%20to%20oXygen> > | Mute This Topic <https://groups.io/mt/95496909/2470666> | New Topic > <https://dita-users.groups.io/g/main/post> > Your Subscription > <https://dita-users.groups.io/g/main/editsub/2470666> | Contact Group > Owner <mailto:main+owner@dita-users.groups.io> | Unsubscribe > <https://dita-users.groups.io/g/main/leave/5778861/2470666/1973504771/xyzzy> > [frank.dissinger(a)cgs-oris.com] > > _._,_._,_ -- *Frank Dissinger* Documentation Manager .................................................................... *CGS Publishing Technologies International GmbH* *Email *frank.dissinger(a)cgs-oris.com | *Web* www.cgs-oris.com <http://www.cgs-oris.com/> *Address* Kettelerstr. 24 | D-63512 Hainburg | Germany *Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99 *Commercial register* Offenbach, HRB no. 21495 *Managing directors* Bernd Rückert, Christoph Thommessen https://www.cgs-oris.com/Signatur.png <https://www.cgs-oris.com/signatur>

2 1

[ANN] Webinar: Validating XML and JSON Documents Using Oxygen Scripting (January 11, 2023)
by Alin Belu 04 Jan '23

04 Jan '23

Hello, What better way to kick off the new year than with the Oxygen XML Editor series of live events? So, next Wednesday, on *the 11th of January*, we invite you to the *Validating XML and JSON Documents Using Oxygen Scripting webinar*! With the latest release of the Oxygen suite of products, additional support was added for validating XML and JSON files via Oxygen XML Scripting. In this webinar, Octavian Nadolu (project manager at Syncro Soft) will cover details about this newly implemented validation scripting support, as well as showing examples of how to use it efficiently. By the end of the webinar, you will know how to validate files or directories from a command line interface and check that your documents are valid from an integration server, as well as having the possibility to generate reports in several formats (text, XML, JSON, or an HTML visual format). We won’t be stopping there, as we will also be looking at how you can use transformation or comparison scripts. During this 1-hour live event, Octavian will focus on showing you how to: - Use the Validation command-line script - Validate against a specific schema file - Validate using the default Oxygen validation scenarios - Use the validation scenario from either a scenarios file or a project file - Generate the validation results in various formats (YAML, JSON, XML, HTML) - Run validation on a continuous integration (CI/CD) server - Make use of the Transformation command-line script - Utilize the Comparison/Merge command-line script This is a free event but registration is required. You can register at https://www.oxygenxml.com/evs2023-1.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] Custom DTDs with default Oxygen OT
by Scott Prentice 21 Dec '22

21 Dec '22

Thanks, Stefan! Yeah .. I was hoping to avoid having the users install a plugin .. just install the framework. But I can see that's not going to fly. I'm thinking that the simplest (least effort for the users, and least opportunity for error), is to provide a pre-configured OT installation that they can point to from Preferences. It'll just be .. 1) Install framework, 2) Point to custom OT in Preferences That way if something goes sideways, they haven't messed with the detail Oxygen installation. Cheers, ...scott On 12/20/22 11:33 AM, Stefan Jung wrote: > Hey Scott, > > You should bundle the grammar files in a toolkit plugin. This is > correct. In your oxygen framework you need to configure the matching > rules to recognize your custom grammar files. You need to install your > plugin to the DITA-OT as well. You need to use > the dita.specialization.catalog.relative extension point in your > plugin.xml. > > BR > > > > Gesendet mit OX Mail > > Scott Prentice <sp14(a)leximation.com <http://sp14@leximation.com>> hat > am December 20, 2022 um 8:25 PM geschrieben: > > I think I know the answer to this question, but want to confirm > that I'm not missing something. > > I've got a set of custom DITA DTDs wrapped up in an OT plugin. If > I install this plugin in the OT, I'm able to successfully generate > output from content that uses the public IDs defined by those > DTDs. However, what I'd like is to include this plugin in an > Oxygen framework, and have the custom doctypes honored for OT > builds without "installing" the plugin. > > As it stands, users can install the framework and edit topics and > maps using the custom doctypes. It validates fine and all is well, > but when they go to do an OT build, it fails to recognize the > location for the custom DTDs. > > I thought there was an OT parameter that let you specify the > location of an alternate catalog file, but I'm not seeing that. > Was hoping that I could get this to work by just having the users > install the framework. > > It seems like my only options are (after installing the framework) .. > > - install and integrate the "doctypes" plugin into the default OT > in Oxygen > > - OR .. provide another OT that has the doctypes plugin installed > and have the users point to that as a custom DITA-OT in Oxygen > > Thoughts? > > Thanks! > ...scott >

2 3

Custom DTDs with default Oxygen OT
by Scott Prentice 20 Dec '22

20 Dec '22

I think I know the answer to this question, but want to confirm that I'm not missing something. I've got a set of custom DITA DTDs wrapped up in an OT plugin. If I install this plugin in the OT, I'm able to successfully generate output from content that uses the public IDs defined by those DTDs. However, what I'd like is to include this plugin in an Oxygen framework, and have the custom doctypes honored for OT builds without "installing" the plugin. As it stands, users can install the framework and edit topics and maps using the custom doctypes. It validates fine and all is well, but when they go to do an OT build, it fails to recognize the location for the custom DTDs. I thought there was an OT parameter that let you specify the location of an alternate catalog file, but I'm not seeing that. Was hoping that I could get this to work by just having the users install the framework. It seems like my only options are (after installing the framework) .. - install and integrate the "doctypes" plugin into the default OT in Oxygen - OR .. provide another OT that has the doctypes plugin installed and have the users point to that as a custom DITA-OT in Oxygen Thoughts? Thanks! ...scott

1 0

[ANN] The DITA-OT Day 2022 recordings have arrived!
by Alin Belu 20 Dec '22

20 Dec '22

Hi everyone, As you know, last month, Oxygen XML Editor once again hosted the DITA-OT Day conference, the full day conference dedicated to the DITA Open Toolkit project. So, we want to properly thank everyone involved that made this 7th edition such a great experience for us, from the attendees to the presenters and supporters (Comtech, Bluestream, Antenna House, IXIASOFT, Miramo). THANK YOU for joining us in 2022 and know that we can't wait to see each other again in the years to come! Until then, you can click the link below to get access to the entire library of recordings of this year's DITA-OT Day presentations, as well as to the full gallery of candid photos: https://www.oxygenxml.com/events/2022/dita-ot_day.html All the best, Alin -- Alin Belu Oxygen XML Editor

1 0

Generate Sample XML Files --> not working correctly
by Roger L Costello 19 Dec '22

19 Dec '22

Hi Folks, Sadly, Tool >> Generate Sample XML Files is not working correctly. It fails to generate lots of elements. For example, in my schema is an element with 11 child elements; the tool generated the element but with no content. It also fails on elements with a type that extends another type. Yes, I know to click on "generate optional elements." Sorry, I cannot share my schema. I am using Oxygen version 25.0 /Roger

3 2

[Ann] New maintenance build available for oXygen 25.0 (2022121306)
by Oxygen XML Editor Support (Adrian Buza) 13 Dec '22

13 Dec '22

Dear oXygen users, We announce the release of a new maintenance build (2022121306) for oXygen 25.0 (XML Editor, XML Developer, XML Author, 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#2022121306 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] Version 5.1.0 of the Oxygen Batch Documents Converter add-on has been released!
by Alin Belu 09 Dec '22

09 Dec '22

Hello everyone, We are excited to announce that *version 5.1.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 useful improvements: * Added two new conversions:*YAML to XML* and *XML to YAML*. * *Word to HTML/DITA * - The processing of table captions was improved. The table is now obtained with a caption child in HTML or with a title in DITA. - The width of table columns is now preserved. - The processing of figure captions was also improved. For XHTML, a <figure> element is obtained with a <figcaption> child element. For DITA, a <fig> element is obtained with a <title> child element. - The saving of images was enhanced and the name from the Word internal structure is now preserved. - Fixed an issue where the content was incorrectly merged between two different unordered lists. * Increased the minimum required version of Oxygen to 23.1. 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 Also, we want to let you know that a new article was published on the Oxygen XML Blog that explains how you can migrate from MS Word to DITA using the Oxygen Batch Documents Converter add-on: https://blog.oxygenxml.com/topics/migrating_word_to_dita_bdc/migrating_word… We hope you will find this add-on useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Webinar: OpenAPI Support in Oxygen (December 14, 2022)
by Alin Belu 08 Dec '22

08 Dec '22

Hello, On the *14th of December*, clear your schedule for the last Oxygen XML Editor live event of the year - the *OpenAPI Support in Oxygen webinar*. There is no way you want to miss this! OpenAPI is a community-driven open specification that defines a language-agnostic interface used to describe, produce, consume, and visualize RESTful APIs and web services. OpenAPI documents describe the API (or its elements) and are represented in either YAML or JSON formats. During this live webinar, Octavian Nadolu (project manager at Syncro Soft) will be showcasing the support offered in Oxygen for OpenAPI documents, as well as demonstrating how to create, edit, test, and generate documentation for OpenAPI documents. By joining this live event, you will get the chance to learn the following: * Creating OpenAPI documents * Editing and validating OpenAPI documents * How to easily edit OpenAPI documentation in Author mode * Generating documentation for OpenAPI components in HTML format * Testing an OpenAPI, execute API requests, and validate responses * Creating and running test scenarios This is a free event but registration is required. You can register at https://oxygenxml.com/evs2022-11.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

MathFlow losing support
by Michael Boudreau 30 Nov '22

30 Nov '22

I recently learned that Wiris, the company that took over MathFlow<https://docs.wiris.com/en/mathflow/start> from DesignScience, will be ceasing support for it sometime in the near future. Does Oxygen have plans for a replacement graphical editor for MathML in XML documents? -- Michael R. Boudreau Electronic Publishing Technology Manager The University of Chicago Press 1427 E. 60th Street Chicago, IL 60637 www.journals.uchicago.edu

3 2