<?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:d="http://docbook.org/ns/docbook" xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" xmlns:xlink="http://www.w3.org/1999/xlink" exclude-result-prefixes="doc d" version='1.0'> <!-- ******************************************************************** $Id: pi.xsl 7644 2008-01-16 11:04:07Z xmldoc $ ******************************************************************** This file is part of the XSL DocBook Stylesheet distribution. See ../README or http://docbook.sf.net/release/xsl/current/ for copyright and other information. ******************************************************************** --> <doc:reference xmlns=""><info><title>manpages Processing Instruction Reference</title> <releaseinfo role="meta"> $Id: pi.xsl 7644 2008-01-16 11:04:07Z xmldoc $ </releaseinfo> </info> <partintro xml:id="partintro"> <title>Introduction</title> <para>This is generated reference documentation for all user-specifiable processing instructions (PIs) in the DocBook XSL stylesheets for manpages output. <note> <para>You add these PIs at particular points in a document to cause specific “exceptions” to formatting/output behavior. To make global changes in formatting/output behavior across an entire document, it’s better to do it by setting an appropriate stylesheet parameter (if there is one).</para> </note> </para> </partintro> </doc:reference> <!-- ==================================================================== --> <doc:pi name="dbman_funcsynopsis-style" xmlns=""> <refpurpose>Specifies presentation style for a funcsynopsis.</refpurpose> <refdescription> <para>Use the <tag class="xmlpi">dbman funcsynopsis-style</tag> PI as a child of a <tag>funcsynopsis</tag> or anywhere within a funcsynopsis to control the presentation style for output of all <tag>funcprototype</tag> instances within that funcsynopsis.</para> </refdescription> <refsynopsisdiv> <synopsis><tag class="xmlpi">dbman funcsynopsis-style="kr"|"ansi"</tag></synopsis> </refsynopsisdiv> <refparameter> <variablelist> <varlistentry><term>funcsynopsis-style="kr"</term> <listitem> <para>Displays the <tag>funcprototype</tag> in K&R style</para> </listitem> </varlistentry> <varlistentry><term>funcsynopsis-style="ansi"</term> <listitem> <para>Displays the <tag>funcprototype</tag> in ANSI style</para> </listitem> </varlistentry> </variablelist> </refparameter> <refsee role="params"> <para><parameter>man.funcsynopsis.style</parameter></para> </refsee> </doc:pi> <xsl:template name="pi.dbman_funcsynopsis-style"> <xsl:param name="node" select="."/> <xsl:call-template name="pi-attribute"> <xsl:with-param name="pis" select="$node/processing-instruction('dbman')"/> <xsl:with-param name="attribute" select="'funcsynopsis-style'"/> </xsl:call-template> </xsl:template> </xsl:stylesheet>
# | 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/manpages/pi.xsl | |||||
#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/manpages/pi.xsl | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/manpages/pi.xsl | |||||
#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. |