A lot of syntax updates, consistency when using certain tags and converting ASCII...

[sfrench/samba-autobuild/.git] / docs / docbook / projdoc / unicode.xml

diff --git a/docs/docbook/projdoc/unicode.xml b/docs/docbook/projdoc/unicode.xml
index 2351668e565e199c32d497d2ab29cccd51c14d28..c222c2bdc1e01f4300fc8fd4c9f1076223a6b3bf 100644 (file)
--- a/docs/docbook/projdoc/unicode.xml
+++ b/docs/docbook/projdoc/unicode.xml
@@ -61,7 +61,7 @@ samba knows of three kinds of character sets:
 
 <variablelist>
        <varlistentry>
-               <term>unix charset</term>
+               <term><parameter>unix charset</parameter></term>
                <listitem><para>
                This is the charset used internally by your operating system. 
                The default is <constant>ASCII</constant>, which is fine for most 
@@ -70,14 +70,14 @@ samba knows of three kinds of character sets:
        </varlistentry>
 
        <varlistentry>
-               <term>display charset</term>
+               <term><parameter>display charset</parameter></term>
                <listitem><para>This is the charset samba will use to print messages
                on your screen. It should generally be the same as the <command>unix charset</command>.
                </para></listitem>
        </varlistentry>
 
        <varlistentry>
-               <term>dos charset</term>
+               <term><parameter>dos charset</parameter></term>
                <listitem><para>This is the charset samba uses when communicating with 
                DOS and Windows 9x clients. It will talk unicode to all newer clients.
                The default depends on the charsets you have installed on your system.
@@ -114,24 +114,24 @@ points of attention when setting it up:</para>
 
 <itemizedlist>
 
-<listitem><para>You should set <command>mangling method =
-hash</command></para></listitem>
+<listitem><para>You should set <parameter>mangling method =
+hash</parameter></para></listitem>
 
 <listitem><para>There are various iconv() implementations around and not
 all of  them work equally well. glibc2's iconv() has a critical problem
 in CP932.  libiconv-1.8 works with CP932 but still has some problems and
 does not  work with EUC-JP.</para></listitem>
 
-<listitem><para>You should set <command>dos charset = CP932</command>, not
+<listitem><para>You should set <parameter>dos charset = CP932</parameter>, not
 Shift_JIS, SJIS...</para></listitem>
 
-<listitem><para>Currently only <command>unix charset = CP932</command>
+<listitem><para>Currently only <parameter>unix charset = CP932</parameter>
 will work (but still has some problems...) because of iconv() issues.
-<command>unix charset = EUC-JP</command> doesn't work well because of
+<parameter>unix charset = EUC-JP</parameter> doesn't work well because of
 iconv() issues.</para></listitem>
 
-<listitem><para>Currently Samba 3.0 does not support <command>unix charset
-= UTF8-MAC/CAP/HEX/JIS*</command></para></listitem>
+<listitem><para>Currently Samba 3.0 does not support <parameter>unix charset
+= UTF8-MAC/CAP/HEX/JIS*</parameter></para></listitem>
 
 </itemizedlist>