| 1 |
Hello Holger, |
| 2 |
|
| 3 |
2008/4/26 Holger Hoffstaette <holger@×××××××.de>: |
| 4 |
> Do you happen to know if this is solved in recent versions? |
| 5 |
|
| 6 |
UTF-8 and US-ASCII are the only supported charsets since CUPS 1.3.3. |
| 7 |
There's some info about this in the Upstream bug: |
| 8 |
http://www.cups.org/str.php?L2537 |
| 9 |
|
| 10 |
Comment #17 of the Samba bug you posted seems to mention it'll get |
| 11 |
fixed over there for Samba 3.2.0/3.2.1: |
| 12 |
https://bugzilla.samba.org/show_bug.cgi?id=5080#c17 |
| 13 |
|
| 14 |
> My understanding is that changing samba's "unix charset" to something |
| 15 |
> else would fix this, but that is not feasible for me at this point. |
| 16 |
> If there is any other way I'd love to hear about it. :) |
| 17 |
|
| 18 |
I'd consider this rather a Samba problem since it probably won't get |
| 19 |
fixed or worked around on the CUPS side. But out of interest, any |
| 20 |
reason to not convert all your files with convmv to UTF-8 and set in |
| 21 |
smb.conf for example: |
| 22 |
|
| 23 |
[global] |
| 24 |
dos charset = 850 |
| 25 |
unix charset = UTF-8 |
| 26 |
|
| 27 |
which should get rid of this issue as well (according to the Samba bug |
| 28 |
comments) and displays the files correctly for Microsoft Windows |
| 29 |
clients, too. |
| 30 |
|
| 31 |
Regards |
| 32 |
Timo Gurr |
| 33 |
-- |
| 34 |
gentoo-dev@l.g.o mailing list |
Archives