fixed quotes, add CVS Id

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1006 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb

Shorewall-docs/support.xml

@@ -2,6 +2,8 @@
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <article id="IPIP">
+  <!--$Id$-->
+
   <articleinfo>
     <title>Shorewall Support Guide</title>
 
@@ -26,8 +28,8 @@
       document under the terms of the GNU Free Documentation License, Version
       1.2 or any later version published by the Free Software Foundation; with
       no Invariant Sections, with no Front-Cover, and with no Back-Cover
-      Texts. A copy of the license is included in the section entitled &#34;<ulink
+      Texts. A copy of the license is included in the section entitled
-      url="GnuCopyright.htm">GNU Free Documentation License</ulink>&#34;.</para>
+      <quote><ulink url="GnuCopyright.htm">GNU Free Documentation License</ulink></quote>.</para>
     </legalnotice>
 
     <revhistory>
@@ -116,21 +118,22 @@
       </listitem>
 
       <listitem>
-        <para>Please don&#39;t describe your problem as &#34;Computer A
+        <para>Please don&#39;t describe your problem as <quote>Computer A
-        can&#39;t see Computer B&#34;. Of course it can&#39;t -- it hasn&#39;t
+        can&#39;t see Computer B</quote>. Of course it can&#39;t -- it
-        any eyes! If ping from A to B fails, say so (and see below for
+        hasn&#39;t any eyes! If ping from A to B fails, say so (and see below
-        information about reporting &#39;ping&#39; problems). If Computer B
+        for information about reporting <quote>ping</quote> problems). If
-        doesn&#39;t show up in &#34;Network Neighborhood&#34; then say so.</para>
+        Computer B doesn&#39;t show up in <quote>Network Neighborhood</quote>
+        then say so.</para>
       </listitem>
 
       <listitem>
         <para>Please give details about what doesn&#39;t work. Reports that
-        say &#34;I followed the directions and it didn&#39;t work&#34; will
+        say <quote>I followed the directions and it didn&#39;t work</quote>
-        elicit sympathy but probably little in the way of help. Again -- if
+        will elicit sympathy but probably little in the way of help. Again --
-        ping from A to B fails, say so (and see below for information about
+        if ping from A to B fails, say so (and see below for information about
-        reporting &#39;ping&#39; problems). If Computer B doesn&#39;t show up
+        reporting <quote>ping</quote> problems). If Computer B doesn&#39;t
-        in &#34;Network Neighborhood&#34; then say so. If access by IP address
+        show up in <quote>Network Neighborhood</quote> then say so. If access
-        works but by DNS names it doesn&#39;t then say so.</para>
+        by IP address works but by DNS names it doesn&#39;t then say so.</para>
       </listitem>
 
       <listitem>
@@ -213,8 +216,8 @@
       </listitem>
 
       <listitem>
-        <para>Do you see any &#34;Shorewall&#34; messages (&#34;<emphasis
+        <para>Do you see any <quote>Shorewall</quote> messages (<quote><emphasis
-        role="underline">/sbin/shorewall show log</emphasis>&#34;) when you
+        role="underline">/sbin/shorewall show log</emphasis></quote>) when you
         exercise the function that is giving you problems? If so, include the
         message(s) in your post along with a copy of your
         /etc/shorewall/interfaces file.</para>
@@ -229,9 +232,9 @@
       </listitem>
 
       <listitem>
-        <para>If an error occurs when you try to &#34;<emphasis
+        <para>If an error occurs when you try to <quote><emphasis
-        role="underline">shorewall start</emphasis>&#34;, include a trace (See
+        role="underline">shorewall start</emphasis></quote>, include a trace
-        the Troubleshooting section for instructions).</para>
+        (See the Troubleshooting section for instructions).</para>
       </listitem>
 
       <listitem>
@@ -254,15 +257,15 @@
 
     <para>A growing number of MTAs serving list subscribers are rejecting all
     HTML traffic. At least one MTA has gone so far as to blacklist
-    shorewall.net &#34;for continuous abuse&#34; because it has been my policy
+    shorewall.net <quote>for continuous abuse</quote> because it has been my
-    to allow HTML in list posts!!</para>
+    policy to allow HTML in list posts!!</para>
 
     <para>I think that blocking all HTML is a Draconian way to control spam
     and that the ultimate losers here are not the spammers but the list
     subscribers whose MTAs are bouncing all shorewall.net mail. As one list
-    subscriber wrote to me privately &#34;These e-mail admin&#39;s need to get
+    subscriber wrote to me privately <quote>These e-mail admin&#39;s need to
-    a (expletive deleted) life instead of trying to rid the planet of HTML
+    get a (expletive deleted) life instead of trying to rid the planet of HTML
-    based e-mail&#34;. Nevertheless, to allow subscribers to receive list
+    based e-mail</quote>. Nevertheless, to allow subscribers to receive list
     posts as must as possible, I have now configured the list server at
     shorewall.net to convert all HTML to plain text. These converted posts are
     difficult to read so all of us will appreciate it if you just post in