<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="insert.olink.page.number"> <refmeta> <refentrytitle>insert.olink.page.number</refentrytitle> <refmiscinfo class="other" otherclass="datatype">list</refmiscinfo> <refmiscinfo class="other" otherclass="value">no</refmiscinfo> <refmiscinfo class="other" otherclass="value">yes</refmiscinfo> <refmiscinfo class="other" otherclass="value">maybe</refmiscinfo> </refmeta> <refnamediv> <refname>insert.olink.page.number</refname> <refpurpose>Turns page numbers in olinks on and off</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="insert.olink.page.number.frag"> <xsl:param name="insert.olink.page.number">no</xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>The value of this parameter determines if cross references made between documents with <tag>olink</tag> will include page number citations. In most cases this is only applicable to references in printed output. </para> <para>The parameter has three possible values. </para> <variablelist> <varlistentry> <term>no</term> <listitem><para>No page number references will be generated for olinks. </para></listitem> </varlistentry> <varlistentry> <term>yes</term> <listitem><para>Page number references will be generated for all <tag>olink</tag> references. The style of page reference may be changed if an <tag class="attribute">xrefstyle</tag> attribute is used. </para></listitem> </varlistentry> <varlistentry> <term>maybe</term> <listitem><para>Page number references will not be generated for an <tag>olink</tag> element unless it has an <tag class="attribute">xrefstyle</tag> attribute whose value specifies a page reference. </para></listitem> </varlistentry> </variablelist> <para>Olinks that point to targets within the same document are treated as <tag>xref</tag>s, and controlled by the <parameter>insert.xref.page.number</parameter> parameter. </para> <para>Page number references for olinks to external documents can only be inserted if the information exists in the olink database. This means each olink target element (<tag>div</tag> or <tag>obj</tag>) must have a <tag class="attribute">page</tag> attribute whose value is its page number in the target document. The XSL stylesheets are not able to extract that information during processing because pages have not yet been created in XSLT transformation. Only the XSL-FO processor knows what page each element is placed on. Therefore some postprocessing must take place to populate page numbers in the olink database. </para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 26953 | Paul Allen | Move //guest/perforce_software/p4convert to //guest/perforce_software/p4convert/main | ||
//guest/perforce_software/p4convert/docs/docbook-xsl-ns-1.78.1/params/insert.olink.page.number.xml | |||||
#2 | 14806 | Paul Allen | Update docs and add +w. | ||
#1 | 13920 | Paul Allen | copy part 2 (no errors) | ||
//guest/paul_allen/p4convert-maven/docs/docbook-xsl-ns-1.78.1/params/insert.olink.page.number.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/insert.olink.page.number.xml | |||||
#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. |