[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Automatic link type detection
Hello, I am trying to design a generic linking mechanism for use in the Borges project (http://borges-dms.sourceforge.net/) in which master documents call various modules (sections) to form the final document. Let's imagine a common scenario: you are writing documentation for a product, which includes 3 manuals: a little installation booklet (booklet.xml), a user guide (user.xml), and a reference manual (reference.xml). All 3 documents begin with the same introduction section (intro.xml) that contains a reference to the customization section (custom.xml) which is included in both user.xml and reference.xml documents. How do you write the link to custom.xml in intro.xml so that it is interpreted correctly in all 3 documents? - If you use xref, it will fail in user.xml - If you use olink (pointing to reference.xml), the reference in user.xml will point to the customization section of the reference manual, while it is actually available in user.xml To solve this, the olink template should be able to detect when a target is actually available from within the same document. If so, an internal reference should be made instead of the external one. This behavior could be controlled through a detect.internal.olink parameter for example. Did someone already faced that problem? How did you solve it? I'd like to hear your input before starting to try tweaking the xref.xsl stylesheet. -- Camille Bégnis NeoDoc Co-Founder http://neodoc.biz
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]