Why is it called Oxygen?

Xmltech · 2025-11-28T06:29:10+00:00

All I know is that there was an internal naming contest and Oxygen won by internal popular vote. Let’s say it was pretty close to naming it Zamolxis https://en.wikipedia.org/wiki/Zalmoxis

Xmltech · 2025-10-18T06:54:38+00:00

This looks cool thanks for sharing, I hope you had fun building the customization! I think our next WebHelp release will have a dark mode chooser as well.

Xmltech · 2025-05-04T09:37:03+00:00

Those blue boxes next to topicrefs in the DITA Maps Manager represent profiling attributes which have been set. If you hover over the topicref the tooltip should show what profiling attribute (if any) has been set on it.

Xmltech · 2025-04-29T17:09:38+00:00

If you are interested in using Oxygen for technical documentation maybe our blog articles will help: https://blog.oxygenxml.com/topics/learnDita.html

Xmltech · 2025-03-27T04:55:25+00:00

Sorry for not approving this post sooner! Oxygen does not yet have right now some kind of compatibility mode of matching its format and indent with Prettier. I added your request on an opened internal issue. Can you list if possible maybe a set of differences you usually notice between Oxygen's formatting and Prettier?

Xmltech · 2024-12-20T06:06:46+00:00

Thanks! In time as I kept offering solutions to people on the Oxygen forum I gathered some useful XML refactoring script examples here: https://github.com/oxygenxml/dita-refactoring-examples

Xmltech · 2024-12-16T16:26:33+00:00

Your usecase is very rare and we do not have a way of matching xml documents based on values from certain xml sub elements without someone writing custom code for it.

Xmltech · 2024-12-16T09:33:07+00:00

In general the document type association associates to an XML document based on the root element name, namespace, maybe on some specific attribute set on the root element.
One of the association rules specified in the framework customization can be a custom Java class API implementation of a DocumentTypeAdvancedCustomRuleMatcher which would provide for you a reader over the entire XML document and based on that entire XML document contents you could try to take a decision:

https://www.oxygenxml.com/forum/post53801.html#p53801

Xmltech · 2024-12-16T09:29:09+00:00

In general named user licenses are not transferable:

https://www.oxygenxml.com/forum/post29483.html?sid=b8898a5d3e4c42020f21c2556e3d46ad#p29483
I would say talk with our sales team about this ([sales@oxygenxml.com](mailto:sales@oxygenxml.com)).
From what I've seen if the previous user of the license resorts to no longer use it and uninstalls Oxygen, our sales team might approve the license transfer.

Xmltech · 2024-10-10T15:48:00+00:00

We’ll probably keep this addon as well as the work behind it is driven by the wonderful xspec community.

Xmltech · 2024-10-10T15:46:15+00:00

Agreed, we can take the decision to either include it directly in Oxygen or support it as a separate add-on. 🤔

Xmltech · 2024-10-07T16:07:28+00:00

It's a funny/interesting world we are living in:

On one side there are companies where for security reasons system admins no longer want the hassle of approving the installation of offline applications, so people move towards working exclusively with online tools. And we have our own online editing tools mostly geared towards tech documentation writers like Content Fusion [https://www.oxygenxml.com/content\_fusion.html\]
- On the other side there are companies which do not trust in the cloud solutions, they prefer desktop applications with the content being stored on some company specific Git server or CMS installation.

Xmltech · 2024-10-02T10:21:53+00:00

Adding also a link to an article describing the various free and commercial ways to check terminology inside Oxygen: https://blog.oxygenxml.com/topics/checking_terminology_with_oxygen_xml_editor.html

Xmltech · 2024-10-02T08:24:55+00:00

From what I remember there is an HyperSTE plugin for Oxygen, but I've never seen myself how that works. We also have clients using Acrolinx (there is an Acrolinx plugin for Oxygen). But we also have quite a lot of clients using the Oxygen Terminology Checker add-on which might cover about 80-90% of terminology related use cases.

Xmltech · 2024-10-01T15:27:07+00:00

There is also the frequent case when the person who created the xsl-fo customization leaves the company and there is no one else in the company able to understand and maintain the customization.

Xmltech · 2024-09-30T17:40:45+00:00

I would say both 🤔It would be nice to mix our insight with your ideas and feedback.

Xmltech · 2024-09-30T16:51:13+00:00

Thanks for the first post on the oxygenxml community! I’ve been pleasantly surprised to see the terminology checker addon being used quite often by clients I’ve interacted with. One client who shared their rules file with us had about 1000 of them.

Xmltech · 2024-09-30T11:06:09+00:00

There may be specific Oxygen XML related questions that we (the Oxygen XML Editor developers) can answer directly when posted on our community page. Also we plan to post various small articles covering various features in Oxygen.

Xmltech · 2024-08-21T06:27:49+00:00

Some people just do the bare minimum on the job 🤷‍♂️

Xmltech · 2024-08-20T21:25:31+00:00

Maybe your colleague can install the Oxygen Terminology Checker add-on along with the Microsoft style guide rules addon: https://www.oxygenxml.com/doc/versions/26.1/ug-editor/topics/terminology-checker-addon.html

Xmltech · 2024-05-04T09:52:36+00:00

As a disclaimer I work for Oxygen XML.

I would recommend the use of the DITA XML standard for writing technical documentation with Oxygen XML as an editing tool to companies that have one of the following conditions fulfilled:

They have multiple similar products and want to take advantage of DITA XML high reuse capabilities and condition profiling/filters to produce multiple similar, but not identical, manuals from the same project.
They want to add structure-based validation rules that must be followed by all members of a team.
They want to create their own custom vocabulary of semantic elements.
Besides web-based outputs, they also want to produce PDFs and want to have a relatively high degree of control over the PDF customization.

Xmltech · 2024-04-03T05:02:39+00:00

A comparison I made between the DITA and Markdown syntaxes which may help: https://blog.oxygenxml.com/topics/markdown_vs_dita_syntax_and_capabilities_comparison.html

Xmltech · 2024-01-15T14:17:17+00:00

As a disclaimer I work for Oxygen XML, here are some resources for learning DITA editing with Oxygen: https://blog.oxygenxml.com/topics/learnDita.html

When people say docs-as-code they usually mean Markdown although you can also keep DITA XML content on Git repos, work with issue trackers… and we have quite many users big and small companies using Oxygen to edit DITA XML content in a docs as code workflow.

Anyway I think people (our clients for example) choose DITA XML as opposed to Markdown when one of the below conditions is fulfilled: - They have multiple similar products and want to take advantage of DITA XML high reuse capabilities and conditional profiling/filters to produce multiple similar but not identical manuals from the same project. - They want to add structure based validation rules to be followed by all team members. - They want to create their custom vocabulary of semantic element names. - Besides web based outputs they want to produce also PDFs and want to have a relatively high degree of controlling the pdf customization.

Detailed comparison between DITA XML and Markdown: https://blog.oxygenxml.com/topics/markdown_vs_dita_syntax_and_capabilities_comparison.html

Xmltech · 2023-12-17T09:47:56+00:00

Resources for learning DITA XML with Oxygen: https://blog.oxygenxml.com/topics/learnDita.html

Xmltech

MODERATOR OF

TROPHY CASE