<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.endnotes.list.enabled"> <refmeta> <refentrytitle>man.endnotes.list.enabled</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>man.endnotes.list.enabled</refname> <refpurpose>Display endnotes list at end of man page?</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.endnotes.list.enabled.frag"> <xsl:param name="man.endnotes.list.enabled">1</xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If the value of <parameter>man.endnotes.list.enabled</parameter> is non-zero (the default), then an endnotes list is added to the end of the output man page.</para> <para>If the value of <parameter>man.endnotes.list.enabled</parameter> is zero, the list is suppressed — unless link numbering is enabled (that is, if <parameter>man.endnotes.are.numbered</parameter> is non-zero), in which case, that setting overrides the <parameter>man.endnotes.list.enabled</parameter> setting, and the endnotes list is still displayed. The reason is that inline numbering of notesources associated with endnotes only makes sense if a (numbered) list of endnotes is also generated.</para> <note> <para>Leaving <parameter>man.endnotes.list.enabled</parameter> at its default (non-zero) value ensures that no “out of line” information (such as the URLs for hyperlinks and images) gets lost in your man-page output. It just gets “rearranged”.</para> <para>So if you’re thinking about disabling endnotes listing by setting the value of <parameter>man.endnotes.list.enabled</parameter> to zero: Before you do so, first take some time to carefully consider the information needs and experiences of your users. The “out of line” information has value even if the presentation of it in text output is not as interactive as it may be in other output formats.</para> <para>As far as the specific case of URLs: Even though the URLs displayed in text output may not be “real” (clickable) hyperlinks, many X terminals have convenience features for recognizing URLs and can, for example, present users with an options to open a URL in a browser with the user clicks on the URL is a terminal window. And short of those, users with X terminals can always manually cut and paste the URLs into a web browser.</para> <para>Also, note that various “man to html” tools, such as the widely used <command><link xlink:href="http://users.actrix.gen.nz/michael/vhman2html.html">man2html</link></command> (<literal>VH-Man2html</literal>) application, automatically mark up URLs with <literal>a@href</literal> markup during conversion — resulting in “real” hyperlinks in HTML output from those tools.</para> </note> <para>To “turn off” numbering of endnotes in the endnotes list, set <parameter>man.endnotes.are.numbered</parameter> to zero. The endnotes list will still be displayed; it will just be displayed without the numbers<footnote><para>It can still make sense to have the list of endnotes displayed even if you have endnotes numbering turned off. In that case, your endnotes list basically becomes a “list of references” without any association with specific text in your document. This is probably the best option if you find the inline endnotes numbering obtrusive. Your users will still have access to all the “out of line” such as URLs for hyperlinks.</para></footnote> </para> <para>The default heading for the endnotes list is <literal>NOTES</literal>. To change that, set a non-empty value for the <parameter>man.endnotes.list.heading</parameter> parameter.</para> <para>In the case of notesources that are links: Along with the URL for each link, the endnotes list includes the contents of the link. The list thus includes only non-empty<footnote> <para>A “non-empty” link is one that looks like this:<literallayout class="monospaced"> <ulink url="http://docbook.sf.net/snapshot/xsl/doc/manpages/">manpages</ulink></literallayout> an “empty link” is on that looks like this:<literallayout class="monospaced"> <ulink url="http://docbook.sf.net/snapshot/xsl/doc/manpages/"/></literallayout> </para></footnote> links. Empty links are never included, and never numbered. They are simply displayed inline, without any numbering.</para> <para>In addition, if there are multiple instances of links in a <tag>refentry</tag> that have the same URL, the URL is listed only once. The contents listed for that link in the endnotes list are the contents of the first link which has that URL.</para> <para>If you disable endnotes listing, you should probably also set <parameter>man.links.are.underlined</parameter> to zero (to disable link underlining).</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.endnotes.list.enabled.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.endnotes.list.enabled.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/man.endnotes.list.enabled.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. |