java.io.FileNotFoundException: topic.dtd

[stefan-jung]

The <xsl:output> is not correctly assembled in the qadata.xsl.

<!-- for 1.x OT versions, use doctype-system="../dtd/technicalContent/dtd/topic.dtd" -->
<xsl:output
  method="xml"
  indent="yes"
  doctype-public="-//OASIS//DTD DITA Topic//EN"
  doctype-system="../plugins/org.oasis-open.dita.v1_2/dtd/technicalContent/dtd/topic.dtd"/>

This I/O error is reported:

I/O error reported by XML parser processing 
file:/C:/Users/eike/DITA-QA/QA-Test%20001/out/qa/QATest001.dita: 
C:\Users\eike\DITA-QA\QA-Test 001\out\plugins\org.oasis-open.dita.v1_2\dtd\technicalContent\dtd\topic.dtd 
(Das System kann den angegebenen Pfad nicht finden) 
Cause: java.io.FileNotFoundException: 
C:\Users\eike\DITA-QA\QA-Test 001\out\plugins\org.oasis-open.dita.v1_2\dtd\technicalContent\dtd\topic.dtd 
(Das System kann den angegebenen Pfad nicht finden)

Das System kann den angegebenen Pfad nicht finden means: path not found

The script tries to assemble the path relative to the DITA source directory, but should use the DITA directory instead.

[bcolborn]

Can you try the change in my most recent commit? If that resolves your issue I'll pull it over.

[stefan-jung]

I had the same idea yesterday, but it did not work. :)

[bcolborn]

Yes, I just found that it won't, though it seemed to earlier. I'm especially confused since the maps and topics in the OT 2.0 sample directory have relative paths to the DTDs that are incorrect. It feels like catalog-dita.xml isn't being properly referenced in one phase of the transformation.

[lief-erickson]

I ran into this issue as well with the 'master' branch and DITA-OT 2.4.3. My workaround was to change the doctype-system path in qadata.xsl to a known location of topic.dtd.