Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#6052 - Nautilus display wrong filenames when browsing smb://
Attached to Project:
Arch Linux
Opened by Roman Kyrylych (Romashka) - Thursday, 21 December 2006, 21:49 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 15 December 2007, 12:48 GMT
Opened by Roman Kyrylych (Romashka) - Thursday, 21 December 2006, 21:49 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 15 December 2007, 12:48 GMT
|
DetailsIt seems that gnome-vfs doesn't honour system locale when browsing Windows shares.
When using Nautilus to browse Windows shares it doesn't show filenames with non-Latin chars properly on systems with non-UTF8 locale and non-UTF8 "unix charset" and "display charset" options in smb.conf. For example, I use KOI8-U locale and have the following lines in smb.conf: [global] . . . dos charset = 866 unix charset = KOI8-U display charset = KOI8-U When browsing shares with Cyrillic names in Nautilus I see "???? ??? ???????? (invalid unicode)" as file/dir names with Cyrillic chars. This is mainstream bug mentioned there:gnome-vfs-list@gnome.org/msg00946.html"> http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00946.html There: https://bugzilla.altlinux.org/show_bug.cgi?id=4685 is another description (in Russian) with few proposed workarounds, but none of them works. The only way to make Nautilus show filenames properly is to remove "unix charset" and "display charset" options, but then they will be displayed wrong in other places that don't use gnome-vfs. Note: though it's mainstream problem maybe it will be possible to fix this or adopt some workaround. If no, then feel free to close it with "Won't Fix". |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 15 December 2007, 12:48 GMT
Reason for closing: Won't fix
Saturday, 15 December 2007, 12:48 GMT
Reason for closing: Won't fix
So it's "Won't fix".