After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 144810 - translate the gconf:gnome-terminal/global/active_encodings to allow different default encoding menus
translate the gconf:gnome-terminal/global/active_encodings to allow different...
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-22 12:42 UTC by Mariano Suárez-Alvarez
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mariano Suárez-Alvarez 2004-06-22 12:42:03 UTC 
For example, as pointed by Takao Fujiwara on bug 138630, in the japanese
translation one could have

msgid "[UTF-8,current]"
msgstr "[UTF-8,EUC-JP,SHIFT-JIS,ISO2022JP,current]"

which is very reasonable.

Now, it seems that one cannot include comments for translators in .schema.in
files, and they should really be aware of the fact that they cannot add whatever
in this list, only valid encoding names, and that 'current' is -not- to be
translated because it is used to represent the locale encoding...
Comment 1 Havoc Pennington 2004-06-23 17:29:33 UTC 
I don't think gconf supports translating the <default>...
Comment 2 Mariano Suárez-Alvarez 2004-06-23 17:53:39 UTC 
http://developer.gnome.org/doc/API/2.0/gconf/ch06.html says it does.
(I wonder if gconf uses the locale gconf is running with or the app's current
locale?)
Comment 3 Mariano Suárez-Alvarez 2004-06-28 04:23:19 UTC 
It turns out Danilo added comments in .schema.in files a little while ago, so
I've moved the default into the <locale> and added a comment explaining a bit
things.

So this is in HEAD now.