Question about adding tagging constraints to Oxygen
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 2
- Joined: Wed Feb 15, 2017 9:07 pm
Question about adding tagging constraints to Oxygen
I am working on adding tagging constraints to Oxygen for my team. We use Oxygen for authoring DITA content, and would like to customize Oxygen so certain tags do not appear as available for our authors. My team works on the Mac operating system.
For example, when a writer is authoring in a <p> tag, we'd prefer that the writers not have the tag <wintitle> appear as an available tag. Our goal in this case would be that when writers have their cursor within the <p> tag and click enter, the <wintitle> tag either does not appear as an available tag, or it is greyed out so they cannot use it.
I found the following documentation article, which appears to provide an example of the constraint we'd like to achieve: https://www.oxygenxml.com/dita/1.3/spec ... omain.html
In this example, the information architect creates a .mod file and also updates a catalog.xml file to include the new constraints file. I have two questions about this process:
1. Where in the Oxygen application folder would the information architect place the .mod file?
2. Where is the catalog.xml file that the architect would update located?
Also, if there is a setting in the Oxygen GUI that could achieve this for my team, which I am overlooking, please let me know.
Thank you for your help,
Kristy
For example, when a writer is authoring in a <p> tag, we'd prefer that the writers not have the tag <wintitle> appear as an available tag. Our goal in this case would be that when writers have their cursor within the <p> tag and click enter, the <wintitle> tag either does not appear as an available tag, or it is greyed out so they cannot use it.
I found the following documentation article, which appears to provide an example of the constraint we'd like to achieve: https://www.oxygenxml.com/dita/1.3/spec ... omain.html
In this example, the information architect creates a .mod file and also updates a catalog.xml file to include the new constraints file. I have two questions about this process:
1. Where in the Oxygen application folder would the information architect place the .mod file?
2. Where is the catalog.xml file that the architect would update located?
Also, if there is a setting in the Oxygen GUI that could achieve this for my team, which I am overlooking, please let me know.
Thank you for your help,
Kristy
-
- Posts: 9446
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Question about adding tagging constraints to Oxygen
Hi Kristy,
Basically you have 3 options:
1) A DITA DTD specialization plugin which restricts the use of wintitle. This would mean that all your DITA topics would have a special DOCTYPE public ID which would map to the specialization DTDs. This takes some implementation effort, you already found the post where I'm referring to Eliot Kimber's specialization tutorial which needs to be followed step by step.
and 2 options by using Oxygen features:
2) A special XML configuration file located in the DITA framework. This is a new feature we added in Oxygen 18.1.
https://www.oxygenxml.com/doc/versions/ ... ually.html
which among lots of other things can be used to reject various elements and attributes from being proposed.
3) If in the Oxygen Preferences->"Document Type Association" page you extend (or directly edit) the DITA document type association, in the Author->Content completion you have a Filter list in which you can add elements which should not be presented to the end user when editing.
http://www.oxygenxml.com/doc/versions/1 ... etion.html
Regards,
Radu
Basically you have 3 options:
1) A DITA DTD specialization plugin which restricts the use of wintitle. This would mean that all your DITA topics would have a special DOCTYPE public ID which would map to the specialization DTDs. This takes some implementation effort, you already found the post where I'm referring to Eliot Kimber's specialization tutorial which needs to be followed step by step.
and 2 options by using Oxygen features:
2) A special XML configuration file located in the DITA framework. This is a new feature we added in Oxygen 18.1.
https://www.oxygenxml.com/doc/versions/ ... ually.html
which among lots of other things can be used to reject various elements and attributes from being proposed.
3) If in the Oxygen Preferences->"Document Type Association" page you extend (or directly edit) the DITA document type association, in the Author->Content completion you have a Filter list in which you can add elements which should not be presented to the end user when editing.
http://www.oxygenxml.com/doc/versions/1 ... etion.html
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service