Re: Google Code-in
There are no wiki privs. Anybody can get an account and edit it. I coordinated GCI for GNOME last year. As I am travelling right now (Google Mentor Summit, nice coincidence), please feel free to edit https://live.gnome.org/GoogleCodeIn/Tasks?action=show (take a look at older versions of that file, as we had a template for potential tasks and that is really needed!), and to update and link to that page from https://live.gnome.org/GoogleCodeIn (and add a warning that GNOME is NOT an accepted org yet). If that's too much work: I might have some time to do this tomorrow myself. :) Thanks, andre Hi Andre! The second link has invalid links in article. I hope to create some tasks for my locale, because there is many tiny mistakes that I have no time to find out. Thanks! ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: More on words (screenshots!)
2011-10-22 17:44 keltezéssel, Jorge González írta: Hi, On Mon, Oct 17, 2011 at 12:47, Gil Forcada wrote: Hi all, Last weekend I got some time to do add word statistics and progress bars on the po file details. The code is living in bug #661869[1] and I added a couple of screenshots [2][3] to see the actual results of applying the patches. Any comments on how are the data displayed would be really appreciated. Sorry but I do not get the point, why do we need those statistics? It can be used as a more accurate estimation of work left. Meaning, that when the file is completely translated, these stats show somethig I do not understand. Eg: http://l10n.gnome.org/vertimus/anjuta/master/help/es PO file statistics: Strings: 100% 534 0 0Words: 94% 7865 35 386 So, file 100% translated, but not "Words"? Please share your experience here: https://bugzilla.gnome.org/show_bug.cgi?id=662454 Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Improve translations in Mallard
Hi all, I added a couple of bugs to Yelp regarding mallard translations. In [1] I ask for adding msgctxt to all Mallard strings so that the (p), (title) and other hints that are easily seen by the translators as are now that are only available on the source reference. In [2] I ask for filtering comments on translations, since I suppose that are only useful for the documentation team and doesn't make any sense to translate (prove me wrong though). Cheers, [1] https://bugzilla.gnome.org/show_bug.cgi?id=662508 [2] https://bugzilla.gnome.org/show_bug.cgi?id=662509 -- 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 planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'hamster-applet.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'hamster-applet.master': + "The overview window of hamster time tracker" + "Time Tracking Overview" 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
Coordination for Xhosa team
I'm helping someone get started in GNOME localisation for Xhosa. I contacted Adi Attar, the listed coordinator for Xhosa, but immediately got a bounce. It seems that she was doing this as part of some work by Canonical a while ago, but is probably not working for Canonical or on GNOME localisation any more. Maybe Adi is on this mailing list and can reply? If not, I guess I can just go ahead and help the translator to commit. If somebody can set me as a committer for Xhosa, that would be kind. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/firefox-maybe-now-most-popular-africa ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Coordination for Xhosa team
Hi! Am Sonntag, den 23.10.2011, 23:18 +0200 schrieb F Wolff: > I'm helping someone get started in GNOME localisation for Xhosa. I > contacted Adi Attar, the listed coordinator for Xhosa, but immediately > got a bounce. It seems that she was doing this as part of some work by > Canonical a while ago, but is probably not working for Canonical or on > GNOME localisation any more. Maybe Adi is on this mailing list and can > reply? Well, according to the guidelines, give her a week ;) > If not, I guess I can just go ahead and help the translator to commit. > If somebody can set me as a committer for Xhosa, that would be kind. I think it would be better (in the long term) to have a (new) coordinator for Xhose if the old is irresponsive. Thanks and regards, Johannes 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: Improve translations in Mallard
On Sun, 2011-10-23 at 12:27 +0200, Gil Forcada wrote: > Hi all, > > I added a couple of bugs to Yelp regarding mallard translations. Hi Gil, Thanks for the reports. It's valuable to know what's helpful to you. The bugs you filed were from PO files generated by xml2po. We've been slowly transitioning our documents to itstool. There are differences. > In [1] I ask for adding msgctxt to all Mallard strings so that the (p), > (title) and other hints that are easily seen by the translators as are > now that are only available on the source reference. With itstool, the line that tells you file and line number for the messages gives you to levels of element context. So instead of this: #: C/account-jabber.page:59(gui) You see this: #: C/account-jabber.page:59(title/gui) Which is more useful in a lot of cases. Maybe three levels would be better sometimes. itstool can set msgctxt for nodes. We use it to distinguish secondary title types right now. I'm wary of using this too much though. It can really get unwieldy if we start automatically setting msgctxt for all nodes. We can also set comments automatically based on what nodes the message came from. If there are common cases where extra information would be valuable, we can add custom ITS rules for those. > In [2] I ask for filtering comments on translations, since I suppose > that are only useful for the documentation team and doesn't make any > sense to translate (prove me wrong though). itstool already gets this right. With itstool, we have the ability to mark things as non-translatable. We can do this node-by-node in a document (e.g. marking a code block non-translatable) or with the global ITS rules (e.g. all Mallard comment elements). And the global ITS rules already mark Mallard comments non-translatable. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Google Code-in
El dg 23 de 10 de 2011 a les 11:25 +0300, en/na Коростіль Данило va escriure: > > There are no wiki privs. Anybody can get an account and edit it. > > > > I coordinated GCI for GNOME last year. As I am travelling right now (Google > > Mentor Summit, nice coincidence), please feel free to edit > > https://live.gnome.org/GoogleCodeIn/Tasks?action=show (take a look at older > > versions of that file, as we had a template for potential tasks and that is > > really needed!), and to update and link to that page from > > https://live.gnome.org/GoogleCodeIn (and add a warning that GNOME is NOT an > > accepted org yet). > > > > If that's too much work: I might have some time to do this tomorrow myself. > > :) > > > > Thanks, > > andre > > > Hi Andre! > The second link has invalid links in article. > I hope to create some tasks for my locale, because there is many tiny > mistakes that I have no time to find out. > Thanks! Hi all, I created [1] where we can start dumping all our ideas, either global or locale specific. Then, when time comes we can move to Google Code In or wherever is needed. I made it in 5 minutes, so please, improve the styling and descriptions as you please :) Cheers, [1] https://live.gnome.org/TranslationProject/SmallTasks > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- 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 planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Improve translations in Mallard
> [: Shaun McCance :] > We've been slowly transitioning our documents to itstool. > [...] > You see this: > > #: C/account-jabber.page:59(title/gui) While intltool does this too, it shouldn't be done. PO processing tools, be it PO editors or whatever else, have no obligation to consider and parse such comments. A source reference comment, according to de-facto PO format reference (Gettext manual), should contain only file names and line numbers, i.e. #: file1:lno1 file2:lno2 Anything else should go into extracted comments. For example: #: C/account-jabber.page:59 #. tag-path: title/gui -- Chusslove Illich (Часлав Илић) 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: Improve translations in Mallard
On Mon, 2011-10-24 at 00:18 +0200, Chusslove Illich wrote: > > [: Shaun McCance :] > > We've been slowly transitioning our documents to itstool. > > [...] > > You see this: > > > > #: C/account-jabber.page:59(title/gui) > > While intltool does this too, it shouldn't be done. PO processing tools, be > it PO editors or whatever else, have no obligation to consider and parse > such comments. Are there any processing tools that actually have a problem with this? > A source reference comment, according to de-facto PO format > reference (Gettext manual), should contain only file names and line numbers, > i.e. #: file1:lno1 file2:lno2 Anything else should go into extracted > comments. For example: > > #: C/account-jabber.page:59 > #. tag-path: title/gui The problem I see with that is that the tag path is no longer tied to the file that defined it. That's fine when strings only appear once, but how about this: #: C/some-topic.page:42 #: C/another-topic.page:17 #. tag-path: title/gui #. tag-path: td/p Which is which? Maybe it doesn't matter that much. I don't know. I'm not a translator. I'm just trying to make things easier. On the other hand, putting the path on its own line would make longer paths less painful, so we could perhaps do a full path, or a path up to the closest sectioning element. That might be helpful. On the other other hand, gettext defines and treats PO files in a way that's not really nice to third-party tools. I'd love to put some info in #, comments (e.g. marking a message transliteration-only), but the fact that it's a controlled vocabulary prevents me. I'd rather not put more and more stuff in #. comments, because it's going to get in the way of actual comments to translators at some point. Open to discussion on all this. These tool are there to make your jobs easier. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
