GNOME Bugzilla – Bug 655997
Unneeded context specifiers
Last modified: 2013-09-14 16:54:13 UTC
In several occurrences, the C_ macro is used with no apparent advantage for the translators. For example: case E_BOOK_CLIENT_ERROR_NO_SUCH_BOOK: return C_("BookClientError", "No such book"); case E_BOOK_CLIENT_ERROR_CONTACT_NOT_FOUND: return C_("BookClientError", "Contact not found"); The problem is that for each different context, translators have to translate the same string again. The C_ macro is only useful when a string might be translated differently depending on the context. But seldom for error messages... I might provide a patch to remove those I think not useful for translators.
I know it's more work for translators, but I thought it's better to tag them with a context, just to make sure, if any similar text will be added in the future, this will not "break things". I was adding contexts here and there recently, on strings which I thought doesn't worth it, but it did worth. Thus this decision with errors.
I understand your approach, but as for me I think it's better to add context when you are really confronted with a string "clash". One case where I find it totally appropriate is C_("Priority", "High"), that is a short word that has all chances to be used elsewhere with a different meaning. But with strings such as "Object not found", "Unknown user", etc. I don't really see how the context may change a translation.
I agree with Claude. Context is used to disambiguate otherwise identical messages.
OK, I'll remove those contexts.
Created commit 0e44c90 in eds master (3.1.90+)
Fine, thanks!