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 516823 - Governor names are not localized in the cpufreq-applet
Governor names are not localized in the cpufreq-applet
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.21.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-16 11:13 UTC by Gabor Kelemen
Modified: 2013-02-11 22:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Screenshot with unlocalized governors (16.90 KB, image/png)
2008-02-16 11:14 UTC, Gabor Kelemen 		Details

Description Gabor Kelemen 2008-02-16 11:13:20 UTC 
The cpufreq applet gets the available governor names from /sys and shows them to users unlocalized.
Comment 1 Gabor Kelemen 2008-02-16 11:14:30 UTC 
Created attachment 105373 [details]
Screenshot with unlocalized governors
Comment 2 André Klapper 2010-04-08 00:35:51 UTC 
And how should this be fixed?
Comment 3 Tobias Mueller 2010-05-24 13:38:54 UTC 
Well. Technically, I guess one needs to have kind of a translation table, i.e. if if g_strcmp(msg, "Performance") governor = _("Performance");

And I'd translate the to "Performanz" or so in the German case. But I guess that's up to the translation teams.
Comment 4 nodiscc 2013-02-11 22:23:16 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.