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 324094 - Untranslatable strings in calendar tooltips
Untranslatable strings in calendar tooltips
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: Srinivasa Ragavan
Evolution QA team
Depends on:
Blocks: 236276
 
 
Reported: 2005-12-14 17:40 UTC by David Richards
Modified: 2013-09-13 00:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Richards 2005-12-14 17:40:54 UTC
Looks like "Organiser" is hard coded into Evolution for when you do a mouse over
on calendar events.  US Spelling is "Organizer".  I would assume this area
should have translations for all languages.

Other information:
Comment 1 André Klapper 2005-12-14 19:47:53 UTC
this is
http://cvs.gnome.org/viewcvs/evolution/calendar/gui/e-calendar-view.c?r1=1.97&r2=1.98
perhaps?

assigning to srag. good evening.

srag, any idea about I18N and that funny "_" to translate strings? sigh...
"please also take care about the other strings in there as well". (it's
frustrating enough that imo it's necessary to even mention this.)

<rant>
damn, why am i doing this here voluntarily?
we should really discuss the term "code quality", i'm pretty pissed with it
currently. it all seems to me like "fixing one bug and creating two new ones for
it".
srag, read the HIG, read the I18N guidelines, and remember them.
it can't be *that* hard.
</rant>
Comment 2 Srinivasa Ragavan 2005-12-15 02:42:27 UTC
Oops, committed a wrong portion of code. Will get this in asap.
Comment 3 Srinivasa Ragavan 2005-12-15 06:50:56 UTC
Fix committed to head.
Comment 4 André Klapper 2005-12-15 10:24:32 UTC
translating
      str = icalcomponent_get_summary (pevent->comp_data->icalcomp);
      tmp = g_strdup_printf (_("<b>%s</b>"), str);
makes no sense at all, please make it untranslatable again. and do NOT include
markup in translations - there are be more than a dozen bugs about this in
bugzilla and this would be one more.

_("Organizer: %s <%s>" needs translator comments, so the translators know that
the first %s is the name and the second one is the email address.
it's just not easy for the translators to find that out. and other languages,
other word positionings (i can pretty well imagine that "organiser" is NOT at
the beginning of all languages of the world, so the entire meaning *must* be
understandable by the translators in the po files).
same with "Time: %s %s". as a translator i have *no* idea at all what this
means. i *must* take a look into the source to understand, and that's totally
unacceptable.


reopening. perhaps i'm nitpicking, but i expect new bug reports about this if
this would not be fixed.
Comment 5 André Klapper 2005-12-15 11:09:42 UTC
keeping it in the current state would produce *three* new bug reports, to just
underline my rant in comment 1. :-)

and for the records:
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#avoid-markup
Comment 6 Srinivasa Ragavan 2005-12-15 12:41:40 UTC
But, 

About the markup it is fine. But im not sure about how to help translators
understand that. May be we will keep it open. Ill get the other thing in cvs asap.

Btw, thanks andre for pointing me out.
Comment 7 Srinivasa Ragavan 2005-12-15 12:51:07 UTC
Andre, 

I have committed a fix for this, as well as i have added a note to the top of
the   function, saying that how this will be displayed. Is there a special
keyword that gets the translators attention while translation, i can do that as
well.
Comment 8 André Klapper 2005-12-15 13:03:05 UTC
srag: use translator comments. see
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#use-comments

it's easy, just put a comment at the line directly above the string that has to
be translated.
Comment 9 André Klapper 2005-12-15 13:05:48 UTC
srag: adding a comment at the top of the function does not work. the comment has
to be directly above the string that has to be translated, otherwise it won't be
part of the po file. we cannot expect translators to take a look into the codebase.

also see my link above. :-)
Comment 10 Srinivasa Ragavan 2005-12-17 11:54:38 UTC
Commited to head. Thanx andre