From 15c7d39533a1eb1da0748011f3378fd0f02ed14d Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Tue, 8 Oct 2013 20:03:29 +0000 Subject: Update stylesheets to docbook-xsl-1.78.1. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10355 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- .../params/prefer.internal.olink.xml | 78 ++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/prefer.internal.olink.xml (limited to 'stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/prefer.internal.olink.xml') diff --git a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/prefer.internal.olink.xml b/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/prefer.internal.olink.xml new file mode 100644 index 000000000..2599d76c1 --- /dev/null +++ b/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/prefer.internal.olink.xml @@ -0,0 +1,78 @@ + + +prefer.internal.olink +boolean + + +prefer.internal.olink +Prefer a local olink reference to an external reference + + + + + + + + +Description + +If you are re-using XML content modules in multiple documents, +you may want to redirect some of your olinks. This parameter +permits you to redirect an olink to the current document. + + +For example: 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. + + + +If you set the prefer.internal.olink +parameter to a non-zero value, then the processor will +first look in the olink database +for the olink's targetptr attribute value +in document matching the current.docid +parameter value. If it isn't found there, then +it tries the document in the database +with the targetdoc +value that matches the olink's targetdoc +attribute. + + +This feature permits an olink reference to resolve to +the current document if there is an element +with an id matching the olink's targetptr +value. The current document's olink data must be +included in the target database for this to work. + + +There is a potential for incorrect links if +the same id attribute value is used for different +content in different documents. +Some of your olinks may be redirected to the current document +when they shouldn't be. It is not possible to control +individual olink instances. + + + + -- cgit v1.2.3-54-g00ecf