On 06/22/2011 03:47 PM, Darren Carlton wrote: > We've been using relationship tables to define links between task > topics, but the ditac limitations documentation says this isn't > supported. How do other people define links between topics of the same type?
No, using relationship tables to define links between topics is quite well supported. (In fact, it's the only raison d'être of <reltable>s.) See below. > > For example, we have something like this: > > <reltable> > <relheader> > <relcolspec type="task"/> > <relcolspec type="reference"/> > <relcolspec type="concept"/> > </relheader> > <relrow> > <relcell collection-type="family"> > <topicref href="topic1.dita"/> > <topicref href="topic2.dita"/> > <topicref href="topic3.dita" linking="targetonly"/> > </relcell> > <relcell/> > <relcell/> > </relrow> > > But http://www.xmlmind.com/ditac/_distrib/doc/manual/limitations.html says > this isn't supported: > "Attribute collection-type, whatever its value, is ignored inside > the reltable element." > The collection-type attribute is indeed ignored in <reltables>. The reason for this limitation is: [1] The laziness of yours truly. [2] While we managed to understand --more or less-- the meaning of this attribute for a hierarchy of <topicref>s, we failed to do so in the context of a <reltable>. This does not mean that you cannot use relationship tables to define links between topics. In the above example, please specify each <topicref> in a different <relcell> and you'll see that links between topic1.dita, topic2.dita and topic3.dita will be automatically generated by ditac. Note that the linking="targetonly" attribute set on topic3.dita will be honored. --- PS: The type attribute of <relcolspec> is ignored too. To our knowledge, this just means that we do not generate text such as "Related tasks", "Related reference", "Related concepts". We always generate: "Related information". -- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
