<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="side.region.precedence">
<refmeta>
<refentrytitle>side.region.precedence</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>side.region.precedence</refname>
<refpurpose>Determines side region page layout precedence</refpurpose>
</refnamediv>
<refsynopsisdiv> <src:fragment xml:id="side.region.precedence.frag">
<xsl:param name="side.region.precedence">false</xsl:param>
</src:fragment>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If optional side regions on a page
are established using parameters such as
<parameter>body.margin.inner</parameter>,
<parameter>region.inner.extent</parameter>, etc., then this
parameter determines what happens at the corners where the
side regions meet the header and footer regions.</para>
<para>If the value of this parameter is <literal>true</literal>,
then the side regions have precedence and extend higher
and lower, while the header and footer regions are narrower
and fit inside the side regions.</para>
<para>If the value of this parameter is <literal>false</literal>
(the default value), then the header and footer regions
have precedence and extend over and below the side regions.
Any value other than <literal>true</literal> or
<literal>false</literal> is taken to be <literal>false</literal>.</para>
<para>If you need to set precedence separately for
individual regions, then you can set four
parameters that are normally internal to the stylesheet.
These four parameters are normally set based
on the value from <parameter>side.region.precedence</parameter>:</para>
<programlisting>region.before.precedence
region.after.precedence
region.start.precedence
region.end.precedence</programlisting>
<para>See also
<parameter>region.inner.extent</parameter>,
<parameter>region.outer.extent</parameter>,
<parameter>body.margin.inner</parameter>,
<parameter>body.margin.outer</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/side.region.precedence.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/side.region.precedence.xml | |||||
| #1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
| //guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/side.region.precedence.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. |
||