[gutsy][samba][k3b]encodings-and-untransleted-gui

[Andrey Zhekov]

Try to consider and implement specific options after installing language-packs, i.e. proper encodings in /etc/fstab for CD-ROM (DVD) dirves, network workstations names and shares names (especialy in NT network envioriments).

1) add iocharset=UTF8 option for mounting dvdrom,cdrom-drives in /etc/fstab
2) to Samba config file I added in [General] section (Russian specific options):
dos charset = cp866
unix charset = UTF8
display charset = UTF8
character set = UTF8
client code page = 866
default case = upper
preserve case = yes
short preserve case = yes

... to prevent the "????"signs apearing in the "Network" when native-language letters are used for naming the computers or share names.

3) to make k3b menus "speaking" in native (not English) language in Ubuntu I have to install the kde-i18n-ru packages not only the k3b-i18n one. The bad thing, that when selecting k3b installation, the kde-i18n package is not automaticaly installed and there isn't any info or dependancy in Synaptic to make russian GUI in k3b.
I know, that is difficult to put in to 1 CD all the i18n for KDE, but when we have a DVD disk or even a pool in the local network that option must work properly.

[François Marier (fmarier)]

Someone has suggested the same thing on for the K3b package on the Debian bug tracker:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361246

[Jonathan Davies (jpds)]

All the k3b translations are in the language-packs, please install the right one for i18ns.

[Steve Langasek (vorlon)]

Thank you for taking the time to report this issue and help to improve Ubuntu.

Breaking down your suggested changes to smb.conf:

 unix charset = UTF8
 display charset = UTF8

These should be equivalent to the defaults, there is no need to set them.

 character set = UTF8
 client code page = 866

These are not valid options with current samba.

 default case = upper
 preserve case = yes
 short preserve case = yes

These don't seem to have anything to do with filename encoding, why do you need to set them? (The last two are also the same as the built-in defaults.)

 dos charset = cp866

This is the last remaining change, and the one that directly affects the character set used for displaying filenames to the client.

It's true that the default 'dos charset' value is only correct for Western European languages. On the other hand, the dos charset setting is only used when communicating with non-Unicode clients; clients from NT4 and above (which includes Windows 2000, Windows XP, and Windows Vista) are handled natively using Unicode. So I don't think the impact of this issue is very large; on the other hand, mapping all of our available installation locales to the (unrelated) set of DOS codepages would be a lot of work. While I'm not marking this as "wontfix" now, I think that's probably what will happen with it.

[Greg Grossmeier (greg.grossmeier)]

Unassigning Andrej as there is no work being done to fix this issue.

[Chuck Short (zulcss)]

Marking as wont-fixed since gutsy is no longer supported, can you please re-test with karmic or lucid.