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 236142 - Don't use acronyms as verbs in messages (camel-gpg-context.c)
Don't use acronyms as verbs in messages (camel-gpg-context.c)
Status: RESOLVED DUPLICATE of bug 238791
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 261982 (view as bug list)
Depends on:
Blocks: 236276
 
 
Reported: 2002-12-28 12:41 UTC by Christian Rose
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to solve this (at least the gpg stuff) (1.53 KB, patch)
2005-01-24 18:57 UTC, Jorge Bernal "Koke" 		none Details | Review

Description Christian Rose 2002-12-28 12:41:15 UTC 
#: camel/camel-gpg-context.c:1122
#, c-format
msgid ""
"Failed to GPG %s: %s\n"
"\n"
"%.*s"

#: camel/camel-gpg-context.c:1128
#, c-format
msgid "Failed to GPG %s: %s\n"


Please don't use acronyms as verbs in messages. Besides being bad English
it's usually also difficult or impossible to translate correctly, since
making verbs out of acronyms can be difficult or impossible in other languages.

Please use "Failed to GPG encrypt %s" or "Failed to encrypt %s with GPG" or
something similar instead of "Failed to GPG %s".
Comment 1 André Klapper 2004-05-12 10:25:51 UTC 
still there in revision 1.52 of camel/camel-gpg-context.c. could be an
easy_fix...
Comment 2 André Klapper 2004-12-15 16:03:13 UTC 
*** bug 261982 has been marked as a duplicate of this bug. ***
Comment 3 Jorge Bernal "Koke" 2005-01-24 18:57:17 UTC 
Created attachment 44650 [details] [review]
Patch to solve this (at least the gpg stuff)
Comment 4 Not Zed 2005-02-01 06:50:46 UTC 
Jorge, sorry but i wont use this patch now - after looking at the code
for fixing another bug, i found that this case is only ever used for
i/o errors.

Also, there are many other errors for which this specific 'i was doing
this at the time' error is not used either.

So to simplify the whole thing and fix the inconsistencies, i just
removed it and it just does a 'failed to execute gpg: strerror()' now.

(marking as duplicate of the other bug, even though it isn't a
duplicate, but the other bugs patch 'fixes' the problem).


*** This bug has been marked as a duplicate of 238791 ***