<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.output.better.ps.enabled"> <refmeta> <refentrytitle>man.output.better.ps.enabled</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>man.output.better.ps.enabled</refname> <refpurpose>Enable enhanced print/PostScript output?</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.output.better.ps.enabled.frag"> <xsl:param name="man.output.better.ps.enabled">0</xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If the value of the <parameter>man.output.better.ps.enabled</parameter> parameter is non-zero, certain markup is embedded in each generated man page such that PostScript output from the <command>man -Tps</command> command for that page will include a number of enhancements designed to improve the quality of that output.</para> <para>If <parameter>man.output.better.ps.enabled</parameter> is zero (the default), no such markup is embedded in generated man pages, and no enhancements are included in the PostScript output generated from those man pages by the <command>man -Tps</command> command.</para> <warning> <para>The enhancements provided by this parameter rely on features that are specific to groff (GNU troff) and that are not part of “classic” AT&T troff or any of its derivatives. Therefore, any man pages you generate with this parameter enabled will be readable only on systems on which the groff (GNU troff) program is installed, such as GNU/Linux systems. The pages <emphasis role="bold">will not not be readable on systems on with the classic troff (AT&T troff) command is installed</emphasis>.</para> </warning> <para>The value of this parameter only affects PostScript output generated from the <command>man</command> command. It has no effect on output generated using the FO backend.</para> <tip> <para>You can generate PostScript output for any man page by running the following command:</para> <programlisting> man <replaceable>FOO</replaceable> -Tps > <replaceable>FOO</replaceable>.ps</programlisting> <para>You can then generate PDF output by running the following command:</para> <programlisting> ps2pdf <replaceable>FOO</replaceable>.ps</programlisting> </tip> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#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. |