From 80e2b75e8ed1a3c078a666d463d9f3f37feb82d8 Mon Sep 17 00:00:00 2001
From: John Terpstra <jht@samba.org>
Date: Mon, 17 Oct 2005 17:49:56 +0000
Subject: Fixing bad XML to ascii code conversions by replacing smbconfblocks
 with programlisting tags. - Bug 2032. (This used to be commit
 b11bf7831ced23a7d1b412067b7c09b4aac45afb)

---
 docs/manpages-3/smb.conf.5.xml | 36 ++++++++++++++++--------------------
 1 file changed, 16 insertions(+), 20 deletions(-)

diff --git a/docs/manpages-3/smb.conf.5.xml b/docs/manpages-3/smb.conf.5.xml
index 15eef17580..833296d2d9 100644
--- a/docs/manpages-3/smb.conf.5.xml
+++ b/docs/manpages-3/smb.conf.5.xml
@@ -111,27 +111,25 @@
 	<para>
 	The following sample section defines a file space share.  The user has write access to the path <filename
 	moreinfo="none">/home/bar</filename>.  The share is accessed via the share name <literal>foo</literal>:
-	</para>
-
-<smbconfblock>
+<programlisting>
 	<smbconfsection name="[foo]"/>
 	<smbconfoption name="path">/home/bar</smbconfoption>
 	<smbconfoption name="read only">no</smbconfoption>
-</smbconfblock>
+</programlisting>
+	</para>
 
 	<para>
 	The following sample section defines a printable share.  The share is read-only, but printable. That is,
 	the only write access permitted is via calls to open, write to and close a spool file. The <emphasis>guest
 	ok</emphasis> parameter means access will be permitted as the default guest user (specified elsewhere):
-	</para>
-
-<smbconfblock>
+<programlisting>
 	<smbconfsection name="[aprinter]"/>
 	<smbconfoption name="path">/usr/spool/public</smbconfoption>
 	<smbconfoption name="read only">yes</smbconfoption>
 	<smbconfoption name="printable">yes</smbconfoption>
 	<smbconfoption name="guest ok">yes</smbconfoption>
-</smbconfblock>
+</programlisting>
+	</para>
 
 </refsect1>
 
@@ -199,12 +197,11 @@
 		<para>
 		The [homes] section can specify all the parameters a normal service section can specify, though some make more sense 
 		than others. The following is a typical and suitable [homes] section:
+<programlisting>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="read only">no</smbconfoption>
+</programlisting>
 		</para>
-
-	<smbconfblock>
-		<smbconfsection name="[homes]"/>
-		<smbconfoption name="read only">no</smbconfoption>
-	</smbconfblock>
 	
 		<para>
 		An important point is that if guest access is specified in the [homes] section, all home directories will be 
@@ -260,15 +257,14 @@
 		<para>
 		Typically the path specified is that of a world-writeable spool directory with the sticky bit set on 
 		it. A typical [printers] entry looks like this:
+<programlisting>
+<smbconfsection name="[printers]"/>
+<smbconfoption name="path">/usr/spool/public</smbconfoption>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+</programlisting>
 		</para>
 
-	<smbconfblock>
-		<smbconfsection name="[printers]"/>
-		<smbconfoption name="path">/usr/spool/public</smbconfoption>
-		<smbconfoption name="guest ok">yes</smbconfoption>
-		<smbconfoption name="printable">yes</smbconfoption>
-	</smbconfblock>
-
 		<para>
 		All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. 
 		If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file
-- 
cgit