The test DITA map below should pose no problem to XMLmind DITA Converter (ditac), provided that you make the following modifications to it:

1) Add a <!DOCTYPE> (or xsi:noNamespaceSchemaLocation for a W3C XML Schema or <?xml-model?> for a RELAX NG schema) at the top of your map.

This is mandatory as without a schema, ditac has no access no attribute default values.

I added:
---
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
---

The system ID ("map.dtd") is not important as ditac uses its own XML catalogs.

2) Fix typo. Replace:

---
href="topic-a.dita" keys="topic-b"
---

by:

---
href="topic-a.dita" keys="topic-a"
---

After doing this, the files generated by ditac looked just fine.

Please do not hesitate to send us privately a *real* document in case you have problems with our tool. Simply zip all maps, topics and graphic files and send the .zip archive to [email protected].




On 07/20/2016 07:30 PM, David Goss wrote:

I'm attempting to build a manual that was previously being
build using the DITA-OT 1.7. I'm evaluating using the ditac
for our webhelp. I'm having a little trouble with reltables.

We are using reltables via keys and keyrefs, so that if an
href for a topic changes, it doesn't break a related link
too. Below is an example:

     <map id="test">
         <title>Test Map</title>

         <topicref href="topic-a.dita" keys="topic-b"/>
         <topicref href="topic-b.dita" keys="topic-b"/>

         <reltable>
             <relrow>
                 <relcell>
                     <topicref keyref="topic-a"/>
                 </relcell>
                 <relcell>
                     <topicref keyref="topic-b"/>
                 </relcell>
             </relrow>
         </reltable>
     </map>

This throws a bunch of errors about not being able to
resolve keyrefs and related links are not produced, and I
suspect the reason is one of the ditac limitations listed in
ditac manual:

The effective value of a <topicref> element having a
@keyref attribute is almost certainly not conforming as we
have not really understood the spec.

I have a few questions about this:

1. Can "almost certainly not conforming" be clarified?
    Specifically, what does the ditac actually do when it
    encounters @keyref in a topicref? Does it simply ignore
    it and throw an error? Does it try to do something else?
2. Given what looks like a limitation with the ditac
    regarding keyrefs, what is the recommended approach for
    reltables? Is there a better way other than using @href
    in both content and the reltable?

(I do want to say that despite this issue, my initial
reaction to the ditac is very positive. It processed one of
our maps in about 1 minutes that takes the DITA-OT about
10-15 minutes! The robust command line interface and options
are also very appreciated)


--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support

Reply via email to