<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.indent.refsect"> <refmeta> <refentrytitle>man.indent.refsect</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>man.indent.refsect</refname> <refpurpose>Adjust indentation of refsect* and refsection?</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="man.indent.refsect.frag"> <xsl:param name="man.indent.refsect" select="0"/></src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>If the value of <parameter>man.indent.refsect</parameter> is non-zero, the width of the left margin for <tag>refsect1</tag>, <tag>refsect2</tag> and <tag>refsect3</tag> contents and titles (and first-level, second-level, and third-level nested <tag>refsection</tag>instances) is adjusted by the value of the <parameter>man.indent.width</parameter> parameter. With <parameter>man.indent.width</parameter> set to its default value of <literal>3n</literal>, the main results are that: <itemizedlist> <listitem> <para>contents of <tag>refsect1</tag> are output with a left margin of three characters instead the roff default of seven or eight characters</para> </listitem> <listitem> <para>contents of <tag>refsect2</tag> are displayed in console output with a left margin of six characters instead the of the roff default of seven characters</para> </listitem> <listitem> <para> the contents of <tag>refsect3</tag> and nested <tag>refsection</tag> instances are adjusted accordingly.</para> </listitem> </itemizedlist> If instead the value of <parameter>man.indent.refsect</parameter> is zero, no margin adjustment is done for <literal>refsect*</literal> output.</para> <tip> <para>If your content is primarly comprised of <tag>refsect1</tag> and <tag>refsect2</tag> content (or the <tag>refsection</tag> equivalent) – with few or no <tag>refsect3</tag> or lower nested sections , you may be able to “conserve” space in your output by setting <parameter>man.indent.refsect</parameter> to a non-zero value. Doing so will “squeeze” the left margin in such as way as to provide an additional four characters of “room” per line in <tag>refsect1</tag> output. That extra room may be useful if, for example, you have many verbatim sections with long lines in them.</para> </tip> </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.indent.refsect.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. |