String additions to 'gtk+.gtk-2-14'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gtk+.gtk-2-14': + Model column to search through during interactive search Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in anjuta - glade integration
Hi! I finally commmited the patch at http://bugzilla.gnome.org/show_bug.cgi?id=542412 with gives us much better Glade3 integration. They were actually schedules for the last cycle but didn't make it because there were issues in the glade3 module that needed fixing. There are a bunch of new strings. 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
Re: banshee in damned-lies
2009-01-26 klockan 08:17 skrev Deniz Koçak: On Mon, Jan 26, 2009 at 1:17 AM, Daniel Nylander p...@danielnylander.se wrote: Is it just me being blind or is banshee translations being updated in damned-lies? Just commited a change but it doesn't show up Also http://l10n.gnome.org/module/banshee/ has warnings/errors about missing files in POTFILES.in. I've filed http://bugzilla.gnome.org/show_bug.cgi?id=569172 for that. — Wouter signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Automated translation into en_GB
I don't have much fate in anything autotranslated. One time that I proofread a translation that was autoupdated from a compendium and then supposedly read through by the translater I think I used more time on the proofreading than he did doing the translation. I suspect this is similar for most other languages and therefore I don't think it is a good idea to add functionality for it, that will just encurage bad translation practices. Any english looking language is a special case and should be treated as such. Regards Kenneth 2009/1/25 Claude Paroz cla...@2xlibre.net: Le samedi 24 janvier 2009 à 20:44 +, Philip Withnall a écrit : If the strings still need to be checked by a human, which they will, I don't see the point in automatically translating them. Translating strings using the script, without a bot, while going through and checking them doesn't, in my experience, take any longer than just going through and checking them. That said, checking translations as they're made via a mailing list (or similar) seems like a nice idea, and should be better than scanning through the pot file. I'd support that. We could rather easily add per-language pretranslation scripts in damned-lies, so as you have only to push a button to get a translated file that you can then proofread with the vertimus workflow. Upload a translation actions in damned-lies already generate mail. Of course, auto-commits will also improve the process, when it's ready. Claude Note that before you do anything major with en_GB.pl, there are three outstanding bugs for it: http://bugzilla.gnome.org/show_bug.cgi?id=504453 http://bugzilla.gnome.org/show_bug.cgi?id=524049 http://bugzilla.gnome.org/show_bug.cgi?id=523912 The last one is less relevant to this subject, though. Regards, Philip On Sat, 2009-01-24 at 15:03 -0500, Thomas Thurman wrote: Translation from the C locale into en_GB is generally done with Abigail Brady's script written for that purpose, and then hand-checked. The script is very reliable and there are rarely changes needed. However, the whole process is currently done by hand, which means it only happens when someone remembers to do it. This means that trunk is now down to 90% translated and documentation only 28%. I propose a bot which checks the .pot files on Damned Lies once a day, and for all strings *which are not already translated* it translates them using Abigail's script and then commits them to svn. Strings which are already translated are left alone. In the case of strings which need human intervention-- for example, if the script didn't know that wastebasket-bin-- they can subsequently be updated by a human translator. And then hopefully also the script can be fixed. The bot could perhaps also post its translations to a dedicated mailing list so that people could check on them. They could also use the commits list for this, or cia.vc. I am quite willing to write and operate this bot. It could also handle en_CA and en_AU and so on with different translation scripts. What do people think? peace Thomas ___ 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: Automated translation into en_GB
Le lundi 26 janvier 2009 à 12:42 +0100, Kenneth Nielsen a écrit : I don't have much fate in anything autotranslated. One time that I proofread a translation that was autoupdated from a compendium and then supposedly read through by the translater I think I used more time on the proofreading than he did doing the translation. I suspect this is similar for most other languages and therefore I don't think it is a good idea to add functionality for it, that will just encurage bad translation practices. Any english looking language is a special case and should be treated as such. I suppose each language coordinator is experienced enough to judge this himself :-) Claude 2009/1/25 Claude Paroz cla...@2xlibre.net: Le samedi 24 janvier 2009 à 20:44 +, Philip Withnall a écrit : If the strings still need to be checked by a human, which they will, I don't see the point in automatically translating them. Translating strings using the script, without a bot, while going through and checking them doesn't, in my experience, take any longer than just going through and checking them. That said, checking translations as they're made via a mailing list (or similar) seems like a nice idea, and should be better than scanning through the pot file. I'd support that. We could rather easily add per-language pretranslation scripts in damned-lies, so as you have only to push a button to get a translated file that you can then proofread with the vertimus workflow. Upload a translation actions in damned-lies already generate mail. Of course, auto-commits will also improve the process, when it's ready. Claude Note that before you do anything major with en_GB.pl, there are three outstanding bugs for it: http://bugzilla.gnome.org/show_bug.cgi?id=504453 http://bugzilla.gnome.org/show_bug.cgi?id=524049 http://bugzilla.gnome.org/show_bug.cgi?id=523912 The last one is less relevant to this subject, though. Regards, Philip On Sat, 2009-01-24 at 15:03 -0500, Thomas Thurman wrote: Translation from the C locale into en_GB is generally done with Abigail Brady's script written for that purpose, and then hand-checked. The script is very reliable and there are rarely changes needed. However, the whole process is currently done by hand, which means it only happens when someone remembers to do it. This means that trunk is now down to 90% translated and documentation only 28%. I propose a bot which checks the .pot files on Damned Lies once a day, and for all strings *which are not already translated* it translates them using Abigail's script and then commits them to svn. Strings which are already translated are left alone. In the case of strings which need human intervention-- for example, if the script didn't know that wastebasket-bin-- they can subsequently be updated by a human translator. And then hopefully also the script can be fixed. The bot could perhaps also post its translations to a dedicated mailing list so that people could check on them. They could also use the commits list for this, or cia.vc. I am quite willing to write and operate this bot. It could also handle en_CA and en_AU and so on with different translation scripts. What do people think? peace Thomas ___ 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Bug 569118 - Use C_() instead of Q_() with context (orca)
Hi All:
I'm looking at http://bugzilla.gnome.org/show_bug.cgi?id=569118, which
is a request to migrate to C_ from Q_. Doing this in the C programming
language seems pretty straightforward, but I'm puzzled about how to do
it in Python.
The current Orca code does the equivalent of this:
def Q_(s):
s = _(s)
s = s[s.find('|')+1:]
return s
This was easy to do since we controlled the whole string. Now that a
context is explicitly called out with the C_ method, it seems like we
might need to make a different gettext method call. I'm not quite sure
what to do.
Is there a Python precedence that exists that I can take a look at?
Will
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
2009-01-26 klockan 13:18 skrev Willie Walker: I'm looking at http://bugzilla.gnome.org/show_bug.cgi?id=569118, which is a request to migrate to C_ from Q_. Doing this in the C programming language seems pretty straightforward, but I'm puzzled about how to do it in Python. This is not yet officially supported in the Python locale/gettext modules. See http://bugs.python.org/issue2504 for more information. In the mean time, you could just stick to using Q_(), since it's functionally equivalent (but a bit harder for translators to use correctly.) — Wouter signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in Accerciser
Hi, A string in accercisers was changed to include translation context. See http://bugzilla.gnome.org/show_bug.cgi?id=520296 for more information. — Wouter signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Sabayon branched for 2.24
Sabayon has been branched for 2.24 (branch name, funnily enough, gnome-2-24), from the revision before the one where I broke string freeze. :) Development will continue in trunk. Philip On Mon, 2009-01-26 at 10:03 -0600, Federico Mena Quintero wrote: On Sun, 2009-01-25 at 20:54 +, Philip Withnall wrote: I committed a string change to Sabayon yesterday[1,2], but didn't realise that Sabayon hasn't branched for 2.24, and is still in string freeze. The suggested solution is to keep the commit unreverted, and branch retrospectively from the previous revision. However, I can't really do that without your permission, since I'm not maintainer. :-) Go ahead and branch it :) I need to do a release soon, anyway. Federico signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Inform of submission action available when status is Translating
Le dimanche 25 janvier 2009 à 23:26 +0100, Marcel Telka a écrit : On Sun, Jan 25, 2009 at 10:29:42PM +0100, Claude Paroz wrote: We should probably prevent users adding a file for the Reserve... actions. +1 Done. Now, my dear damned-lies developer, is it OK that for my account, with commiter privileges, both Write comment and Inform of submission actions are currently available. We've decided to offer Inform of submission for all stages for committers. Of course, it is not nice to do that, except when you reserved the translation yourself. I see only one outcome from this process done by commiter: Reserve for translation - Inform of submission The outcome is: an email sent to the team mailing list. Is this intended? Why not? The mailing list is informed someone has updated the specific translation. Just that. If you don't want to alert the mailing list, just commit the file without using vertimus at all. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Inform of submission action available when status is Translating
On Mon, Jan 26, 2009 at 07:38:24PM +0100, Claude Paroz wrote: Le dimanche 25 janvier 2009 à 23:26 +0100, Marcel Telka a écrit : On Sun, Jan 25, 2009 at 10:29:42PM +0100, Claude Paroz wrote: We should probably prevent users adding a file for the Reserve... actions. +1 Done. Great. Thanks. Few minutes ago I had a question from my translator why it is no longer possible to attach a file to Reserve ... action :-). It means that the change makes sense! Thanks. Now, my dear damned-lies developer, is it OK that for my account, with commiter privileges, both Write comment and Inform of submission actions are currently available. We've decided to offer Inform of submission for all stages for committers. Of course, it is not nice to do that, except when you reserved the translation yourself. I see only one outcome from this process done by commiter: Reserve for translation - Inform of submission The outcome is: an email sent to the team mailing list. Is this intended? Why not? The mailing list is informed someone has updated the specific translation. Just that. If you don't want to alert the mailing list, just commit the file without using vertimus at all. Ok. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Automated translation into en_GB
2009/1/26 Claude Paroz cla...@2xlibre.net: Le lundi 26 janvier 2009 à 12:42 +0100, Kenneth Nielsen a écrit : I don't have much fate in anything autotranslated. One time that I proofread a translation that was autoupdated from a compendium and then supposedly read through by the translater I think I used more time on the proofreading than he did doing the translation. I suspect this is similar for most other languages and therefore I don't think it is a good idea to add functionality for it, that will just encurage bad translation practices. Any english looking language is a special case and should be treated as such. I suppose each language coordinator is experienced enough to judge this himself :-) Sure, let me refraise it in a way so that I don't speak for anyone else. I personally don't think automated translations in any shape, way or form, have any justification in free software for any other languages than the english derivatives. One could of course argue, that it will always be possible to people that don't give a damn to commit broken (possible automated) translations i.e. an automate pretranslations script in DL won't change that, however I do think there is a _availability_ argument in there also. In any case, my sole concerns with the previous e-mail was that before you (being one of the DL gurus) consider using any time on this (no matter how little) I think there should be maybe a couple of positive feedbacks first? Other than from the english family of languages, which can't cover more than 4 of our 118 languages. I think some of all the other stuff you guys are talking about doing with DL is way more important. Regards Kenneth nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Evolution 2.24.[.4 / .5]
Hello guys, I have communicated on evolution-hackers that due to regressions we have in 2.24.x stable series, we are extending the stable release cycles beyond 2.24.3. Here is the release schedule for the same. Jan 30 - 2.24.4 Feb 25 - 2.24.5 We finalized this last Wednesday and I'm late in communicate this, sorry for that. -Srini. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Some translated files need to be commited
Hi, I have translated some modules and the translations are attached in their pages. These are the links: http://l10n.gnome.org/vertimus/gnome-nettool/HEAD/po/ps http://l10n.gnome.org/vertimus/gnome-netstatus/HEAD/po/ps As I am back after long, so don't know about the new system that whether they are committed automatically after attaching or we have to attach them there and ask someone to commit them. If second is the case, so please someone commit them for me. thanks -- Blog: http://zabeehkhan.blogspot.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Some translated files need to be commited
Hi, The Vertimus functionality that has been added to Damned-Lies allows to manage the translation, but, by now it doesn't commit the files. By now it only controls the translation workflow: translating, reviewing and committing. I have uploaded the translations already :) Cheers, El dt 27 de 01 de 2009 a les 10:32 +0500, en/na Zabeeh Khan va escriure: Hi, I have translated some modules and the translations are attached in their pages. These are the links: http://l10n.gnome.org/vertimus/gnome-nettool/HEAD/po/ps http://l10n.gnome.org/vertimus/gnome-netstatus/HEAD/po/ps As I am back after long, so don't know about the new system that whether they are committed automatically after attaching or we have to attach them there and ask someone to commit them. If second is the case, so please someone commit them for me. thanks -- 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
