GNOME Bugzilla – Bug 261062
Strange messages marked for translation in evolution addressbook
Last modified: 2010-04-01 16:39:29 UTC
#: addressbook/addressbook-errors.xml.h:22 #: addressbook/addressbook-errors.xml.h:26 #: addressbook/addressbook-errors.xml.h:34 #: addressbook/addressbook-errors.xml.h:38 msgid "{0}" #: addressbook/addressbook-errors.xml.h:28 #: composer/mail-composer-errors.xml.h:4 msgid "{1}" It seems strange that these messages are marked for translation. At the very least, there should be a translator comment (http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#use-comments) explaining how these "strings" are used and what they should be translated into.
This is also the case for these messages: #: addressbook/gui/component/GNOME_Evolution_Addressbook.server.in.in.h:1 msgid "*Control*F2" #: calendar/gui/GNOME_Evolution_Calendar.server.in.in.h:1 msgid "*Control*F3" #: calendar/gui/GNOME_Evolution_Calendar.server.in.in.h:2 msgid "*Control*F4"
String freeze, will wait untill 2.1
Jeff, what's the status on the comment addition?
{0} and {1} are strings that are inserted. I'll leave this to notzed to determine how to make sure these aren't marked for translation. As for the others, that appears to be fixed now.
retargetting the string translation bugs that were targetted to 2.1 to 2.3. for an entire list see bug 236276.
punting to 2.5 due to string freeze; adding "string" keyword
addressbook aint nothing to do with me. the e-error readme explains how strings are or aren't marked for translation.
removing old target milestone. devashish: another string bug in address book, cc'ing you.
Created attachment 72961 [details] [review] The patch handles all translation issues except mentioned in comment #1
Commited the patch.
comment #1 seems solved by now (svn head), guess we can close this bug.
cough... srini? "It seems strange that these messages are **marked for translation**." i'd prefer to have these strings removed from the po files instead of having a translator comment by ushveen, as already committed. :-/ imho, the comments are not helpful for translators.
I think _primary/primary _secondary/secondary should be the way to go head. First should be translated and the second shouldn't be. Im not sure, if that is the way it is implemented.
Bumping version to a stable release.
Created commit 816614e in evo master (2.31.1+)