<refentry xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:src="http://nwalsh.com/xmlns/litprog/fragment" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="5.0" xml:id="activate.external.olinks"> <refmeta> <refentrytitle>activate.external.olinks</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>activate.external.olinks</refname> <refpurpose>Make external olinks into active links</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="activate.external.olinks.frag"> <xsl:param name="activate.external.olinks" select="1"/> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If <parameter>activate.external.olinks</parameter> is nonzero (the default), then any olinks that reference another document become active links that can be clicked on to follow the link. If the parameter is set to zero, then external olinks will have the appropriate link text generated, but the link is not made active. Olinks to destinations in the current document remain active.</para> <para>To make an external olink active for HTML outputs, the link text is wrapped in an <tag>a</tag> element with an <tag>href</tag> attribute. To make an external olink active for FO outputs, the link text is wrapped in an <tag>fo:basic-link</tag> element with an <tag>external-destination</tag> attribute.</para> <para>This parameter is useful when you need external olinks to resolve but not be clickable. For example, if documents in a collection are available independently of each other, then having active links between them could lead to unresolved links when a given target document is missing.</para> <para>The epub stylesheets set this parameter to zero by default because there is no standard linking mechanism between Epub documents.</para> <para>If external links are made inactive, you should consider setting the stylesheet parameter <parameter>olink.doctitle</parameter> to <literal>yes</literal>. That will append the external document's title to the link text, making it easier for the user to locate the other document.</para> <para>An olink is considered external when the <parameter>current.docid</parameter> stylesheet parameter is set to some value, and the olink's <tag>targetdoc</tag> attribute has a different value. If the two values match, then the link is considered internal. If the <parameter>current.docid</parameter> parameter is blank, or the <tag>olink</tag> element does not have a <tag>targetdoc</tag> attribute, then the link is considered to be internal and will become an active link.</para> <para>See also <parameter>olink.doctitle</parameter>, <parameter>prefer.internal.olink</parameter>.</para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 12728 | eedwards |
Upgrade ANT doc build infrastructure to assemble PDFs: - remove non-namespaced DocBook source and add namespaced DocBook source. - add Apache FOP 1.1 - copy fonts, images, XSL into _build, establishing new asset structure. The original structure remains until all guides using it can be upgraded, and several other issues can be resolved. - updated build.xml to allow for per-target build properties. - upgraded the P4SAG to use the new infrastructure. - tweaked admonition presentation in PDFs to remove admonition graphics, and resemble closely the presentation used in the new HTML layout, including the same colors. With these changes, building PDFs involves using a shell, navigating into the guide's directory (just P4SAG for now), and executing "ant pdf". Issues still to be resolved: - PDF generation encounters several warnings about missing fonts (bold versions of Symbol and ZapfDingbats), and a couple of locations where the page content exceeds the defined content area. - Due to issues within Apache FOP, PDF generation emits a substantial amount of output that is not easily suppressed without losing important warning information. - Apache FOP's interface to ANT does not expose a way to set the font base directory. The current configuration does work under Mac OSX, but further testing on Windows will need to be done to determine if the relative paths defined continue to work. The workaround is for Windows users to customize the fop-config.xml to provide absolute system paths to the required fonts. - HTML generation needs further browser testing, and exhibits broken navigation on iOS browsers within the TOC sidebar. - A number of PDF and HTML presentation tweaks still need to be made, for example: sidebars, gui* DocBook tags, whitespace, section separation, etc. |