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 579769 - combo options are displayed not translated
combo options are displayed not translated
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: [obsolete] GIO
2.26.x
Other Linux
: Normal normal
: 2.28.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 580136 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-21 20:27 UTC by Sebastien Bacher
Modified: 2009-04-30 10:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Mark strings as translatable (6.64 KB, patch)
2009-04-29 17:21 UTC, Gabor Kelemen 		committed Details | Review

Description Sebastien Bacher 2009-04-21 20:27:37 UTC 
the bug has been opened on https://bugs.launchpad.net/bugs/364577

"I'm using ubuntu with french locale but preference dialog in nautilus is in english since upgrade in 9.04.
you can't found an image illustrating this minor 'bug'.

http://launchpadlibrarian.net/25819171/Capture-Pr%C3%A9f%C3%A9rences%20du%20gestionnaire%20de%20fichiers.png"
Comment 1 Sebastien Bacher 2009-04-21 20:28:10 UTC 
The combo values in the preferences dialog are not displayed translated in GNOME 2.26
Comment 2 André Klapper 2009-04-29 14:49:39 UTC 
*** Bug 580136 has been marked as a duplicate of this bug. ***
Comment 3 Gabor Kelemen 2009-04-29 17:21:57 UTC 
Created attachment 133581 [details] [review]
Mark strings as translatable

Glade3 seems not to support marking these strings as translatable :(. This solved the problem for me.
Comment 4 Cosimo Cecchi 2009-04-29 18:16:13 UTC 
If it really solves the issue, please commit to master.
Comment 5 Gabor Kelemen 2009-04-30 09:58:09 UTC 
How about the gnome-2-26 branch? These should IMHO fixed there too.
Comment 6 Cosimo Cecchi 2009-04-30 10:07:52 UTC 
Yes, I cherry-picked the commit to the gnome-2-26 branch and sent a mail to gnome-i18n explaining the issue. Thanks.