| 7 | ---- |
| 8 | === Samba Codepage support seems to be broken from 3.0.35 onward - why does this not work anymore? === |
| 9 | Older Samba Server releases had the codepage settings hardwired to SYSTEM and later releases to IBM-850. This turned out to be the culprit for various problems regarding codepages with the Client. |
| 10 | Therefore this was changed to a dynamic code page detection with changeset [http://svn.netlabs.org/samba/changeset/307 307 for 3.0.x] and [http://svn.netlabs.org/samba/changeset/308 308 for 3.3.x]. |
| 11 | |
| 12 | However, while this solved the problems with the client, it turned out to be problematic on the server. |
| 13 | |
| 14 | So the advice is to set the following settings manually in smb.conf: |
| 15 | |
| 16 | {{{ |
| 17 | [global] |
| 18 | ... |
| 19 | dos charset = ASCII |
| 20 | unix charset = UTF-8 |
| 21 | display charset = UTF-8 |
| 22 | ... |
| 23 | }}} |
| 24 | |
| 25 | The following codepage values have been tested with the following results: |
| 26 | || UTF-8 || works completely || |
| 27 | || IBM-850 || works completely || |
| 28 | || IBM-437 || works partly, 82 out of 128 characters work, 44 mismatches, 2 cannot be written || |
| 29 | || UTF-16 || crashes Samba, do not try that || |
| 30 | || IBM-863 || not tested, but we'd like to get results || |
| 31 | || IBM-866 || not tested, but we'd like to get results || |
| 32 | |
| 33 | General advice: Enter UTF-8, even if your system is running on other codepages, this will most likely give you the best results. On systems running on IBM-850 no change is required). |
| 34 | |
| 35 | ''Note: Characters below 128 work on any codepage. Issues are only seen when using characters between 128 and 255 in file and directory names.''[[BR]] |
| 36 | ''Note: Recent sscc.exe knows these issues and provides appropriate additions to smb.conf.'' |