2008/4/26 Holger Hoffstaette <email@example.com>:
> Do you happen to know if this is solved in recent versions?
UTF-8 and US-ASCII are the only supported charsets since CUPS 1.3.3.
There's some info about this in the Upstream bug:
Comment #17 of the Samba bug you posted seems to mention it'll get
fixed over there for Samba 3.2.0/3.2.1:
> My understanding is that changing samba's "unix charset" to something
> else would fix this, but that is not feasible for me at this point.
> If there is any other way I'd love to hear about it.
I'd consider this rather a Samba problem since it probably won't get
fixed or worked around on the CUPS side. But out of interest, any
reason to not convert all your files with convmv to UTF-8 and set in
smb.conf for example:
dos charset = 850
unix charset = UTF-8
which should get rid of this issue as well (according to the Samba bug
comments) and displays the files correctly for Microsoft Windows
firstname.lastname@example.org mailing list