diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/unicode.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/unicode.html | 170 |
1 files changed, 85 insertions, 85 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/unicode.html b/docs/htmldocs/Samba3-HOWTO/unicode.html index 3c43bafb9c..05d180ea57 100644 --- a/docs/htmldocs/Samba3-HOWTO/unicode.html +++ b/docs/htmldocs/Samba3-HOWTO/unicode.html @@ -1,5 +1,5 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 30. Unicode/Charsets</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter 31. 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 30. 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 30. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><span class="contrib">Japanese character support</span> <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></code></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unicode.html#id2669736">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669787">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2669921">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670056">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2670088">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2670218">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670859">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2670982">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2671128">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2671134">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669736"></a>Features and Benefits</h2></div></div></div><p> -<a class="indexterm" name="id2669744"></a> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 30. Unicode/Charsets</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter 31. 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 30. 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" title="Chapter 30. Unicode/Charsets"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter 30. 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><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></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><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><span class="contrib">Japanese character support</span> <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></code></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unicode.html#id432542">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id432588">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id432707">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id432832">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id432862">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id432977">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id433554">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id433668">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id433807">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id433812">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432542"></a>Features and Benefits</h2></div></div></div><p> +<a class="indexterm" name="id432550"></a> 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 @@ -11,19 +11,19 @@ language support for all computer users, the efforts of the <a class="ulink" href="http://www.openi18n.org/" target="_top">Openi18n organization</a> is deserving of special mention. </p><p> -<a class="indexterm" name="id2669772"></a> +<a class="indexterm" name="id432574"></a> 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 transglobal 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="id2669787"></a>What Are Charsets and Unicode?</h2></div></div></div><p> -<a class="indexterm" name="id2669795"></a> +</p></div><div class="sect1" title="What Are Charsets and Unicode?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432588"></a>What Are Charsets and Unicode?</h2></div></div></div><p> +<a class="indexterm" name="id432595"></a> Computers communicate in numbers. In texts, each number is 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 class="indexterm" name="id2669813"></a> -<a class="indexterm" name="id2669819"></a> +<a class="indexterm" name="id432611"></a> +<a class="indexterm" name="id432618"></a> 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). The American Standard Code @@ -31,36 +31,36 @@ for Information Interchange (ASCII) encoding system has been the normative chara encoding scheme used by computers to date. This employs a charset that contains 256 characters. Using this mode of encoding, each character takes exactly one byte. </p><p> -<a class="indexterm" name="id2669837"></a> -<a class="indexterm" name="id2669844"></a> +<a class="indexterm" name="id432632"></a> +<a class="indexterm" name="id432639"></a> There are also charsets that support extended characters, but those need at least twice as much storage space as does ASCII encoding. Such charsets can contain <code class="literal">256 * 256 = 65536</code> 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 class="indexterm" name="id2669866"></a> +<a class="indexterm" name="id432657"></a> One standardized multibyte charset encoding scheme is known as <a class="ulink" href="http://www.unicode.org/" target="_top">unicode</a>. 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> -<a class="indexterm" name="id2669886"></a> -<a class="indexterm" name="id2669893"></a> -<a class="indexterm" name="id2669900"></a> +<a class="indexterm" name="id432675"></a> +<a class="indexterm" name="id432682"></a> +<a class="indexterm" name="id432689"></a> Old Windows clients use single-byte charsets, named <em class="parameter"><code>codepages</code></em>, 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="id2669921"></a>Samba and Charsets</h2></div></div></div><p> -<a class="indexterm" name="id2669929"></a> -<a class="indexterm" name="id2669936"></a> +</p></div><div class="sect1" title="Samba and Charsets"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432707"></a>Samba and Charsets</h2></div></div></div><p> +<a class="indexterm" name="id432714"></a> +<a class="indexterm" name="id432721"></a> As of Samba-3, 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="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a></span></dt><dd><p> -<a class="indexterm" name="id2669968"></a> -<a class="indexterm" name="id2669974"></a> +<a class="indexterm" name="id432751"></a> +<a class="indexterm" name="id432758"></a> This is the charset used internally by your operating system. The default is <code class="constant">UTF-8</code>, which is fine for most systems and covers all characters in all languages. The default @@ -73,26 +73,26 @@ Samba knows of three kinds of character sets: The default depends on the charsets you have installed on your system. Run <code class="literal">testparm -v | grep "dos charset"</code> 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="id2670056"></a>Conversion from Old Names</h2></div></div></div><p> -<a class="indexterm" name="id2670064"></a> + </p></dd></dl></div></div><div class="sect1" title="Conversion from Old Names"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432832"></a>Conversion from Old Names</h2></div></div></div><p> +<a class="indexterm" name="id432840"></a> 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><p>Bjoern Jacke has written a utility named <a class="ulink" href="http://j3e.de/linux/convmv/" target="_top">convmv</a> that can convert whole directory structures to different charsets with one single command. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2670088"></a>Japanese Charsets</h2></div></div></div><p> +</p></div><div class="sect1" title="Japanese Charsets"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432862"></a>Japanese Charsets</h2></div></div></div><p> Setting up Japanese charsets is quite difficult. This is mainly because: -</p><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2670104"></a> +</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id432876"></a> The Windows character set is extended from the original legacy Japanese standard (JIS X 0208) and is not standardized. This means that the strictly standardized implementation cannot support the full Windows character set. - </p></li><li><p> -<a class="indexterm" name="id2670119"></a> -<a class="indexterm" name="id2670125"></a> -<a class="indexterm" name="id2670132"></a> -<a class="indexterm" name="id2670139"></a> -<a class="indexterm" name="id2670146"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id432890"></a> +<a class="indexterm" name="id432896"></a> +<a class="indexterm" name="id432903"></a> +<a class="indexterm" name="id432910"></a> +<a class="indexterm" name="id432917"></a> Mainly for historical reasons, there are several encoding methods in Japanese, which are not fully compatible with each other. There are two major encoding methods. One is the Shift_JIS series used in Windows @@ -101,35 +101,35 @@ Setting up Japanese charsets is quite difficult. This is mainly because: methods, named CAP and HEX, to keep interoperability with CAP/NetAtalk and UNIXes that can't use Japanese filenames. Some implementations of the EUC-JP series can't support the full Windows character set. - </p></li><li><p>There are some code conversion tables between Unicode and legacy + </p></li><li class="listitem"><p>There are some code conversion tables between Unicode and legacy Japanese character sets. One is compatible with Windows, another one is based on the reference of the Unicode consortium, and others are a mixed implementation. The Unicode consortium does not officially define any conversion tables between Unicode and legacy character sets, so there cannot be standard one. - </p></li><li><p>The character set and conversion tables available in iconv() depend + </p></li><li class="listitem"><p>The character set and conversion tables available in iconv() depend on the iconv library that is available. Next to that, the Japanese locale names may be different on different systems. This means that the value of the charset parameters depends on the implementation of iconv() you are using. </p><p> -<a class="indexterm" name="id2670186"></a> -<a class="indexterm" name="id2670192"></a> -<a class="indexterm" name="id2670199"></a> -<a class="indexterm" name="id2670206"></a> +<a class="indexterm" name="id432946"></a> +<a class="indexterm" name="id432953"></a> +<a class="indexterm" name="id432960"></a> +<a class="indexterm" name="id432966"></a> Though 2-byte fixed UCS-2 encoding is used in Windows internally, Shift_JIS series encoding is usually used in Japanese environments as ASCII encoding is in English environments. - </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670218"></a>Basic Parameter Setting</h3></div></div></div><p> -<a class="indexterm" name="id2670225"></a> + </p></li></ul></div><div class="sect2" title="Basic Parameter Setting"><div class="titlepage"><div><div><h3 class="title"><a name="id432977"></a>Basic Parameter Setting</h3></div></div></div><p> +<a class="indexterm" name="id432984"></a> The <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a> and <a class="link" href="smb.conf.5.html#DISPLAYCHARSET" target="_top">display charset</a> should be set to the locale compatible with the character set and encoding method used on Windows. This is usually CP932 but sometimes has a different name. </p><p> -<a class="indexterm" name="id2670262"></a> -<a class="indexterm" name="id2670268"></a> -<a class="indexterm" name="id2670275"></a> +<a class="indexterm" name="id433017"></a> +<a class="indexterm" name="id433024"></a> +<a class="indexterm" name="id433031"></a> The <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> can be either Shift_JIS series, EUC-JP series, or UTF-8. UTF-8 is always available, but the availability of other locales and the name itself depends on the system. @@ -137,7 +137,7 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Additionally, you can consider using the Shift_JIS series as the value of the <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> parameter by using the vfs_cap module, which does the same thing as - setting “<span class="quote">coding system = CAP</span>” in the Samba 2.2 series. + setting <span class="quote">“<span class="quote">coding system = CAP</span>”</span> in the Samba 2.2 series. </p><p> Where to set <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> to is a difficult question. Here is a list of details, advantages, and @@ -146,9 +146,9 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Shift_JIS series means a locale that is equivalent to <code class="constant">Shift_JIS</code>, used as a standard on Japanese Windows. In the case of <code class="constant">Shift_JIS</code>, for example, if a Japanese filename consists of 0x8ba4 and 0x974c - (a 4-bytes Japanese character string meaning “<span class="quote">share</span>”) and “<span class="quote">.txt</span>” + (a 4-bytes Japanese character string meaning <span class="quote">“<span class="quote">share</span>”</span>) and <span class="quote">“<span class="quote">.txt</span>”</span> is written from Windows on Samba, the filename on UNIX becomes - 0x8ba4, 0x974c, “<span class="quote">.txt</span>” (an 8-byte BINARY string), same as Windows. + 0x8ba4, 0x974c, <span class="quote">“<span class="quote">.txt</span>”</span> (an 8-byte BINARY string), same as Windows. </p><p>Since Shift_JIS series is usually used on some commercial-based UNIXes; hp-ux and AIX as the Japanese locale (however, it is also possible to use the EUC-JP locale series). To use Shift_JIS series on these platforms, @@ -159,33 +159,33 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Shift_JIS series is the best choice. However, broken filenames may be displayed, and some commands that cannot handle non-ASCII filenames may be aborted during parsing filenames. Especially, there - may be “<span class="quote">\ (0x5c)</span>” in filenames, which need to be handled carefully. + may be <span class="quote">“<span class="quote">\ (0x5c)</span>”</span> in filenames, which need to be handled carefully. It is best to not touch filenames written from Windows on UNIX. </p><p> Note that most Japanized free software actually works with EUC-JP only. It is good practice to verify that the Japanized free software can work with Shift_JIS. </p></dd><dt><span class="term">EUC-JP series</span></dt><dd><p> -<a class="indexterm" name="id2670409"></a> -<a class="indexterm" name="id2670416"></a> +<a class="indexterm" name="id433147"></a> +<a class="indexterm" name="id433154"></a> EUC-JP series means a locale that is equivalent to the industry standard called EUC-JP, widely used in Japanese UNIX (although EUC contains specifications for languages other than Japanese, such as EUC-KR). In the case of EUC-JP series, for example, if a Japanese - filename consists of 0x8ba4 and 0x974c and “<span class="quote">.txt</span>” is written from + filename consists of 0x8ba4 and 0x974c and <span class="quote">“<span class="quote">.txt</span>”</span> is written from Windows on Samba, the filename on UNIX becomes 0xb6a6, 0xcdad, - “<span class="quote">.txt</span>” (an 8-byte BINARY string). + <span class="quote">“<span class="quote">.txt</span>”</span> (an 8-byte BINARY string). </p><p> -<a class="indexterm" name="id2670441"></a> -<a class="indexterm" name="id2670448"></a> -<a class="indexterm" name="id2670454"></a> -<a class="indexterm" name="id2670461"></a> -<a class="indexterm" name="id2670468"></a> -<a class="indexterm" name="id2670475"></a> -<a class="indexterm" name="id2670482"></a> -<a class="indexterm" name="id2670488"></a> -<a class="indexterm" name="id2670495"></a> -<a class="indexterm" name="id2670502"></a> +<a class="indexterm" name="id433175"></a> +<a class="indexterm" name="id433182"></a> +<a class="indexterm" name="id433189"></a> +<a class="indexterm" name="id433196"></a> +<a class="indexterm" name="id433202"></a> +<a class="indexterm" name="id433209"></a> +<a class="indexterm" name="id433216"></a> +<a class="indexterm" name="id433223"></a> +<a class="indexterm" name="id433230"></a> +<a class="indexterm" name="id433236"></a> Since EUC-JP is usually used on open source UNIX, Linux, and FreeBSD, and on commercial-based UNIX, Solaris, IRIX, and Tru64 UNIX as Japanese locale (however, it is also possible on Solaris to use Shift_JIS and UTF-8, and on Tru64 UNIX it is possible to use Shift_JIS). To use EUC-JP series, most Japanese filenames created from @@ -194,11 +194,11 @@ Setting up Japanese charsets is quite difficult. This is mainly because: It is recommended to choose EUC-JP series when using Japanese filenames on UNIX. </p><p> Although there is no character that needs to be carefully treated - like “<span class="quote">\ (0x5c)</span>”, broken filenames may be displayed and some + like <span class="quote">“<span class="quote">\ (0x5c)</span>”</span>, broken filenames may be displayed and some commands that cannot handle non-ASCII filenames may be aborted during parsing filenames. </p><p> -<a class="indexterm" name="id2670535"></a> +<a class="indexterm" name="id433263"></a> Moreover, if you built Samba using differently installed libiconv, the eucJP-ms locale included in libiconv and EUC-JP series locale included in the operating system may not be compatible. In this case, you may need to @@ -209,8 +209,8 @@ Setting up Japanese charsets is quite difficult. This is mainly because: most characters are expressed using 3 bytes. Since on Windows Shift_JIS, where a character is expressed with 1 or 2 bytes is used to express Japanese, basically a byte length of a UTF-8 string the length of the UTF-8 string is 1.5 times that of the original Shift_JIS string. In the case of UTF-8, for example, if a Japanese - filename consists of 0x8ba4 and 0x974c, and “<span class="quote">.txt</span>” is written from Windows on Samba, the filename - on UNIX becomes 0xe585, 0xb1e6, 0x9c89, “<span class="quote">.txt</span>” (a 10-byte BINARY string). + filename consists of 0x8ba4 and 0x974c, and <span class="quote">“<span class="quote">.txt</span>”</span> is written from Windows on Samba, the filename + on UNIX becomes 0xe585, 0xb1e6, 0x9c89, <span class="quote">“<span class="quote">.txt</span>”</span> (a 10-byte BINARY string). </p><p> For systems where iconv() is not available or where iconv()'s locales are not compatible with Windows, UTF-8 is the only locale available. @@ -219,13 +219,13 @@ Setting up Japanese charsets is quite difficult. This is mainly because: </p><p> Some broken filenames may be displayed, and some commands that cannot handle non-ASCII filenames may be aborted during parsing - filenames. Especially, there may be “<span class="quote">\ (0x5c)</span>” in filenames, which + filenames. Especially, there may be <span class="quote">“<span class="quote">\ (0x5c)</span>”</span> in filenames, which must be handled carefully, so you had better not touch filenames written from Windows on UNIX. </p><p> -<a class="indexterm" name="id2670608"></a> -<a class="indexterm" name="id2670615"></a> -<a class="indexterm" name="id2670622"></a> +<a class="indexterm" name="id433324"></a> +<a class="indexterm" name="id433330"></a> +<a class="indexterm" name="id433337"></a> In addition, although it is not directly concerned with Samba, since there is a delicate difference between the iconv() function, which is generally used on UNIX, and the functions used on other platforms, @@ -233,23 +233,23 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Shift_JIS and Unicode UTF-8 must be done with care and recognition of the limitations involved in the process. </p><p> -<a class="indexterm" name="id2670639"></a> +<a class="indexterm" name="id433351"></a> Although Mac OS X uses UTF-8 as its encoding method for filenames, it uses an extended UTF-8 specification that Samba cannot handle, so UTF-8 locale is not available for Mac OS X. </p></dd><dt><span class="term">Shift_JIS series + vfs_cap (CAP encoding)</span></dt><dd><p> -<a class="indexterm" name="id2670660"></a> -<a class="indexterm" name="id2670666"></a> -<a class="indexterm" name="id2670673"></a> +<a class="indexterm" name="id433371"></a> +<a class="indexterm" name="id433377"></a> +<a class="indexterm" name="id433384"></a> CAP encoding means a specification used in CAP and NetAtalk, file server software for Macintosh. In the case of CAP encoding, for example, if a Japanese filename consists of 0x8ba4 and 0x974c, and - “<span class="quote">.txt</span>” is written from Windows on Samba, the filename on UNIX - becomes “<span class="quote">:8b:a4:97L.txt</span>” (a 14 bytes ASCII string). + <span class="quote">“<span class="quote">.txt</span>”</span> is written from Windows on Samba, the filename on UNIX + becomes <span class="quote">“<span class="quote">:8b:a4:97L.txt</span>”</span> (a 14 bytes ASCII string). </p><p> For CAP encoding, a byte that cannot be expressed as an ASCII - character (0x80 or above) is encoded in an “<span class="quote">:xx</span>” form. You need to take - care of containing a “<span class="quote">\(0x5c)</span>” in a filename, but filenames are not + character (0x80 or above) is encoded in an <span class="quote">“<span class="quote">:xx</span>”</span> form. You need to take + care of containing a <span class="quote">“<span class="quote">\(0x5c)</span>”</span> in a filename, but filenames are not broken in a system that cannot handle non-ASCII filenames. </p><p> The greatest merit of CAP encoding is the compatibility of encoding @@ -269,14 +269,14 @@ Setting up Japanese charsets is quite difficult. This is mainly because: </p><p> To use CAP encoding on Samba-3, you should use the unix charset parameter and VFS as in <a class="link" href="unicode.html#vfscap-intl" title="Example 30.1. VFS CAP">the VFS CAP smb.conf file</a>. - </p><div class="example"><a name="vfscap-intl"></a><p class="title"><b>Example 30.1. VFS CAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># the locale name "CP932" may be different</td></tr><tr><td><a class="indexterm" name="id2670773"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2670784"></a><em class="parameter"><code>unix charset = CP932</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[cap-share]</code></em></td></tr><tr><td><a class="indexterm" name="id2670805"></a><em class="parameter"><code>vfs option = cap</code></em></td></tr></table></div></div><br class="example-break"><p> -<a class="indexterm" name="id2670820"></a> -<a class="indexterm" name="id2670827"></a> -<a class="indexterm" name="id2670833"></a> -<a class="indexterm" name="id2670840"></a> + </p><div class="example"><a name="vfscap-intl"></a><p class="title"><b>Example 30.1. VFS CAP</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td># the locale name "CP932" may be different</td></tr><tr><td><a class="indexterm" name="id433470"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id433482"></a><em class="parameter"><code>unix charset = CP932</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[cap-share]</code></em></td></tr><tr><td><a class="indexterm" name="id433502"></a><em class="parameter"><code>vfs option = cap</code></em></td></tr></table></div></div><br class="example-break"><p> +<a class="indexterm" name="id433517"></a> +<a class="indexterm" name="id433524"></a> +<a class="indexterm" name="id433530"></a> +<a class="indexterm" name="id433537"></a> You should set CP932 if using GNU libiconv for unix charset. With this setting, - filenames in the “<span class="quote">cap-share</span>” share are written with CAP encoding. - </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670859"></a>Individual Implementations</h3></div></div></div><p> + filenames in the <span class="quote">“<span class="quote">cap-share</span>”</span> share are written with CAP encoding. + </p></dd></dl></div></div><div class="sect2" title="Individual Implementations"><div class="titlepage"><div><div><h3 class="title"><a name="id433554"></a>Individual Implementations</h3></div></div></div><p> Here is some additional information regarding individual implementations: </p><div class="variablelist"><dl><dt><span class="term">GNU libiconv</span></dt><dd><p> To handle Japanese correctly, you should apply the patch @@ -299,15 +299,15 @@ display charset = CP932 to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later. </p><p> Using the above glibc, these setting are available: - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2670935"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id2670947"></a><em class="parameter"><code>unix charset = CP932 / eucJP-ms / UTF-8</code></em></td></tr><tr><td><a class="indexterm" name="id2670959"></a><em class="parameter"><code>display charset = CP932</code></em></td></tr></table><p> + </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id433623"></a><em class="parameter"><code>dos charset = CP932</code></em></td></tr><tr><td><a class="indexterm" name="id433635"></a><em class="parameter"><code>unix charset = CP932 / eucJP-ms / UTF-8</code></em></td></tr><tr><td><a class="indexterm" name="id433646"></a><em class="parameter"><code>display charset = CP932</code></em></td></tr></table><p> </p><p> Other Japanese locales (for example, Shift_JIS and EUC-JP) should not be used because of the lack of the compatibility with Windows. - </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2670982"></a>Migration from Samba-2.2 Series</h3></div></div></div><p> -Prior to Samba-2.2 series, the “<span class="quote">coding system</span>” parameter was used. The default codepage in Samba + </p></dd></dl></div></div><div class="sect2" title="Migration from Samba-2.2 Series"><div class="titlepage"><div><div><h3 class="title"><a name="id433668"></a>Migration from Samba-2.2 Series</h3></div></div></div><p> +Prior to Samba-2.2 series, the <span class="quote">“<span class="quote">coding system</span>”</span> parameter was used. The default codepage in Samba 2.x was code page 850. In the Samba-3 series this has been replaced with the <a class="link" href="smb.conf.5.html#UNIXCHARSET" target="_top">unix charset</a> parameter. <a class="link" href="unicode.html#japancharsets" title="Table 30.1. Japanese Character Sets in Samba-2.2 and Samba-3">Japanese Character Sets in Samba-2.2 and Samba-3</a> shows the mapping table when migrating from the Samba-2.2 series to Samba-3. -</p><div class="table"><a name="japancharsets"></a><p class="title"><b>Table 30.1. Japanese Character Sets in Samba-2.2 and Samba-3</b></p><div class="table-contents"><table summary="Japanese Character Sets in Samba-2.2 and Samba-3" border="1"><colgroup><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Samba-2.2 Coding System</th><th align="center">Samba-3 unix charset</th></tr></thead><tbody><tr><td align="center">SJIS</td><td align="center">Shift_JIS series</td></tr><tr><td align="center">EUC</td><td align="center">EUC-JP series</td></tr><tr><td align="center">EUC3<sup>[<a name="id2671078" href="#ftn.id2671078" class="footnote">a</a>]</sup></td><td align="center">EUC-JP series</td></tr><tr><td align="center">CAP</td><td align="center">Shift_JIS series + VFS</td></tr><tr><td align="center">HEX</td><td align="center">currently none</td></tr><tr><td align="center">UTF8</td><td align="center">UTF-8</td></tr><tr><td align="center">UTF8-Mac<sup>[<a name="id2671108" href="#ftn.id2671108" class="footnote">b</a>]</sup></td><td align="center">currently none</td></tr><tr><td align="center">others</td><td align="center">none</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2671078" href="#id2671078" class="para">a</a>] </sup>Only exists in Japanese Samba version</p></div><div class="footnote"><p><sup>[<a name="ftn.id2671108" href="#id2671108" class="para">b</a>] </sup>Only exists in Japanese Samba version</p></div></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2671128"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2671134"></a>CP850.so Can't Be Found</h3></div></div></div><p>“<span class="quote">Samba is complaining about a missing <code class="filename">CP850.so</code> file.</span>”</p><p> +</p><div class="table"><a name="japancharsets"></a><p class="title"><b>Table 30.1. Japanese Character Sets in Samba-2.2 and Samba-3</b></p><div class="table-contents"><table summary="Japanese Character Sets in Samba-2.2 and Samba-3" border="1"><colgroup><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Samba-2.2 Coding System</th><th align="center">Samba-3 unix charset</th></tr></thead><tbody><tr><td align="center">SJIS</td><td align="center">Shift_JIS series</td></tr><tr><td align="center">EUC</td><td align="center">EUC-JP series</td></tr><tr><td align="center">EUC3<sup>[<a name="id433757" href="#ftn.id433757" class="footnote">a</a>]</sup></td><td align="center">EUC-JP series</td></tr><tr><td align="center">CAP</td><td align="center">Shift_JIS series + VFS</td></tr><tr><td align="center">HEX</td><td align="center">currently none</td></tr><tr><td align="center">UTF8</td><td align="center">UTF-8</td></tr><tr><td align="center">UTF8-Mac<sup>[<a name="id433788" href="#ftn.id433788" class="footnote">b</a>]</sup></td><td align="center">currently none</td></tr><tr><td align="center">others</td><td align="center">none</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id433757" href="#id433757" class="para">a</a>] </sup>Only exists in Japanese Samba version</p></div><div class="footnote"><p><sup>[<a name="ftn.id433788" href="#id433788" class="para">b</a>] </sup>Only exists in Japanese Samba version</p></div></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id433807"></a>Common Errors</h2></div></div></div><div class="sect2" title="CP850.so Can't Be Found"><div class="titlepage"><div><div><h3 class="title"><a name="id433812"></a>CP850.so Can't Be Found</h3></div></div></div><p><span class="quote">“<span class="quote">Samba is complaining about a missing <code class="filename">CP850.so</code> file.</span>”</span></p><p> CP850 is the default <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a>. The <a class="link" href="smb.conf.5.html#DOSCHARSET" target="_top">dos charset</a> 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> |