diff options
Diffstat (limited to 'docs/htmldocs/unicode.html')
| -rw-r--r-- | docs/htmldocs/unicode.html | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html new file mode 100644 index 0000000000..01cc974f5c --- /dev/null +++ b/docs/htmldocs/unicode.html @@ -0,0 +1,69 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 27. Unicode/Charsets</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="integrate-ms-networks.html" title="Chapter 26. Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter 28. Samba Backup Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 27. Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="Backup.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter 27. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><div class="affiliation"><div class="address"><p><tt class="email"><<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="unicode.html#id2963374">Features and Benefits</a></dt><dt><a href="unicode.html#id2963419">What Are Charsets and Unicode?</a></dt><dt><a href="unicode.html#id2963499">Samba and Charsets</a></dt><dt><a href="unicode.html#id2963627">Conversion from Old Names</a></dt><dt><a href="unicode.html#id2963643">Japanese Charsets</a></dt><dt><a href="unicode.html#id2963781">Common Errors</a></dt><dd><dl><dt><a href="unicode.html#id2963788">CP850.so Can't Be Found</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963374"></a>Features and Benefits</h2></div></div><div></div></div><p> +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 +ago it was common for software to be written for exclusive use in the country of +origin. +</p><p> +Of all the effort that has been brought to bear on providing native language support +for all computer users, the efforts of the <ulink url="http://www.openi18n.org/">Openi18n organization</ulink> is deserving of +special mention. +</p><p> +Samba-2.x supported a single locale through a mechanism called +<span class="emphasis"><em>codepages</em></span>. Samba-3 is destined to become a truly trans-global +file and printer-sharing platform. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963419"></a>What Are Charsets and Unicode?</h2></div></div><div></div></div><p> +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 <span class="emphasis"><em>character set (charset) +</em></span> that is used. +</p><p> +A charset can be seen as a table that is used to translate numbers to +letters. Not all computers use the same charset (there are charsets +with German umlauts, Japanese characters, and so on). Usually a charset contains +256 characters, which means that storing a character with it takes +exactly one byte. </p><p> +There are also charsets that support even more characters, +but those need twice as much storage space (or more). These +charsets can contain <b class="command">256 * 256 = 65536</b> characters, which +is more than all possible characters one could think of. They are called +multibyte charsets because they use more then one byte to +store one character. +</p><p> +A standardized multibyte charset is <ulink url="http://www.unicode.org/">unicode</ulink>. +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. +</p><p>Old Windows clients use single-byte charsets, named +<i class="parameter"><tt>codepages</tt></i>, by Microsoft. However, there is no support for +negotiating the charset to be used in the SMB/CIFS protocol. Thus, you +have to make sure you are using the same charset when talking to an older client. +Newer clients (Windows NT, 200x, XP) talk unicode over the wire. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963499"></a>Samba and Charsets</h2></div></div><div></div></div><p> +As of Samba-3.0, Samba can (and will) talk unicode over the wire. Internally, +Samba knows of three kinds of character sets: +</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2963521"></a><i class="parameter"><tt>unix charset</tt></i></span></dt><dd><p> + This is the charset used internally by your operating system. + The default is <tt class="constant">UTF-8</tt>, which is fine for most + systems, which covers all characters in all languages. The default in previous Samba releases was <tt class="constant">ASCII</tt>. + </p></dd><dt><span class="term"><a class="indexterm" name="id2963558"></a><i class="parameter"><tt>display charset</tt></i></span></dt><dd><p>This is the charset Samba will use to print messages + on your screen. It should generally be the same as the <i class="parameter"><tt>unix charset</tt></i>. + </p></dd><dt><span class="term"><a class="indexterm" name="id2963592"></a><i class="parameter"><tt>dos charset</tt></i></span></dt><dd><p>This is the charset Samba uses when communicating with + DOS and Windows 9x/Me clients. It will talk unicode to all newer clients. + The default depends on the charsets you have installed on your system. + Run <b class="command">testparm -v | grep "dos charset"</b> to see + what the default is on your system. + </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963627"></a>Conversion from Old Names</h2></div></div><div></div></div><p>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.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963643"></a>Japanese Charsets</h2></div></div><div></div></div><p>Samba does not work correctly with Japanese charsets yet. Here are +points of attention when setting it up:</p><div class="itemizedlist"><ul type="disc"><li><p>You should set <a class="indexterm" name="id2963664"></a><i class="parameter"><tt>mangling method</tt></i> = hash</p></li><li><p>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.</p></li><li><p>You should set <a class="indexterm" name="id2963693"></a><i class="parameter"><tt>dos charset</tt></i> = CP932, not + Shift_JIS, SJIS.</p></li><li><p>Currently only <a class="indexterm" name="id2963713"></a><i class="parameter"><tt>UNIX charset</tt></i> = CP932 + will work (but still has some problems...) because of iconv() issues. + <a class="indexterm" name="id2963729"></a><i class="parameter"><tt>UNIX charset</tt></i> = EUC-JP does not work well because of + iconv() issues.</p></li><li><p>Currently Samba-3.0 does not support <a class="indexterm" name="id2963749"></a><i class="parameter"><tt>UNIX charset</tt></i> = UTF8-MAC/CAP/HEX/JIS*.</p></li></ul></div><p>More information (in Japanese) is available at: <ulink url="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</ulink>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963781"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963788"></a>CP850.so Can't Be Found</h3></div></div><div></div></div><p>“<span class="quote">Samba is complaining about a missing <tt class="filename">CP850.so</tt> file.</span>”</p><p><span class="emphasis"><em>Answer:</em></span> CP850 is the default <a class="indexterm" name="id2963814"></a><i class="parameter"><tt>dos charset</tt></i>. + The <a class="indexterm" name="id2963828"></a><i class="parameter"><tt>dos charset</tt></i> is used to convert data to the codepage used by your dos clients. + If you do not have any dos clients, you can safely ignore this message. </p><p>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 to configure found iconv.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Backup.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 26. Integrating MS Windows Networks with Samba </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 28. Samba Backup Techniques</td></tr></table></div></body></html> |