DITA RNG customization plugin not recognized by oXygen 17

[Frank Ralf]

Hi,

I've created a DITA RNG specialization as a DITA-OT plugin (http://www.oxygenxml.com/doc/versions/1 ... ation.html):

Code: Select all

<plugin id="com.company-name.dita.rng">

  <feature extension="dita.specialization.catalog.relative" file="catalog.xml"/>

</plugin>

I've successfully run the Ant integrator script, the entry gets added to the catalog-dita.xml file of the DITA-OT:

Code: Select all

<nextCatalog catalog="plugins/com.company-name.dita.rng/catalog.xml" />

However, the catalog reference doesn't seem to be picked up by oXygen 17.0 because test files won't validate. When I reference the main catalog file of the plugin directly in the document type (framework) validation works.

Because I've successfully done similar specializations before using oXygen 16 could this be related to oXygen 17? Any pointers welcome.

Kind regards,
Frank

[Radu]

Hi Frank,

Does the publishing work?
Could you check in the Oxygen 17 installation, the Preferences->DITA page?
That should be the place where the main DITA OT installation is referenced.
By default its catalog-dita.xml should be added by Oxygen to the used list of XML catalogs.
Could you also look inside the catalog-dita.xml to see that it contains a reference to your plugin's catalog?

Regards,
Radu

[Frank Ralf]

Many thanks for your quick reply, Radu! I think this might indeed be the culprit. I will check and report back.

Frank

[Frank Ralf]

Hi Radu,

That was indeed the reason. I use a separate DITA framework which is integrated into oXygen as an additional framework (Options > Preferences > Document Type Association > Location). With oXygen 16 that was enough to also point oXygen to that framework's DITA-OT. With oXygen 17 I have to set the path separately as you suggested.

However, using one of the framework related editor variables (${frameworkDir}/DITA-OT or ${framework}/DITA-OT) didn't work. I had to resort to an environment variable (which we use anyway): ${env(MY_DITA_XML_DIR)}\DITA-OT

Many thanks again for your help.

Frank

[Radu]

Hi Frank,

With oXygen 16 that was enough to also point oXygen to that framework's DITA-OT.

If you edit your custom DITA framework, in the Catalogs list it has a reference to the catalog-dita.xml

If the reference is like this:

${configured.ditaot.dir.url}/catalog-dita.xml

then it would use the setting in the DITA Preferences page to point to its catalog.
But if you change it to this:

${framework}/DITA-OT/catalog-dita.xml

then it will refer to its catalog without taking the preferences into account.

Regards,
Radu

[Frank Ralf]

Hi Radu,

Thanks for this explanation. After giving the issue some more thought I noticed that using the ${framework} variable on the DITA settings page cannot work because at any given time there might be more than one framework active.

I will use your solution and override the DITA setting in our customized framework.

Kind regards,
Frank

[Radu]

Hi Frank,

Exactly, the ${framework} editor variable can only be used when editing a document type configuration. So it cannot be used anywhere externally, for example in other preference pages.

Regards,
Radu