<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.pdf.frag"> <refmeta> <refentrytitle>insert.olink.pdf.frag</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>insert.olink.pdf.frag</refname> <refpurpose>Add fragment identifiers for links into PDF files</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="insert.olink.pdf.frag.frag"> <xsl:param name="insert.olink.pdf.frag" select="0"/> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>The value of this parameter determines whether the cross reference URIs to PDF documents made with <tag>olink</tag> will include fragment identifiers. </para> <para>When forming a URI to link to a PDF document, a fragment identifier (typically a '#' followed by an id value) appended to the PDF filename can be used by the PDF viewer to open the PDF file to a location within the document instead of the first page. However, not all PDF files have id values embedded in them, and not all PDF viewers can handle fragment identifiers. </para> <para>If <parameter>insert.olink.pdf.frag</parameter> is set to a non-zero value, then any olink targeting a PDF file will have the fragment identifier appended to the URI. The URI is formed by concatenating the value of the <parameter>olink.base.uri</parameter> parameter, the value of the <tag class="attribute">baseuri</tag> attribute from the <tag class="element">document</tag> element in the olink database with the matching <tag class="attribute">targetdoc</tag> value, and the value of the <tag class="attribute">href</tag> attribute for the targeted element in the olink database. The <tag class="attribute">href</tag> attribute contains the fragment identifier. </para> <para>If <parameter>insert.olink.pdf.frag</parameter> is set to zero (the default value), then the <tag class="attribute">href</tag> attribute from the olink database is not appended to PDF olinks, so the fragment identifier is left off. A PDF olink is any olink for which the <tag class="attribute">baseuri</tag> attribute from the matching <tag class="element">document</tag> element in the olink database ends with '.pdf'. Any other olinks will still have the fragment identifier added. </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.pdf.frag.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.pdf.frag.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/insert.olink.pdf.frag.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. |