From bfc3b2d82ba4791ea2f1fa74054f1a88aab32de6 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Thu, 12 Feb 2009 15:44:12 +0000
Subject: [PATCH] Fix indentation in manpage

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9437 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 manpages/shorewall-rules.xml | 97 +++++++++++++++++-------------------
 1 file changed, 47 insertions(+), 50 deletions(-)

diff --git a/manpages/shorewall-rules.xml b/manpages/shorewall-rules.xml
index 76b4a1328..d7514a940 100644
--- a/manpages/shorewall-rules.xml
+++ b/manpages/shorewall-rules.xml
@@ -435,59 +435,56 @@
                 separated by a slash (e.g. FTP/ACCEPT) is still allowed but is
                 deprecated.</para>
 
-                <programlisting></programlisting>
+                <para>The <emphasis role="bold">ACTION</emphasis> may
+                optionally be followed by ":" and a syslog log level (e.g,
+                REJECT:info or DNAT:debug). This causes the packet to be
+                logged at the specified level. Note that if the <emphasis
+                role="bold">ACTION</emphasis> involves destination network
+                address translation (DNAT, REDIRECT, SAME, etc.) then the
+                packet is logged <emphasis role="bold">before</emphasis> the
+                destination address is rewritten.</para>
+
+                <para>If the <emphasis role="bold">ACTION</emphasis> names an
+                <emphasis>action</emphasis> declared in <ulink
+                url="shorewall-actions.html">shorewall-actions</ulink>(5) or
+                in /usr/share/shorewall/actions.std then:</para>
+
+                <itemizedlist>
+                  <listitem>
+                    <para>If the log level is followed by "!' then all rules
+                    in the action are logged at the log level.</para>
+                  </listitem>
+
+                  <listitem>
+                    <para>If the log level is not followed by "!" then only
+                    those rules in the action that do not specify logging are
+                    logged at the specified level.</para>
+                  </listitem>
+
+                  <listitem>
+                    <para>The special log level <emphasis
+                    role="bold">none!</emphasis> suppresses logging by the
+                    action.</para>
+                  </listitem>
+                </itemizedlist>
+
+                <para>You may also specify <emphasis
+                role="bold">ULOG</emphasis> or <emphasis
+                role="bold">NFLOG</emphasis> (must be in upper case) as a log
+                level.This will log to the ULOG or NFLOG target for routing to
+                a separate log through use of ulogd (<ulink
+                url="http://www.netfilter.org/projects/ulogd/index.html">http://www.netfilter.org/projects/ulogd/index.html</ulink>).</para>
+
+                <para>Actions specifying logging may be followed by a log tag
+                (a string of alphanumeric characters) which is appended to the
+                string generated by the LOGPREFIX (in <ulink
+                url="shorewall.conf.html">shorewall.conf</ulink>(5)).</para>
+
+                <para>Example: ACCEPT:info:ftp would include 'ftp ' at the end
+                of the log prefix generated by the LOGPREFIX setting.</para>
               </listitem>
             </varlistentry>
           </variablelist>
-
-          <blockquote>
-            <para>The <emphasis role="bold">ACTION</emphasis> may optionally
-            be followed by ":" and a syslog log level (e.g, REJECT:info or
-            DNAT:debug). This causes the packet to be logged at the specified
-            level. Note that if the <emphasis role="bold">ACTION</emphasis>
-            involves destination network address translation (DNAT, REDIRECT,
-            SAME, etc.) then the packet is logged <emphasis
-            role="bold">before</emphasis> the destination address is
-            rewritten.</para>
-
-            <para>If the <emphasis role="bold">ACTION</emphasis> names an
-            <emphasis>action</emphasis> declared in <ulink
-            url="shorewall-actions.html">shorewall-actions</ulink>(5) or in
-            /usr/share/shorewall/actions.std then:</para>
-
-            <itemizedlist>
-              <listitem>
-                <para>If the log level is followed by "!' then all rules in
-                the action are logged at the log level.</para>
-              </listitem>
-
-              <listitem>
-                <para>If the log level is not followed by "!" then only those
-                rules in the action that do not specify logging are logged at
-                the specified level.</para>
-              </listitem>
-
-              <listitem>
-                <para>The special log level <emphasis
-                role="bold">none!</emphasis> suppresses logging by the
-                action.</para>
-              </listitem>
-            </itemizedlist>
-
-            <para>You may also specify <emphasis role="bold">ULOG</emphasis>
-            or <emphasis role="bold">NFLOG</emphasis> (must be in upper case)
-            as a log level.This will log to the ULOG or NFLOG target for
-            routing to a separate log through use of ulogd (<ulink
-            url="http://www.netfilter.org/projects/ulogd/index.html">http://www.netfilter.org/projects/ulogd/index.html</ulink>).</para>
-
-            <para>Actions specifying logging may be followed by a log tag (a
-            string of alphanumeric characters) which is appended to the string
-            generated by the LOGPREFIX (in <ulink
-            url="shorewall.conf.html">shorewall.conf</ulink>(5)).</para>
-
-            <para>Example: ACCEPT:info:ftp would include 'ftp ' at the end of
-            the log prefix generated by the LOGPREFIX setting.</para>
-          </blockquote>
         </listitem>
       </varlistentry>