On 08/26/2019 04:08 PM, Rodolfo M. Raya wrote:
Yes, the problem is related to embedding ditac in Conversa.
If the main file to convert is written in Markdown for LwDITA, ditac uses a
the fallback mechanism when invoking Saxon and fails to locate
"xsl/hdita/hdita.xsl".
Yes. The code is:
---
URL url = Resolve.resolveURI("ditac-xsl:hdita/hdita.xsl",
/*base*/ null);
---
in
<ditac_install_dir>/src/com/xmlmind/ditac/load/hdita/HDITALoaderFactory.java
Notice the "ditac-xsl:" prefix.
All my tools store the XML catalog in a folder named "catalog". In Conversa
I used to have the catalog in a folder named "catalog" too and made it work
by setting the " xml.catalog.file" property. This still works well for
regular DITA but currently fails for LwDITA and Markdown. Renaming the
catalog folder to "schema" solved the issue in Conversa 1.3.1.
I thought about setting my own catalog resolver, but ResolverFactory uses a
concrete class from Apache resolver instead of using a regular Java
interface like org.xml.sax.EntityResolver. I need to check if my own
resolver would work.
The problem is not urgent, Conversa works.
It seems that ditac really needs the following XML catalog entry to be
found in any of your XML catalogs:
<rewriteURI uriStartString="ditac-xsl:"
rewritePrefix="LOCATION_OF_DITAC_XSL_DIR" />
All XMLmind tools embedding ditac add this entry to their own XML catalogs.
We'll update our documentation
Part III. Embedding XMLmind DITA Converter in a Java™ application
https://www.xmlmind.com/ditac/_distrib/doc/manual/manual-7.html#I_f2h3lb_
to explain and document this requirement.
--
XMLmind DITA Converter Support List
[email protected]
https://www.xmlmind.com/mailman/listinfo/ditac-support
