Recurring missing DTD after being targeted in the Document Type association

[gbv34]

Hello!
I have a project where the client declared a DTD with an absolute path.

Code: Select all

<!DOCTYPE concept PUBLIC "urn:pubid:xxx.com:doctypes:dita:concept" "file:///C:/xxxxx/xxxxxx/xxxxx/xxxxx/DocTypes/dita-oasis/1.2/com.xxx.doctypes/dtd/concept/dtd/xxx-concept.dtd"[]>

I can't modify the content so I have to figure out how to achieve a publication on my side with the DITA-OT provided.
Here are the steps I followed:
1. I created a DITA-OT with the custom dtd provided by the client.
2. I applied the Integrator scenario to it and it successfully build the DITA-OT.
3. I target the Document Type association in Oxygen with the relevant folder to the DTDs into the DITA-OT folder.

Thanks to these operations, I can open and visualize the content of the maps and topics. However, I feel confused because when I start a transformation, I only have access to the scenarios that I previously created and not the default ones.

image.png

When publishing via one these scenarios, the log outputs an error related to the DTD being not found although I can open and access the files in the editor.
What can I do in order to successfully build the project. I suspect the urn and path to the DTD should be adapted, but how?

[Radu]

Hi,

So you created a DITA OT DTD specialization plugin and integrated it in the DITA OT bundled with Oxygen, right?
If you can share the plugin and a sample document with me (support@oxygenxml.com) I could try to try it on my side, because I do not know exactly what it contains, what mappings you defined in its catalog.xml XML catalog file.

Regards,
Radu

[gbv34]

Hello, Radu!
I'll do it right now. Thank you

[Radu]

Thanks for the samples.

We'll discuss more via email, adding here a few general remarks based on the samples if someone else stumbles on this thread:

1) In the Oxygen Preferences->DITA page you need to refer to the entire "DITA OT" folder, not to the plugin folder.
2) Any DITA OT specialization plugin folder needs to contain inside it a "plugin.xml" defining the plugin ID and referencing the catalog.xml. Something like:

Code: Select all

<plugin id="com.my.specialization">
  <feature extension="dita.specialization.catalog.relative" file="catalog.xml"/>
</plugin>

3) After running validation, if the XML topic instance is opened in Oxygen and validated, Oxygen should show errors in the DTDs if the DTDs still have validation problems and the errors need to be fixed.

Regards,
Radu