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 261084 - "match-all" and "match-threads" in evolution camel needs translator comments
"match-all" and "match-threads" in evolution camel needs translator comments
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
1.4.x (obsolete)
Other All
: Normal normal
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 236276
 
 
Reported: 2004-07-02 15:03 UTC by Christian Rose
Modified: 2007-08-27 09:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
fixed using g_strdup_printf (3.08 KB, patch)
2007-07-29 04:58 UTC, Jared Moore
committed Details | Review
trivial fix (527 bytes, patch)
2007-08-18 01:00 UTC, Jared Moore
committed Details | Review

Description Christian Rose 2004-07-02 15:03:46 UTC
#: camel/camel-folder-search.c:672 camel/camel-folder-search.c:705
msgid "(match-all) requires a single bool result"

#: camel/camel-folder-search.c:755
msgid "(match-threads) not allowed inside match-all"

#: camel/camel-folder-search.c:758 camel/camel-folder-search.c:762
msgid "(match-threads) requires a match type string"

#: camel/camel-folder-search.c:784
msgid "(match-threads) expects an array result"

#: camel/camel-folder-search.c:790
msgid "(match-threads) requires the folder set"

These messages probably need translator comments (see
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#use-comments)
to explain what match-threads and match-all is and whether they should be
translated or not.
Comment 1 Christian Rose 2004-12-29 23:03:44 UTC
Status?
Comment 2 Jeffrey Stedfast 2005-02-04 20:28:05 UTC
the text inside ()'s is not for translation, it is the function name
used in the filter scripting language
Comment 3 Christian Rose 2005-02-06 22:20:47 UTC
Then please replace the function name with an %s in these messages in
a printf*-like approach, in order to make the messages generic.

Having function names hard coded in messages marked for translation is
bad for multiple reasons:
1) Only stuff that should actually be translated should be marked for
translation. Stuff that shouldn't be translated but still is marked
for translation only complicates things for translators.
2) Having stuff that shouldn't be translated hard coded into
translateable messages is not good design, since if these function
names change or other functions need to output similar messages all
translations will need updating, whereas with a printf-based approach
this would not be the case.
3) Having stuff that shouldn't be translated in messages marked for
translation unnecessarily introdocuces another significant possibility
for errors, in that translators may actually "translate" the function
names, or put other typos in by accident.

With "stuff that shouldn't be translated" is often meant all names
that never change, such as function names, file names etc.
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#generic

In addition, please provide translator comments for these messages, so
that translators will know that this is function names (or, if the
printf*-style solution is used, that the %s gets replaced with a
function name):
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#use-comments
Comment 4 André Klapper 2005-03-23 17:49:27 UTC
retargetting the string translation bugs that were targetted to 2.1 to
2.3. for an entire list see bug 236276.
Comment 5 André Klapper 2005-09-16 04:18:03 UTC
camel was moved to eds; still correct in e-d-s-1.4
Comment 6 Jared Moore 2007-07-29 04:58:07 UTC
Created attachment 92631 [details] [review]
fixed using g_strdup_printf
Comment 7 Srinivasa Ragavan 2007-08-02 10:05:41 UTC
Jared, looks fine to commit. Please announce to the i18n list, while committing the patch.
Comment 8 Jared Moore 2007-08-02 11:04:21 UTC
Thanks - I thought it might be nice to get this old bug out of the way. String change has been announced. Unfortunately, I don't have commit access, somebody else will have to do that. :)
Comment 9 Johnny Jacob 2007-08-11 21:19:09 UTC
Committed revision 7937.
Comment 10 Jared Moore 2007-08-12 09:31:09 UTC
Thank you :)
Comment 11 André Klapper 2007-08-17 13:11:57 UTC
hmm. a translator comment for "(%s) not allowed inside match-all" would be nice (to not translate "match all", but anyway. better now. :-)
Comment 12 Jared Moore 2007-08-18 01:00:36 UTC
Created attachment 93879 [details] [review]
trivial fix

Good point, I didn't notice that. Anyway here is a fix (using g_strdup_printf rather than a translator comment seems to me like the better solution here). :)
Comment 13 Johnny Jacob 2007-08-27 06:25:26 UTC
cimmtted to trunk rev 7994. Thanks.
Comment 14 Jared Moore 2007-08-27 09:22:54 UTC
Great, thanks :)