From c97b78b4452ef39ffe28a1427f6f555248a70a1c Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Sun, 13 Mar 2005 18:25:08 +0000
Subject: More validation fixes; building FO-PDF versions of the HOWTO and the
 Guide work now! (This used to be commit
 2192c44663d3031cd6c0f228aea4a8cdd2a29a82)

---
 docs/Samba-HOWTO-Collection/Unicode.xml | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

(limited to 'docs/Samba-HOWTO-Collection/Unicode.xml')

diff --git a/docs/Samba-HOWTO-Collection/Unicode.xml b/docs/Samba-HOWTO-Collection/Unicode.xml
index cf29ef2b7a..a858a38508 100644
--- a/docs/Samba-HOWTO-Collection/Unicode.xml
+++ b/docs/Samba-HOWTO-Collection/Unicode.xml
@@ -375,14 +375,12 @@ Setting up Japanese charsets is quite difficult. This is mainly because:
 			</para>
 
 <smbconfexample><title>VFS CAP</title>
-<smbconfsection>[global]</smbconfsection>
+<smbconfsection name="[global]"/>
 <smbconfcomment>the locale name "CP932" may be different</smbconfcomment>
 <smbconfoption name="dos charset">CP932</smbconfoption>
 <smbconfoption name="unix charset">CP932</smbconfoption>
 
-<member>...</member>
-
-<smbconfsection>[cap-share]</smbconfsection>
+<smbconfsection name="[cap-share]"/>
 <smbconfoption name="vfs option">cap</smbconfoption>
 </smbconfexample>
 
-- 
cgit