Re: telegnome translations
Le mardi 28 avril 2009 à 14:08 +0100, Colin Watson a écrit : > Hi, > > Could the telegnome module be added to l10n.gnome.org, please? It picked > up a few translations a while back (under a previous maintainer), but > hasn't had any attention recently; I'm guessing that this is because it > needs to be added to some list or other that translators will pay > attention to. Done: http://l10n.gnome.org/module/telegnome If you have a bug tracker, please tell us. Cheers, Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
pre-receive hook translation problem
When creating a new remote branch for seahorse, I ran into the following problem: $ git push origin gtk-doc Total 0 (delta 0), reused 0 (delta 0) --- The following translation (.po) file appears to be invalid. (When updating branch 'gtk-doc'.) po/bn.po The results of the validation follow. Please correct the errors on the line numbers mentioned and try to push again. :772: number of format specifications in 'msgid' and 'msgstr[1]' does not match :1459: number of format specifications in 'msgid' and 'msgstr[1]' does not match msgfmt: found 2 fatal errors To check this locally before attempting to push again, you can use the following command: msgfmt -c bn.po After making fixes, modify your commit to include them, by doing: git add bn.po git commit --amend If you have any further problems or questions, please contact the GNOME Translation Project mailing list . Thank you. --- error: hooks/pre-receive exited with error code 1 To ssh://sa...@git.gnome.org/git/seahorse ! [remote rejected] gtk-doc -> gtk-doc (pre-receive hook declined) error: failed to push some refs to 'ssh://sa...@git.gnome.org/git/seahorse' I checked po/bn.po and neither line contains format specifications. Is this an error in the translation, or should I take this up with the sysadmin team/whomever is maintaining that commit hook? Cheers, Adam ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pre-receive hook translation problem
On Wed, Apr 29, 2009 at 3:00 PM, Adam Schreiber wrote: > When creating a new remote branch for seahorse, I ran into the > following problem: > > > > $ git push origin gtk-doc > Total 0 (delta 0), reused 0 (delta 0) > --- > The following translation (.po) file appears to be invalid. (When > updating branch 'gtk-doc'.) > > po/bn.po > > The results of the validation follow. Please correct the errors on the > line numbers mentioned and try to push again. > > :772: number of format specifications in 'msgid' and > 'msgstr[1]' does not match > :1459: number of format specifications in 'msgid' and > 'msgstr[1]' does not match > msgfmt: found 2 fatal errors > > To check this locally before attempting to push again, you can use the > following command: > > msgfmt -c bn.po > > After making fixes, modify your commit to include them, by doing: > > git add bn.po > git commit --amend > > If you have any further problems or questions, please contact the > GNOME Translation Project mailing list . Thank > you. > --- > error: hooks/pre-receive exited with error code 1 > To ssh://sa...@git.gnome.org/git/seahorse > ! [remote rejected] gtk-doc -> gtk-doc (pre-receive hook declined) > error: failed to push some refs to 'ssh://sa...@git.gnome.org/git/seahorse' > > > > I checked po/bn.po and neither line contains format specifications. > Is this an error in the translation, or should I take this up with the > sysadmin team/whomever is maintaining that commit hook? The message is #. TODO: We can use the GPGME progress to make this more accurate #: ../libseahorse/seahorse-pgp-source.c:723 #, c-format msgid "Loaded %d key" msgid_plural "Loaded %d keys" msgstr[0] "%d-টি কি লোড করা হয়েছে" msgstr[1] "" The problem is that msgstr[1] has been left untranslated (plural form), which causes the issue. Apparently, the git hook for translations is activated when branches are created. Since the specific translation is about 2 years old, it appears it managed to make it through the commit checks that were introduced later. I am not sure if there is a policy for this issues; I think the typical thing to do is to mark those messages as fuzzy. That is, change the above fragment to #. TODO: We can use the GPGME progress to make this more accurate #: ../libseahorse/seahorse-pgp-source.c:723 #, fuzzy, c-format msgid "Loaded %d key" msgid_plural "Loaded %d keys" msgstr[0] "%d-টি কি লোড করা হয়েছে" msgstr[1] "" Simos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pre-receive hook translation problem
On Wed, Apr 29, 2009 at 10:21 AM, Simos Xenitellis wrote: > The problem is that msgstr[1] has been left untranslated (plural > form), which causes the issue. > Apparently, the git hook for translations is activated when branches > are created. > Since the specific translation is about 2 years old, it appears it > managed to make it through the commit checks > that were introduced later. > > I am not sure if there is a policy for this issues; I think the > typical thing to do is to mark those messages as fuzzy. > That is, change the above fragment to Thanks. That got me past bn.po but I received more different errors with other po files. Should I contact each translator individually to have them fix problems as I go along? I suppose there was a time when our QA on po files wasn't as good as it is now. I suspect other projects will be running into this kind of difficulty with older translation files as maintainers branch for 2.27.1. Cheers, Adam ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pre-receive hook translation problem
Adam Schreiber írta: > On Wed, Apr 29, 2009 at 10:21 AM, Simos Xenitellis > wrote: > >> The problem is that msgstr[1] has been left untranslated (plural >> form), which causes the issue. >> Apparently, the git hook for translations is activated when branches >> are created. >> Since the specific translation is about 2 years old, it appears it >> managed to make it through the commit checks >> that were introduced later. >> >> I am not sure if there is a policy for this issues; I think the >> typical thing to do is to mark those messages as fuzzy. >> That is, change the above fragment to >> > > Thanks. That got me past bn.po but I received more different errors > with other po files. Should I contact each translator individually to > have them fix problems as I go along? > > Please file bugs against translations here: http://bugzilla.gnome.org/enter_bug.cgi?product=l10n Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: telegnome translations
On Wed, Apr 29, 2009 at 09:52:36AM +0200, Claude Paroz wrote: > Le mardi 28 avril 2009 à 14:08 +0100, Colin Watson a écrit : > > Could the telegnome module be added to l10n.gnome.org, please? It picked > > up a few translations a while back (under a previous maintainer), but > > hasn't had any attention recently; I'm guessing that this is because it > > needs to be added to some list or other that translators will pay > > attention to. > > Done: http://l10n.gnome.org/module/telegnome Thanks! > If you have a bug tracker, please tell us. Not right now, I'm afraid; I want to build up a slightly better track record of releasing before asking for a bugzilla component. Cheers, -- Colin Watson [cjwat...@debian.org] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gnome-doc-utils branched
Stable work continues on the gnome-2-26 branch. Mallard happens on master! -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pre-receive hook translation problem
2009/4/29 Gabor Kelemen : > Adam Schreiber írta: >> On Wed, Apr 29, 2009 at 10:21 AM, Simos Xenitellis >> wrote: >> >>> The problem is that msgstr[1] has been left untranslated (plural >>> form), which causes the issue. >>> Apparently, the git hook for translations is activated when branches >>> are created. >>> Since the specific translation is about 2 years old, it appears it >>> managed to make it through the commit checks >>> that were introduced later. >>> >>> I am not sure if there is a policy for this issues; I think the >>> typical thing to do is to mark those messages as fuzzy. >>> That is, change the above fragment to >>> >> >> Thanks. That got me past bn.po but I received more different errors >> with other po files. Should I contact each translator individually to >> have them fix problems as I go along? >> >> > Please file bugs against translations here: > http://bugzilla.gnome.org/enter_bug.cgi?product=l10n 580770 l10nUNCOnor errors in seahorse translation 580769 l10nUNCOnor errors in seahorse translation 580768 l10nUNCOmaj CY translation in seahorse has errors Done. Cheers, Adam ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pre-receive hook translation problem
Le mercredi 29 avril 2009 à 11:04 -0400, Adam Schreiber a écrit : > On Wed, Apr 29, 2009 at 10:21 AM, Simos Xenitellis > wrote: > > The problem is that msgstr[1] has been left untranslated (plural > > form), which causes the issue. > > Apparently, the git hook for translations is activated when branches > > are created. > > Since the specific translation is about 2 years old, it appears it > > managed to make it through the commit checks > > that were introduced later. > > > > I am not sure if there is a policy for this issues; I think the > > typical thing to do is to mark those messages as fuzzy. > > That is, change the above fragment to > > Thanks. That got me past bn.po but I received more different errors > with other po files. Should I contact each translator individually to > have them fix problems as I go along? Some translators are more reactive than others... If you can easily find problematic strings, just add the fuzzy marker as Simos told you. You can also ask for help on #i18n channel. > I suppose there was a time when our QA on po files wasn't as good as > it is now. The gettext check hook was deactivated on the SVN server because of an obsolete gettext version :-( > I suspect other projects will be running into this kind of > difficulty with older translation files as maintainers branch for > 2.27.1. Yes, you're not the first one bitten by this issue. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-doc-utils branched
El dc 29 de 04 de 2009 a les 10:49 -0500, en/na Shaun McCance va escriure: > Stable work continues on the gnome-2-26 branch. > Mallard happens on master! l10n.gnome.org updated! > -- > Shaun > > > ___ > gnome-doc-list mailing list > gnome-doc-l...@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-doc-list -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New team for [Dhivehi] ([dv])
Sometime back in 2006, we opened a new team for Dhivehi language (dv) which is the primary language of the Maldives. Coming back to this after an idle period, I couldn't find our team nor the language in the list of Languages. So this is to open a new team for the language and in hope to proceed with translating Gnome to Dhivehi. Contact details: Full Name: Inash Zubair Email: in...@leptone.com Bugzilla account: in...@leptone.com Mailing list: mlu...@googlegroups.com Website: www.mlug.mv For further clarification of information, you could contact me or the mailing list stated above. Cheers. -- Inash Zubair ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
