Re: Strings with context wrongly translated in gtk+ and epiphany
Hi, On Thu, 2006-09-14 at 09:20 +0530, Runa B wrote: In case the msgstr is untranslated or fuzzy, doesnt the original msgid string show up on the interface? Hence if these strings are left blank the original msgid i.e. some prefix| would be used in the display, which beats the purpose of leaving out the prefix in the translation in the first place. You are wrong here. The translation context is stripped away before displaying the message. This only works if the translation context is left untranslated. Thus, if you don't translate a message, the original message will be used after stripping away some prefix|. For implementation details, see http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS By the way, quite a few GIMP translations suffer from the same problem that was reported here for gtk+ and epiphany. Sven ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
Sven Neumann wrote: Hi, On Thu, 2006-09-14 at 09:20 +0530, Runa B wrote: In case the msgstr is untranslated or fuzzy, doesnt the original msgid string show up on the interface? Hence if these strings are left blank the original msgid i.e. some prefix| would be used in the display, which beats the purpose of leaving out the prefix in the translation in the first place. You are wrong here. The translation context is stripped away before displaying the message. This only works if the translation context is left untranslated. Thus, if you don't translate a message, the original message will be used after stripping away some prefix|. For implementation details, see http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS Hmm. Makes sense. Thanks Sven and Abel for clarifying the matter. regards Runa ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
Runa B quoth on 14. sep 2006 05:50:
In case the msgstr is untranslated or fuzzy, doesnt the original msgid
string show up on the interface? Hence if these strings are left blank
the original msgid i.e. some prefix| would be used in the display,
which beats the purpose of leaving out the prefix in the translation in
the first place.
Please correct me if I am wrong.
So some context| could be translated to some context| (msgstr ==
msgid) and the problem goes away?
--
Åsmund Skjæveland {
foo();
}
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
On Wed, 13 Sep 2006 02:15:19 +0100, Abel Cheung [EMAIL PROTECTED] wrote: On 9/13/06, Christian Persch [EMAIL PROTECTED] wrote: I noticed there are still some translations for gtk+ and epiphany that incorrectly translate strings with context (this is context|this is the string) to include either the literal context (this is context|) or even translate the context! No, the list of translation files having problem is not restricted to these. I attached a list of files with potential problems -- some of the evolution files might be false positives, but translators would definitely want to check all others. The file is generated against gnome 2.16, that means some belongs to HEAD and others belong to gnome-2-16 branch. Here is the command: Thanks, I've fixed the en_GB issues (except for Evolution, which was a false positive). This does lead to an interesting question though. gok has a selection of strings for extra characters on the keyboard, which may or may not exist, these are given a context. Translation of the first few levels is easy, as this is the normal lower case, upper case, symbols etc., but gok provides two extra levels (with a context) to allow extra characters. For en_GB this means that whence the context is removed the strings are empty. So I'm now getting untranslated strings on gok. (well only one as I added the Euro symbol to level2 :-) Any idea of how these strings should be translated? The strings from the .po file: #. Not used in C locale: this string can contain a third set of characters #. * at another 'shift level'. It can be used to provide a second/alternate #. * glyph/character set for the locale, separately or in conjunction with #. * 'level 3'. At the translator's discretion, accented characters can be #. * placed here and in 'level 3' as well. #. #. #. * Seldom-used or alternate characters can appear in levels 2 and 3 if necessary. #. #: ../gok/gok-keyboard.c:877 ../gok/gok-keyboard.c:933 msgid level 2| msgstr level 2| #. For locales which need an even larger character set, or offer uppercase versions #. * of the 'level2' characters, add them to 'level 3' #: ../gok/gok-keyboard.c:880 ../gok/gok-keyboard.c:934 msgid level 3| msgstr level 3| Thanks dave ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
On 9/13/06, David Lodge [EMAIL PROTECTED] wrote: This does lead to an interesting question though. gok has a selection of strings for extra characters on the keyboard, which may or may not exist, these are given a context. Translation of the first few levels is easy, as this is the normal lower case, upper case, symbols etc., but gok provides two extra levels (with a context) to allow extra characters. For en_GB this means that whence the context is removed the strings are empty. So I'm now getting untranslated strings on gok. (well only one as I added the Euro symbol to level2 :-) Any idea of how these strings should be translated? That depends on how gok handles it. If transating it into anything would adversely affect gok's behavior, I'd suggest not translating it. Abel The strings from the .po file: #. Not used in C locale: this string can contain a third set of characters #. * at another 'shift level'. It can be used to provide a second/alternate #. * glyph/character set for the locale, separately or in conjunction with #. * 'level 3'. At the translator's discretion, accented characters can be #. * placed here and in 'level 3' as well. #. #. #. * Seldom-used or alternate characters can appear in levels 2 and 3 if necessary. #. #: ../gok/gok-keyboard.c:877 ../gok/gok-keyboard.c:933 msgid level 2| msgstr level 2| #. For locales which need an even larger character set, or offer uppercase versions #. * of the 'level2' characters, add them to 'level 3' #: ../gok/gok-keyboard.c:880 ../gok/gok-keyboard.c:934 msgid level 3| msgstr level 3| Thanks dave -- Abel Cheung (GPG Key: 0xC67186FF) Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF * GNOME Hong Kong - http://www.gnome.hk/ * Opensource Application Knowledge Assoc. - http://oaka.org/ * My own cave: http://me.abelcheung.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
På Thu, Sep 14, 2006 at 01:19:42AM +0800, Abel Cheung skrev: On 9/13/06, David Lodge [EMAIL PROTECTED] wrote: This does lead to an interesting question though. gok has a selection of strings for extra characters on the keyboard, which may or may not exist, these are given a context. Translation of the first few levels is easy, as this is the normal lower case, upper case, symbols etc., but gok provides two extra levels (with a context) to allow extra characters. For en_GB this means that whence the context is removed the strings are empty. So I'm now getting untranslated strings on gok. (well only one as I added the Euro symbol to level2 :-) Any idea of how these strings should be translated? That depends on how gok handles it. If transating it into anything would adversely affect gok's behavior, I'd suggest not translating it. When the msgid is some prefix| without an actual string, the translated msgstr becomes if no content is needed (see the translator comments in the gok .po files). Although is correct, this counts as untranslated for msgfmt/intlook/i18n-status, etc. This _is_ a problem. mvrgr, Wouter -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl i'm the girl :: i'm the girl :: you know me -- heather nova signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
Wouter Bolsterlee wrote: På Thu, Sep 14, 2006 at 01:19:42AM +0800, Abel Cheung skrev: On 9/13/06, David Lodge [EMAIL PROTECTED] wrote: snipped So I'm now getting untranslated strings on gok. (well only one as I added the Euro symbol to level2 :-) Any idea of how these strings should be translated? That depends on how gok handles it. If transating it into anything would adversely affect gok's behavior, I'd suggest not translating it. When the msgid is some prefix| without an actual string, the translated msgstr becomes if no content is needed (see the translator comments in the gok .po files). Although is correct, this counts as untranslated for msgfmt/intlook/i18n-status, etc. This _is_ a problem. In case the msgstr is untranslated or fuzzy, doesnt the original msgid string show up on the interface? Hence if these strings are left blank the original msgid i.e. some prefix| would be used in the display, which beats the purpose of leaving out the prefix in the translation in the first place. Please correct me if I am wrong. regards Runa ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
On სამ, 2006-09-12 at 20:52 +0200, Christian Persch wrote: Hi there, I noticed there are still some translations for gtk+ and epiphany that incorrectly translate strings with context (this is context|this is the string) to include either the literal context (this is context|) or even translate the context! The following translations are concerned: Epiphany: dz ,ka ,lv ,mn ,ms ,ta ,uk Gtk+: el, hi, ka, lt, mk, pa, ru, ta Regards, Christian Fixed for Georgian (ka)! Thanks! Vladimer ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings with context wrongly translated in gtk+ and epiphany
On 9/13/06, Christian Persch [EMAIL PROTECTED] wrote: I noticed there are still some translations for gtk+ and epiphany that incorrectly translate strings with context (this is context|this is the string) to include either the literal context (this is context|) or even translate the context! The following translations are concerned: Epiphany: dz ,ka ,lv ,mn ,ms ,ta ,uk Gtk+: el, hi, ka, lt, mk, pa, ru, ta No, the list of translation files having problem is not restricted to these. I attached a list of files with potential problems -- some of the evolution files might be false positives, but translators would definitely want to check all others. The file is generated against gnome 2.16, that means some belongs to HEAD and others belong to gnome-2-16 branch. Here is the command: pcregrep -M -l 'msgid.*\|.*\nmsgstr.*\|' */po/*.po | egrep -v '^(gdm2|gconf)' Abel Regards, Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Abel Cheung (GPG Key: 0xC67186FF) Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF * GNOME Hong Kong - http://www.gnome.hk/ * Opensource Application Knowledge Assoc. - http://oaka.org/ * My own cave: http://me.abelcheung.org/ epiphany/po/dz.po epiphany/po/ka.po epiphany/po/lv.po epiphany/po/mn.po epiphany/po/ms.po epiphany/po/ta.po epiphany/po/uk.po evolution-data-server/po/ar.po evolution/po/ar.po evolution/po/az.po evolution/po/be.po evolution/po/bg.po evolution/po/bn_IN.po evolution/po/bn.po evolution/po/bs.po evolution/po/ca.po evolution/po/cs.po evolution/po/cy.po evolution/po/da.po evolution/po/de.po evolution/po/el.po evolution/po/en_CA.po evolution/po/en_GB.po evolution/po/es.po evolution/po/et.po evolution/po/eu.po evolution/po/fi.po evolution/po/fr.po evolution/po/ga.po evolution/po/gl.po evolution/po/gu.po evolution/po/he.po evolution/po/hi.po evolution/po/hr.po evolution/po/hu.po evolution/po/id.po evolution/po/it.po evolution/po/ja.po evolution/po/ko.po evolution/po/lt.po evolution/po/lv.po evolution/po/mk.po evolution/po/ml.po evolution/po/mr.po evolution/po/nb.po evolution/po/ne.po evolution/po/nl.po evolution/po/nn.po evolution/po/or.po evolution/po/pl.po evolution/po/pt_BR.po evolution/po/pt.po evolution/po/ro.po evolution/po/ru.po evolution/po/sk.po evolution/po/sl.po evolution/po/sq.po evolution/po/[EMAIL PROTECTED] evolution/po/sr.po evolution/po/sv.po evolution/po/ta.po evolution/po/te.po evolution/po/th.po evolution/po/tr.po evolution/po/uk.po evolution/po/vi.po evolution/po/xh.po evolution/po/zh_CN.po evolution/po/zh_HK.po evolution/po/zh_TW.po gnome-games/po/el.po gnome-games/po/es.po gnome-games/po/fa.po gnome-games/po/id.po gnome-games/po/lt.po gnome-games/po/lv.po gnome-games/po/mk.po gnome-games/po/mr.po gnome-games/po/nb.po gnome-games/po/pa.po gnome-games/po/ro.po gnome-games/po/sq.po gnome-games/po/[EMAIL PROTECTED] gnome-games/po/sr.po gnome-games/po/ta.po gnome-games/po/vi.po gnome-panel/po/br.po gnome-panel/po/ca.po gnome-panel/po/dz.po gnome-panel/po/hi.po gnome-panel/po/id.po gnome-panel/po/ka.po gnome-panel/po/ko.po gnome-panel/po/mk.po gnome-panel/po/mn.po gnome-panel/po/nb.po gnome-panel/po/ro.po gnome-panel/po/sq.po gnome-panel/po/[EMAIL PROTECTED] gnome-panel/po/sr.po gnopernicus/po/en_GB.po gnopernicus/po/hi.po gnopernicus/po/id.po gnopernicus/po/lv.po gnopernicus/po/mk.po gnopernicus/po/pt_BR.po gnopernicus/po/sq.po gnopernicus/po/te.po gnopernicus/po/tr.po gok/po/ar.po gok/po/az.po gok/po/bg.po gok/po/bn_IN.po gok/po/bn.po gok/po/ca.po gok/po/cs.po gok/po/cy.po gok/po/da.po gok/po/de.po gok/po/el.po gok/po/en_CA.po gok/po/en_GB.po gok/po/es.po gok/po/eu.po gok/po/fi.po gok/po/fr.po gok/po/gl.po gok/po/gu.po gok/po/hi.po gok/po/hr.po gok/po/hu.po gok/po/id.po gok/po/it.po gok/po/ja.po gok/po/ko.po gok/po/lt.po gok/po/lv.po gok/po/mk.po gok/po/ml.po gok/po/mn.po gok/po/mr.po gok/po/ms.po gok/po/nb.po gok/po/ne.po gok/po/nl.po gok/po/or.po gok/po/pa.po gok/po/pl.po gok/po/pt_BR.po gok/po/pt.po gok/po/ro.po gok/po/ru.po gok/po/rw.po gok/po/sl.po gok/po/sq.po gok/po/[EMAIL PROTECTED] gok/po/sr.po gok/po/sv.po gok/po/ta.po gok/po/tr.po gok/po/uk.po gok/po/vi.po gok/po/zh_CN.po gok/po/zh_HK.po gok/po/zh_TW.po gtk+/po/bn_IN.po gtk+/po/bn.po gtk+/po/ca.po gtk+/po/el.po gtk+/po/en_GB.po gtk+/po/hi.po gtk+/po/id.po gtk+/po/it.po gtk+/po/ja.po gtk+/po/ka.po gtk+/po/ko.po gtk+/po/mk.po gtk+/po/nb.po gtk+/po/pa.po gtk+/po/ru.po gtk+/po/ta.po gtk+/po/vi.po totem/po/bn_IN.po totem/po/bn.po totem/po/id.po totem/po/ka.po totem/po/lv.po totem/po/ml.po totem/po/pt_BR.po ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
