Re: gdu string freeze break request
David Zeuthen írta: Heya, I'd like to request a string freeze break for the patch in https://bugzilla.gnome.org/show_bug.cgi?id=608423 since it fixes some spelling error. Thanks for considering. i18n approval 1/2. We are early in the freeze and spleling errors are so lame... Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to change the default asignee for the language (Gujarati) component?
On Wed, Feb 24, 2010 at 12:53:28PM +0530, Ankit Patel wrote: Is there a way to change the default asignee? I've changed the default assignee to l10n-gu-ma...@gnome.bugs. Watch that email address to receive the bugs. #bugs if you need assistance -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
How to prepare for GNOME 3.0
Hi, Gnome 2.30 is the last before 3.0 and this period should be used for testing the Gnome 2.30 components and translations. As far as I understand, the most important components of Gnome 3.0 will be: Gnome Shell Gnome Zeitgeist Mutter Our team has translated Gnome Shell. Mutter is seems an easy task because it is based on metacity and the strings are similar. Zeitgeist/Gnome activity journal is another thing. It is not in Gnome's git. When will it be imported there? There was a policy that official releases are to be based on source on Gnome's servers. What should we do in order to translate it? Bear in mind that bazaar is different source control system and Launchpad has their own policies. Kind regards: al_shopov ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Missing libgnome-keyring on l10n.gnome.org
The gnome-keyring module was splitted some times ago to gnome-keyring and libgnome-keiring modules. The latter isn't listed on l10n.gnome.org :( ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Missing libgnome-keyring on l10n.gnome.org
Luca Ferretti írta: The gnome-keyring module was splitted some times ago to gnome-keyring and libgnome-keiring modules. The latter isn't listed on l10n.gnome.org :( Here it is: http://l10n.gnome.org/module/libgnome-keyring/ Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to prepare for GNOME 3.0
According to GNOME release rules it needs to be imported. I guess that will be done once the final module decision for 3.0 is taken. Well, this will happen after Gnome 2.30 which sadly means that we will miss the boat to ship translated proto GNOME 3.0 components via popular distros like Fedora. al_shopov ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to prepare for GNOME 3.0
El dc 24 de 02 de 2010 a les 13:53 +0100, en/na Andre Klapper va escriure: Am Mittwoch, den 24.02.2010, 14:33 +0200 schrieb li...@kambanaria.org: Well, this will happen after Gnome 2.30 which sadly means that we will miss the boat to ship translated proto GNOME 3.0 components via popular distros like Fedora. Not if you translate it in Launchpad, where gnome-journal/zeitgeist upstream is currently located as the maintainers chose to do so. Same with every other project that's currently not officially included in GNOME. Sure but then we will have the in general bad quality translations done on Launchpad :S Not that I don't want to start a flame or anything, just a thought that has been shared on this list from time to time. Cheers, Once it's proposed for inclusion in GNOME the current situation might/can/will change, as Johannes already wrote here. andre -- 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
Re: Using different translation workflow
Le mardi 23 février 2010 à 08:31 +0100, Claude Paroz a écrit : Hi, For the first time, we have a GNOME Git hosted module that choose to use a different translation tool than l10n.gnome.org. https://bugzilla.gnome.org/show_bug.cgi?id=608627 http://mail.gnome.org/archives/gnome-i18n/2010-February/msg00153.html On one side, I would say that freedom is the key, so every module maintainer should choose the tool which suited him the best. On the other side, this could lead to fragmentation. If GNOME translation teams have to use several different platform for their work, there is clearly an overhead implied. Considering various comments on the bug #608627, coordinators don't like this situation. So the question is, should we make it an explicit requirement to use l10n.gnome.org as the main translation platform for a module to be hosted in GNOME Git? Thanks for all those who contributed to this discussion. While discussing privately with Debarshi, we found a sort of compromise. Transifex.net will still be available to translate solang, but po files will be sent by email from the platform to Debarshi, which will then submit the files to the corresponding GNOME translation team. This way, GNOME teams will still be able to quality check the file and then commit it like any other GNOME module. Hopefully this solution will be satisfactory to all parts. Cheers, Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Using different translation workflow
On Wed, Feb 24, 2010 at 3:44 PM, Claude Paroz cla...@2xlibre.net wrote: Transifex.net will still be available to translate solang, but po files will be sent by email from the platform to Debarshi, which will then submit the files to the corresponding GNOME translation team. This way, GNOME teams will still be able to quality check the file and then commit it like any other GNOME module. Hopefully this solution will be satisfactory to all parts. Great news Claude! Really glad to see things worked out for everyone involved! Cheers, -- Og B. Maciel omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Using different translation workflow
I suppose we're suggesting this as a temporary solution, right? It kinda puts a lot of weight on the developer himself and scalability is pretty low. I think the extra work of routing translations from Tx.net to l10n.gnome.org manually will be worth the effort in the end. Cheers, Debarshi -- One reason that life is complex is that it has a real part and an imaginary part. -- Andrew Koenig ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Using different translation workflow
Le mercredi 24 février 2010 à 23:30 +0200, Debarshi Ray a écrit : I suppose we're suggesting this as a temporary solution, right? It kinda puts a lot of weight on the developer himself and scalability is pretty low. I think the extra work of routing translations from Tx.net to l10n.gnome.org manually will be worth the effort in the end. Dimitris, We could try to automate the process a bit. Let's take this privately and see if we could send the file by email directly to Damned-Lies. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Freeze break request: #598820 Add tap-to-click button settings to gnome-settings-daemon
Hi! gnome-i18n: If gconf schema strings do not need translation or are otherwise exempt from string freezes, please say so explicitly -- it is not clear from the string freeze guide[1]. They are not and exempt and need translation. Anyway, 1 of 2 from i18n from my side and sorry for missing it first. Regards, Johannes signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
