From a2e3ba6e1281a7d3693173679ec7fb28898df319 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 12 Aug 2003 17:36:25 +0000 Subject: Merge over book changes into 3_0 CVS (This used to be commit d8fe4a81fb0d4972b2331b3d5fc4890244b44c33) --- docs/docbook/projdoc/unicode.xml | 64 ++++++++++++++++++++++------------------ 1 file changed, 35 insertions(+), 29 deletions(-) (limited to 'docs/docbook/projdoc/unicode.xml') diff --git a/docs/docbook/projdoc/unicode.xml b/docs/docbook/projdoc/unicode.xml index d24ec4b5cd..28d6f76cdf 100644 --- a/docs/docbook/projdoc/unicode.xml +++ b/docs/docbook/projdoc/unicode.xml @@ -25,9 +25,8 @@ origin. Of all the effort that has been brought to bear on providing native language support -for all computer users, the efforts of the Openi18n organisation is deserving of -special mention. For more information about Openi18n please refer to: -http://www.openi18n.org/. +for all computer users, the efforts of the Openi18n organisation is deserving of +special mention. @@ -62,17 +61,16 @@ store one character). -A standardised multibyte charset is unicode, info is available at -www.unicode.org. -A big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are + A standardised multibyte charset is unicode. +A big advantage of using a multibyte charset is that you only need one; there +is no need to make sure two computers use the same charset when they are communicating. -Old windows clients used to use single-byte charsets, named +Old windows clients use single-byte charsets, named 'codepages' by Microsoft. However, there is no support for negotiating the charset to be used in the smb protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. +have to make sure you are using the same charset when talking to an older client. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. @@ -87,23 +85,23 @@ samba knows of three kinds of character sets: - unix charset + unix charset This is the charset used internally by your operating system. - The default is ASCII, which is fine for most - systems. + The default is UTF-8, which is fine for most + systems. The default in previous samba releases was ASCII. - display charset + display charset This is the charset samba will use to print messages on your screen. It should generally be the same as the unix charset. - dos charset + dos charset 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. @@ -122,14 +120,10 @@ samba knows of three kinds of character sets: characters in filenames are usually not correct in the unix charset but only for the local charset used by the DOS/Windows clients. -The following script from Steve Langasek converts all -filenames from CP850 to the iso8859-15 charset. - - -#find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ - -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; - +Bjoern Jacke has written a utility named convm that can convert whole directory + structures to different charsets with one single command. + @@ -140,29 +134,41 @@ points of attention when setting it up: -You should set mangling method = -hash + You should set mangling methodhash 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. -You should set dos charset = CP932, not +You should set dos charsetCP932, not Shift_JIS, SJIS... -Currently only unix charset = CP932 +Currently only unix charsetCP932 will work (but still has some problems...) because of iconv() issues. -unix charset = EUC-JP doesn't work well because of +unix charsetEUC-JP doesn't work well because of iconv() issues. -Currently Samba 3.0 does not support unix charset -= UTF8-MAC/CAP/HEX/JIS* +Currently Samba 3.0 does not support unix charsetUTF8-MAC/CAP/HEX/JIS* -More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html. +More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html. + + + + + Common errors + + + CP850.so can't be found + + Samba is complaining about a missing CP850.so file. + + CP850 is the default dos charset. The dos charset is used to convert data to the codepage used by your dos clients. If you don't have any dos clients, you can safely ignore this message. + CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv. + -- cgit