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 592313 - Default label names untranslated
Default label names untranslated
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Milan Crha
Evolution QA team
: 616408 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-19 10:35 UTC by Seán de Búrca
Modified: 2010-04-22 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed evo patch (607 bytes, patch)
2009-10-06 12:32 UTC, Milan Crha
committed Details | Review

Description Seán de Búrca 2009-08-19 10:35:58 UTC
The dropdown Show: menu in the mail screen shows the default label names untranslated. The same default label names are correctly translated in the Label context menu. The culprit appears to be the inclusion of the default label names (data sensitive to localization) as a default in the gconf schema. I would be willing to attempt a patch, but I'm unsure of the correct solution. A better solution might be an empty default in the schema and having the application set the key on first run. Opinions would be much appreciated.
Comment 2 Milan Crha 2009-10-06 12:32:07 UTC
Created attachment 144879 [details] [review]
proposed evo patch

for evolution;

This makes it for labels.

The problem is with categories. As categories are just texts separated by commas in components, the translation makes it quite hard to work properly in multiple languages.
Comment 3 Matthew Barnes 2009-10-07 01:13:00 UTC
Looks okay to me.
Comment 4 Milan Crha 2009-10-07 07:51:36 UTC
Created commit fc01347 in evo gnome-2-28 (2.28.1+)

Please open a separate bug for categories, as it'll need more thinking. If you'll have a suggestion, then even better.
Comment 5 Akhil Laddha 2010-04-22 03:58:12 UTC
looks like patch hasn't fixed the problem properly, see bug 616408
Comment 6 Milan Crha 2010-04-22 10:40:34 UTC
*** Bug 616408 has been marked as a duplicate of this bug. ***