Ralf Christmann
1999-Apr-30 06:47 UTC
german umlaute win95 client vs. Linux-Samba file server
Hello, I've a problem known especially to german speaking users (and other nationalities using special characters). I'm using Samba 1.9.18 and a linux 2.0.35 kernel I want to create a directory or file with a name containing german umlaute from the win95 client so that I can see it on the linux machine with the equal characters I've used under win95. On the win95 machine the new added file (or directory) with this special characters seems to be good, but when I'm looking on the linux machine I've file or dir names with questionmarks instead of the special characters??? I know about valid chars, character set and client code page. I've tried a lot but nothing seems to help. I've also tried a solution with validchr.exe program under dos like it is proposed in the docs from tino@augburg... Also I've changed export LC_ALL=de_DE in the bash. But no success. Did somebody (especially users from switzerland or germany) get rid of the problem. Or could somebody else help? Thanks a lot. Ralf
Giulio Orsero
1999-Apr-30 08:51 UTC
german umlaute win95 client vs. Linux-Samba file server
On Fri, 30 Apr 1999 17:10:03 +1000, hai scritto:>On the win95 machine the new added file (or directory) with this special >characters seems to be good, but when I'm looking >on the linux machine I've file or dir names with questionmarks instead of >the special characters???I have the same problem. I think this is linux related and not samba. $ echo ciao > aaa??? $ ls aaa* aaa??? -- Giulio giuliox@tin.it
Steve Langasek
1999-Apr-30 15:41 UTC
german umlaute win95 client vs. Linux-Samba file server
On Fri, 30 Apr 1999 Ralf Christmann wrote:> I've a problem known especially to german speaking users (and other > nationalities using special characters). > I'm using Samba 1.9.18 and a linux 2.0.35 kernel > I want to create a directory or file with a name containing german umlaute > from the win95 client > so that I can see it on the linux machine with the equal characters I've > used under win95. > On the win95 machine the new added file (or directory) with this special > characters seems to be good, but when I'm looking > on the linux machine I've file or dir names with questionmarks instead of > the special characters???> I know about valid chars, character set and client code page. I've tried a > lot but nothing seems to help. > I've also tried a solution with validchr.exe program under dos like it is > proposed in the docs from tino@augburg... > Also I've changed export LC_ALL=de_DE in the bash. But no success. > Did somebody (especially users from switzerland or germany) get rid of the > problem. > Or could somebody else help?This is a problem on the Linux end. This is usually covered in the Linux national language HOWTOs, but for some reason the German HOWTO doesn't mention 'ls'. To get 'ls' to display the characters correctly, you should pass it the -N option: $ touch bl?e $ ls bl?e bl?e $ls -N bl?e bl?e There is a lot besides 'export LC_ALL=de_DE' involved in properly internationalizing a Linux system, and I recommend reading the German HOWTO, if you haven't already done so. -Steve Langasek postmodern programmer
On Fri, 30 Apr 1999, Giulio Orsero wrote:>> On Fri, 30 Apr 1999 17:10:03 +1000, hai scritto: >> >> >On the win95 machine the new added file (or directory) with thisspecial>> >characters seems to be good, but when I'm looking >> >on the linux machine I've file or dir names with questionmarks insteadof>> >the special characters??? >> >> I have the same problem. I think this is linux related and not samba. >> >> $ echo ciao > aaa??? >> $ ls aaa* >> aaa??? >> > >I believe this is smbfs related. >smbclient shows (correctly): > ???-sql.txt A 759 Tue Apr 6 16:25:44 1999 >/bin/ls on the same share mounted as smbfs shows: >???-sql.txt > >But on a different filesystem (ext2): >cola:~>touch ??? >cola:~>/bin/ls ??? >??? > >This is with 2.2.6/2.0.3. I haven't looked at all at options to smbfs >(or smbmount) it is possible that there is something there that can help.There is a good chance that your ls is by default using the -q option, which shows ? instead of 8-bit characters. I believe there is an option to ls to display the filename in their original form, but that option escapes me right now. Andy.
Ralf Christmann
1999-May-05 16:04 UTC
german umlaute win95 client vs. Linux-Samba file server
First of all thanks a lot for the discussion of the people which made some suggestions . Urban last wrote:>/bin/ls -b on the share gives: >\206\204\224-sql.txt > >While ls on the ext2 still gives >cola:~>/bin/ls -b ??? >??? > >LC_CTYPE is set to sv_SE, so ??? isprint() (I think?). Clearing LC_CTYPE, >gives: >cola:~>/bin/ls -b ??? >\345\344\366 > >Which is different from the above. There seems to be a need to make some >kind of translation of filenames (\206 -> \345 ?) For smbclient this is >done by these settings: > character set = iso8859-1 > client code page = 850 > >The above settings also make shares from a linux box handle ??? in >filenames with a NT client (both files created on the server and from the >client). I think this is an answer to the original question. Ralf, did you >have these set? > >I still haven't found a way to tell smbmount/mount/smbfs to use a >"codepage". When mounting vfat for example, it takes a codepage=### >option. > >Oh, and /bin/ls -N doesn't help, as someone suggested. I just get black >squares (both xterm and console).You are right, ls -N does only help for those files which where created on the linux side. But this is not the problem! The problem is the translation of files touched by a win95 client to the linux side. On the win95 clients I can not notify that there are problems on the linux server. The clients see the files in the way they created on in the windows box. But when I look at this files on the linux server the strange mistranslation of the filenames is done as I described before. So I set up the parameters character set = iso8859-1 and client code page = 850 But this does not help. I've also tried to give some valid chars parameters without success. I believe that the problem is related to the right settings of valid chars. Do you share my point of view?