use.local.olink.style.xml 1.7 KB

12345678910111213141516171819202122232425262728
  1. <refentry xmlns="http://docbook.org/ns/docbook"
  2. xmlns:xlink="http://www.w3.org/1999/xlink"
  3. xmlns:xi="http://www.w3.org/2001/XInclude"
  4. xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"
  5. xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  6. version="5.0" xml:id="use.local.olink.style">
  7. <refmeta>
  8. <refentrytitle>use.local.olink.style</refentrytitle>
  9. <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
  10. </refmeta>
  11. <refnamediv>
  12. <refname>use.local.olink.style</refname>
  13. <refpurpose>Process olinks using xref style of current
  14. document</refpurpose>
  15. </refnamediv>
  16. <refsynopsisdiv> <src:fragment xml:id="use.local.olink.style.frag">
  17. <xsl:param name="use.local.olink.style" select="0"/> </src:fragment>
  18. </refsynopsisdiv>
  19. <refsection><info><title>Description</title></info>
  20. <para>When cross reference data is collected for use by olinks, the data for each potential target includes one field containing a completely assembled cross reference string, as if it were an xref generated in that document. Other fields record the separate title, number, and element name of each target. When an olink is formed to a target from another document, the olink resolves to that preassembled string by default. If the <parameter>use.local.olink.style</parameter> parameter is set to non-zero, then instead the cross
  21. reference string is formed again from the target title, number, and
  22. element name, using the stylesheet processing the targeting document.
  23. Then olinks will match the xref style in the targeting document
  24. rather than in the target document. If both documents are processed
  25. with the same stylesheet, then the results will be the same.</para>
  26. </refsection>
  27. </refentry>