I've been bugged by this issue since 3.0.0beta1 (the 1st samba 3.0-dev version
the issue blocks me from viewing files & directories that contain files - with
Hebrew letters (although it let me view directories with Hebrew letters in their
names - but as a single "square" character yet)
i don't know whatever if it is a config. issue, or a samba 3.0-dev bug - i'm
really clueless here.
here's my configuration file's content (partly made via swat, partly handily) :
# Global parameters
dos charset = CP862
workgroup = -
server string = NT Workstation 5.0
interfaces = 10.0.0.1
bind interfaces only = Yes
ldap ssl = no
hosts allow = 10.0.0.
unix extensions = Yes
admin users = root
# Sharing parameters
comment = Mounted Filesystems at ZMan
path = /mnt/
profile acls = Yes
comment = HP DeskJet 890c at ZMan
path = /var/spool/cups/tmp
printer admin = root
max print jobs = 50
printable = Yes
printing = cups
comment = LAN Sandbox at ZMan
path = /mnt/120gb_part1/temp/_Sandbox.LAN
read only = No
profile acls = Yes
Thanks for Opening windos to a Wider World ! :)
Created attachment 50 [details]
Hebrew Files in Directory (see the Error Msg.) & Hebrew Directory (seen as a "square")
Created attachment 51 [details]
Same Issue, Different Directory...
(just to Show that there's no specific problem with the (Hebrew-Music)
moving to extended character component
What did you use as your 'unix charset' option setting?
I do not see it set to something in provided config file.
Could you please make an Ethereal (www.ethereal.com) trace of the session and
attach it to the bug report?
how are the files encoded on the samba server? If you never set the
"character set" variable, the files on the server are in the clients
codepage encoded, e.g. CP862. Samba3 per default maps to UTF-8 filenames
which is the best way to do on a Unix system. You either have to set
the "unix charset" variable (IIRC) to the cp you use or convert the
files from your codepage you used to utf-8. Check out
http://j3e.de/linux/convmv/ for a tool to convert the filenames.
this configuration line've solved my problem totally :
unix charset = ISO8859-8
thanks for the fast response ! :}
(please close the bug as fixed, bugzilla don't allow me to do it myself...)
Fixed by proper configuration of smb.conf
originally reported against 3.0.0beta2. CLeaning out
non-production release versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.