Hi Mark,
What Oxygen version do your clients have?
Please see some answers below:
I put DITA template files in <Oxygen install dir>/frameworks/dita/templates/<company>.
Then I went to Options > Preferences > Editor > Templates > Document Templates and added the template dir above.
Any of these approaches you tried should have the same final consequence of having your templates appear in the "File->New" wizard.
If you do both the approaches in the File->New wizard you will probably have duplicate file templates available for your specialization.
Removing the standard DITA templates would be good, what's a good way to do that?
You could try to remove them from:
<Oxygen install dir>/frameworks/dita/templates/
Or in the Preferences->"Document Type Association" page you could extend (
Extend button) the "DITA" framework and make changes to the list of new file templates folders it defines. Then disable the original "DITA" document type association so that only the extension is enabled and provides new file templates.
Removing the standard DITA doctypes would be even better. Would I needed to edit the catalog file under <oxygen>\frameworks\dita\DITA-OT?
By default Oxygen uses the XML catalog located in:
<oxygen>\frameworks\dita\DITA-OT\catalog-dita.xml
to resolve DTD Public IDs to DTD resources.
That main DITA OT catalog has mappings in it like:
Code: Select all
<public publicId="-//OASIS//DTD DITA Topic//EN" uri="topic.dtd" xml:base="dtd/technicalContent/dtd/"></public>
and at the end it has references to particular plugin contributed catalogs (among which is your own specialization plugin).
So potentially even if your plugin's catalog.xml adds mappings for the default DITA Public IDs to not existing resources and you integrate your plugin in the DITA OT, the mappings which exists higher up in the catalog-dita.xml will have more priority. So you cannot elegantly override the XML catalog mappings for the base DTDs from your integrated specialization plugin.
Regards,
Radu