From 3878085eca35d5c3b08761f61281de0b1b49ce2d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 1 Jul 2003 22:58:52 +0000 Subject: regenerate docs (This used to be commit cc02d3bc170fe5c8c4474156edb6c83720a47aa0) --- docs/htmldocs/unicode.html | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'docs/htmldocs/unicode.html') diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html index e9ab20044f..a971602e81 100644 --- a/docs/htmldocs/unicode.html +++ b/docs/htmldocs/unicode.html @@ -1,5 +1,4 @@ - -Chapter 27. Unicode/Charsets

Chapter 27. Unicode/Charsets

Jelmer R. Vernooij

The Samba Team

TAKAHASHI Motonobu

25 March 2003

Features and Benefits

+Chapter 27. Unicode/Charsets

Chapter 27. Unicode/Charsets

Jelmer R. Vernooij

The Samba Team

TAKAHASHI Motonobu

25 March 2003

Features and Benefits

Every industry eventually matures. One of the great areas of maturation is in the focus that has been given over the past decade to make it possible for anyone anywhere to use a computer. It has not always been that way, in fact, not so long @@ -12,9 +11,9 @@ special mention. For more information about Openi18n please refer to: http://www.openi18n.org/.

Samba-2.x supported a single locale through a mechanism called -codepages. Samba-3 is destined to become a truely trans-global +codepages. Samba-3 is destined to become a truly trans-global file and printer sharing platform. -

What are charsets and unicode?

+

What are charsets and unicode?

Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned to a certain number depends on the character set(charset) @@ -37,11 +36,11 @@ 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 communicating.

Old windows clients used to use single-byte charsets, named -'codepages' by microsoft. However, there is no support for +'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. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -

Samba and charsets

+

Samba and charsets

As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, samba knows of three kinds of character sets:

unix charset

@@ -55,14 +54,14 @@ samba knows of three kinds of character sets: The default depends on the charsets you have installed on your system. Run testparm -v | grep "dos charset" to see what the default is on your system. -

Conversion from old names

Because previous samba versions did not do any charset conversion, +

Conversion from old names

Because previous samba versions did not do any charset conversion, 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' \; -

Japanese charsets

Samba doesn't work correctly with Japanese charsets yet. Here are +

Japanese charsets

Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:

  • You should set mangling method = hash

  • There are various iconv() implementations around and not all of them work equally well. glibc2's iconv() has a critical problem -- cgit