Hello,
I am new to this list. I have (and all Trukish users of Samba) trouble with
Turkish charactes (iso8859-9)with Samba. I saw some character definition tables
in charcnv.o (in sources). I couldn't understand the logic. A part of the
table
for iso8859-2 is
/* MSDOS Code Page 852 -> ISO-8859-2 */
update_map("\241\244\242\364\243\235\244\317\245\225\246\227\247\365");
update_map("\250\371\251\346\252\270\253\233\254\215\256\246\257\275");
update_map("\261\245\262\362\263\210\264\357\265\226\266\230\267\363");
What does these number mean? Could anybody expain please? So that I can a
prepare for iso8859-9.
Thanks.
On Tue, 8 Jun 1999, Mustafa BASER wrote:> Hello, > I am new to this list. I have (and all Trukish users of Samba) trouble with > Turkish charactes (iso8859-9)with Samba. I saw some character definition tablesWhat part of samba? (server, smbclient, something else ...)> /* MSDOS Code Page 852 -> ISO-8859-2 */ > update_map("\241\244\242\364\243\235\244\317\245\225\246\227\247\365"); > update_map("\250\371\251\346\252\270\253\233\254\215\256\246\257\275"); > update_map("\261\245\262\362\263\210\264\357\265\226\266\230\267\363"); > > What does these number mean? Could anybody expain please? So that I can a > prepare for iso8859-9.I believe smbclient and smbd use these to convert filenames between codepages. \241 is an octal number \241\244 says that the character with number \241 in cp852, should be replaced by \244 in iso-8859-2 Anything that is the same in both codepages can be left out. smbclient does not translate share names or server comments, so you might get: cola:~>smbclient -L xyz -N ... Server Comment --------- ------- ... FOO B*R ... (where * is a black square for me since it doesn't map onto anything printable) This is probably a bug (or is it not allowed to use such servernames/ sharenames/comments?). If this is your problem then simply adding a codepage is not going to be enough. /Urban
Hello,>I believe smbclient and smbd use these to convert filenames between >codepages. >\241 is an octal number >\241\244 says that the character with number \241 in cp852, should be > replaced by \244 in iso-8859-2I looked at cp857 (Turkish) from microsoft site and saw that location of Turkish characters in cp857 and iso8859-9 are not the same. For example the character 158 (oct 236) in cp857 must be mapped to 222 (oct 336) in iso8859-9. This cahracter is an S with a cedille below. Like Ccedille. So the table should be \336\236 I prepared a table for Turkish characters. The table is \246\320\247\360\236\336\237\376\230\335\215\375 \232\334\201\374\231\326\224\366\200\307\207\347 There are 12 characters to be mapped. I added this table to charcnv.c in the sources. The file I prepared is attached with this mail. I also prepared a codepage.857. I compiled Samba with this new charcnv.c and installed. I set "log level=10" to see if there is something wrong. And the followings in the [global] section in smb.conf character set=iso8859-9 client code page = 857 When I started samba, there is nothing wrong in the log file. Everything seems good. That is it found the charset iso8859-9 and set and also codepage 857.>From windows 95 I try to create folders with Turkish cahracters on a shareddirectory on Samba. Nothing changed. Again Win95 cannot see the newly created directory and in Linux the name of the newly created directory is nonsense. Am I doing the things correct? or missed something. Thanks for your advise.> >Anything that is the same in both codepages can be left out. > > >smbclient does not translate share names or server comments, so you might >get: >cola:~>smbclient -L xyz -N >... > Server Comment > --------- ------- >... > FOO B*R >... > >(where * is a black square for me since it doesn't map onto anything >printable) > >This is probably a bug (or is it not allowed to use such servernames/ >sharenames/comments?). If this is your problem then simply adding a >codepage is not going to be enough. > >/Urban