<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.encoding"> <refmeta> <refentrytitle>man.output.encoding</refentrytitle> <refmiscinfo class="other" otherclass="datatype">string</refmiscinfo> </refmeta> <refnamediv> <refname>man.output.encoding</refname> <refpurpose>Encoding used for man-page output</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.output.encoding.frag"> <xsl:param name="man.output.encoding">UTF-8</xsl:param> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>This parameter specifies the encoding to use for files generated by the manpages stylesheet. Not all processors support specification of this parameter.</para> <important> <para>If the value of the <parameter>man.charmap.enabled</parameter> parameter is non-zero (the default), keeping the <parameter>man.output.encoding</parameter> parameter at its default value (<literal>UTF-8</literal>) or setting it to <literal>UTF-16</literal> <emphasis role="bold">does not cause your man pages to be output in raw UTF-8 or UTF-16</emphasis> -- because any Unicode characters for which matches are found in the enabled character map will be replaced with roff escape sequences before the final man-page files are generated.</para> <para>So if you want to generate "real" UTF-8 man pages, without any character substitution being performed on your content, you need to set <parameter>man.charmap.enabled</parameter> to zero (which will completely disable character-map processing). </para> <para>You may also need to set <parameter>man.charmap.enabled</parameter> to zero if you want to output man pages in an encoding other than <literal>UTF-8</literal> or <literal>UTF-16</literal>. Character-map processing is based on Unicode character values and may not work with other output encodings.</para> </important> </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.output.encoding.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.output.encoding.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/man.output.encoding.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. |