<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="man.font.links"> <refmeta> <refentrytitle>man.font.links</refentrytitle> <refmiscinfo class="other" otherclass="datatype">string</refmiscinfo> </refmeta> <refnamediv> <refname>man.font.links</refname> <refpurpose>Specifies font for links</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.font.links.frag"> <xsl:param name="man.font.links">B</xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>The <parameter>man.font.links</parameter> parameter specifies the font for output of links (<tag>ulink</tag> instances and any instances of any element with an <tag class="attribute">xlink:href</tag> attribute).</para> <para>The value of <parameter>man.font.links</parameter> must be either <literal>B</literal> or <literal>I</literal>, or empty. If the value is empty, no font formatting is applied to links.</para> <para>If you set <parameter>man.endnotes.are.numbered</parameter> and/or <parameter>man.endnotes.list.enabled</parameter> to zero (disabled), then you should probably also set an empty value for <parameter>man.font.links</parameter>. But if <parameter>man.endnotes.are.numbered</parameter> is non-zero (enabled), you should probably keep <parameter>man.font.links</parameter> set to <literal>B</literal> or <literal>I</literal><footnote><para>The main purpose of applying a font format to links in most output formats it to indicate that the formatted text is “clickable”; given that links rendered in man pages are not “real” hyperlinks that users can click on, it might seem like there is never a good reason to have font formatting for link contents in man output.</para> <para>In fact, if you suppress the display of inline link references (by setting <parameter>man.endnotes.are.numbered</parameter> to zero), there is no good reason to apply font formatting to links. However, if <parameter>man.endnotes.are.numbered</parameter> is non-zero, having font formatting for links (arguably) serves a purpose: It provides “context” information about exactly what part of the text is being “annotated” by the link. Depending on how you mark up your content, that context information may or may not have value.</para></footnote>.</para> </refsection> <refsection><info><title>Related Parameters</title></info> <para><parameter>man.endnotes.list.enabled</parameter>, <parameter>man.endnotes.are.numbered</parameter></para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/man.font.links.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. |