Transformation fails to find DTD file for DITA XML
Posted: Fri Dec 19, 2014 10:35 pm
Hi!
I am trying to run DITA transformation scenarios on DITA XML files.
The XML files are based on customized versions of topic/concept/task/reference, not on the standard DITA-OT's.
To make Oxygen aware of these customizations, I created an XML catalog, and added the catalog entry in $OXYGEN/frameworks/dita/catalog.xml. Then I made the DOCTYPE declarations match the PUBLIC IDs I have set in the catalog. For SYSTEM ID, I just entered the DTD filename.
Now, this puzzles me: Validation succeeds, but Transformation fails to find the appropriate DTDs.
[DOTJ012F][FATAL] Failed to parse the input file './my.ditamap'. The XML parser reported the following error: ./my-custom.dtd (The system cannot find the file specified)
It seems as if Oxygen is following the PUBLIC ID through the XML catalog to find the DTD whereabouts during validation, but not during trasnformation. So it tries to find the DTD in the same path where the XML file is stored, instead of looking in the path defined in the XML catalog.
Thanks for your support,
Pablo
I am trying to run DITA transformation scenarios on DITA XML files.
The XML files are based on customized versions of topic/concept/task/reference, not on the standard DITA-OT's.
To make Oxygen aware of these customizations, I created an XML catalog, and added the catalog entry in $OXYGEN/frameworks/dita/catalog.xml. Then I made the DOCTYPE declarations match the PUBLIC IDs I have set in the catalog. For SYSTEM ID, I just entered the DTD filename.
Now, this puzzles me: Validation succeeds, but Transformation fails to find the appropriate DTDs.
[DOTJ012F][FATAL] Failed to parse the input file './my.ditamap'. The XML parser reported the following error: ./my-custom.dtd (The system cannot find the file specified)
It seems as if Oxygen is following the PUBLIC ID through the XML catalog to find the DTD whereabouts during validation, but not during trasnformation. So it tries to find the DTD in the same path where the XML file is stored, instead of looking in the path defined in the XML catalog.
Thanks for your support,
Pablo