Question about adding tagging constraints to Oxygen
Posted: Wed Feb 15, 2017 9:24 pm
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