<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.base.url.for.relative.links"> <refmeta> <refentrytitle>man.base.url.for.relative.links</refentrytitle> <refmiscinfo class="other" otherclass="datatype">string</refmiscinfo> </refmeta> <refnamediv> <refname>man.base.url.for.relative.links</refname> <refpurpose>Specifies a base URL for relative links</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.base.url.for.relative.links.frag"><xsl:param name="man.base.url.for.relative.links">[set $man.base.url.for.relative.links]/</xsl:param></src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>For any “notesource” listed in the auto-generated “NOTES” section of output man pages (which is generated when the value of the <parameter>man.endnotes.list.enabled</parameter> parameter is non-zero), if the notesource is a link source with a relative URI, the URI is displayed in output with the value of the <parameter>man.base.url.for.relative.links</parameter> parameter prepended to the value of the link URI.</para> <note> <para>A link source is an notesource that references an external resource: <itemizedlist> <listitem> <para>a <tag>ulink</tag> element with a <tag class="attribute">url</tag> attribute</para> </listitem> <listitem> <para>any element with an <tag class="attribute">xlink:href</tag> attribute</para> </listitem> <listitem> <para>an <tag>imagedata</tag>, <tag>audiodata</tag>, or <tag>videodata</tag> element</para> </listitem> </itemizedlist> </para> </note> <para>If you use relative URIs in link sources in your DocBook <tag>refentry</tag> source, and you leave <parameter>man.base.url.for.relative.links</parameter> unset, the relative links will appear “as is” in the “Notes” section of any man-page output generated from your source. That’s probably not what you want, because such relative links are only usable in the context of HTML output. So, to make the links meaningful and usable in the context of man-page output, set a value for <parameter>man.base.url.for.relative.links</parameter> that points to the online version of HTML output generated from your DocBook <tag>refentry</tag> source. For example: <programlisting ><xsl:param name="man.base.url.for.relative.links" >http://www.kernel.org/pub/software/scm/git/docs/</xsl:param></programlisting> </para> </refsection> <refsection><info><title>Related Parameters</title></info> <para><parameter>man.endnotes.list.enabled</parameter></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/man.base.url.for.relative.links.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/man.base.url.for.relative.links.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/man.base.url.for.relative.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. |