You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Converted from internal issue: EXM-37912
Document a step by step procedure for adding support for an new XML vocabulary in Oxygen: validation, content completion, new file templates, custom CSS, custom Author actions, custom Schematron rules maybe.
Pasting an older answer I gave at some point:
Oxygen comes bundled with out of the box support for several XML vocabularies. If you look in the Oxygen Preferences->"Document Type Association" page you can see a list of them.
For all other XML vocabularies like Pubmed, support for editing can be added to Oxygen.
For example you can add new file templates:
https://www.oxygenxml.com/doc/versions/18.1/ug-editor/topics/create-your-own-templates.html
If you have access to the schemas used for the Pubmed vocabulary, you can configure Oxygen to use those schemas for validating the Pubmed XML documents.
You can download the schemas locally and if there is a "catalog.xml" catalog file included, you can go to the Oxygen Preferences->"XML / XML Catalog" page and add there a reference to the XML catalog.
Oxygen will also use the schemas information to propose content completion entries when editing the XML documents.
The text was updated successfully, but these errors were encountered:
Somebody who was not able to create a framework because there does not seem to be anything in the user's manual about association rules:
I am trying to build a custom framework with the "Framework Customization Tutorial". I did steps 1 to 6 but at step 7, i get stucked. I don't know understand how to test the framework customization. There is a missing link I think I do not get. I tried to do a new document, but I don't see how to start my new type of document. It does not appear in the Framework templates.
Converted from internal issue: EXM-37912
Document a step by step procedure for adding support for an new XML vocabulary in Oxygen: validation, content completion, new file templates, custom CSS, custom Author actions, custom Schematron rules maybe.
Pasting an older answer I gave at some point:
The text was updated successfully, but these errors were encountered: