Swiftdiff options
| author | Tobias Markmann <tm@ayena.de> | 2018-07-13 15:20:36 (GMT) |
|---|---|---|
| committer | Tobias Markmann <tm@ayena.de> | 2018-09-26 14:05:36 (GMT) |
| commit | 1536284a15743f6ec41d3230177a24d245158a9d (patch) | |
| tree | 21216d18d93ddfc620e6b36dc28428c5d5b71775 /3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml | |
| parent | 091f6e520694360a0407ab0cf3bb036fb461e6e3 (diff) | |
| download | swift-1536284a15743f6ec41d3230177a24d245158a9d.zip swift-1536284a15743f6ec41d3230177a24d245158a9d.tar.bz2 | |
Update SCons in 3rdParty from 2.4.0 to 3.0.1
This also has our scons patch in 3rdParty/SCons applied.
Test-Information:
Builds with unit tests on macOS 10.13.6.
Change-Id: I25d3662eeec27a76dab10d501ba46dc16f0bef4b
Diffstat (limited to '3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml')
| -rw-r--r-- | 3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml | 70 |
1 files changed, 70 insertions, 0 deletions
diff --git a/3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml b/3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml new file mode 100644 index 0000000..8db98d3 --- /dev/null +++ b/3rdParty/SCons/scons-3.0.1/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/manpages/pi.xml @@ -0,0 +1,70 @@ +<?xml version="1.0"?> + +<reference><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> + +<refentry xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="dbman_funcsynopsis-style"> +<refnamediv> +<refname>dbman_funcsynopsis-style</refname> +<refpurpose>Specifies presentation style for a funcsynopsis.</refpurpose> +</refnamediv> +<refsynopsisdiv> + + <synopsis><tag class="xmlpi">dbman funcsynopsis-style="kr"|"ansi"</tag></synopsis> + +</refsynopsisdiv> +<refsect1><title>Description</title> + +<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> + + </refsect1><refsect1><title>Parameters</title> + +<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> + + </refsect1><refsect1 role="params"><title>Related Global Parameters</title> + +<para><parameter>man.funcsynopsis.style</parameter></para> + + </refsect1></refentry> +</reference> + |