On 6/8/06, Andre Klapper <[EMAIL PROTECTED]> wrote:
i have no idea if i have to announce this - guess not - anyway, better to write a redundant email just to be on the safe side. ;-)
Yes, thanks for doing so. It's better to be on the safe side. And yes, your suspicions were right, this does not actually have anything to do with string freeze, but it's good to know.
some messages are now translated in the gnome-2-14 branch that were previously not translated by accident (an incorrect gettext domain for translations was used): http://cvs.gnome.org/viewcvs/evolution/e-util/e-i18n.h?r1=1.11&r2=1.11.20.1 this fixes http://bugzilla.gnome.org/show_bug.cgi?id=333003 . however, if i understand everything right, this does not affect the translators, because those strings were already part of the po files before and should be already translated.
Yes, xgettext should already have fetched those messages if they were properly marked and included in POTFILES.in, so they should already be translated in the po files. A domain mismatch problem would only affect the runtime result, i.e. the translations not being actually used. However, this being fixed means a lot to translators. There's nothing more frustrating than when you know you have translated something in the UI, and it still doesn't show up. Thanks a lot for fixing/reporting this! Christian _______________________________________________ gnome-i18n mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-i18n
