Re: GNOME 2.32 Release Notes

2010-09-23 Thread Andika Triwidada
another typo in rndevelopers.xml? diff --git a/help/C/rndevelopers.xml b/help/C/rndevelopers.xml index 5eb2573..f0d9672 100644 --- a/help/C/rndevelopers.xml +++ b/help/C/rndevelopers.xml @@ -62,7 +62,7 @@ Glib also includes new support for dtrace and systemtap static markers;

Re: GNOME 2.32 Release Notes

2010-09-23 Thread Andika Triwidada
typo? diff --git a/help/C/rnlookingforward.xml b/help/C/rnlookingforward.xml index 07db4a1..cd227a8 100644 --- a/help/C/rnlookingforward.xml +++ b/help/C/rnlookingforward.xml @@ -20,7 +20,7 @@ and the GNOME Activity Journal which easily helps you browse and find files on your com

Re: GNOME 2.32 Release Notes

2010-09-23 Thread Andika Triwidada
On Fri, Sep 24, 2010 at 8:11 AM, Paul Cutler wrote: > Hi localization teams! > In the better late than never category, the Release Notes are now ready for > translation.  They are in the release-notes repo in the gnome-2-32 branch. > I sincerely apologize for the delay in getting these ready for y

GNOME 2.32 Release Notes

2010-09-23 Thread Paul Cutler
Hi localization teams! In the better late than never category, the Release Notes are now ready for translation. They are in the release-notes repo in the gnome-2-32 branch. I sincerely apologize for the delay in getting these ready for you. Please let me know if you have any questions. Paul __

Re: String additions to 'anjuta.master'

2010-09-23 Thread Kenneth Nielsen
Hallo guys How about looking for it at commit time? What I was thinking is that, afaik the strings that are marked for translation are done so with a special syntax. So we should be able to look for strings that are not marked for translation. If that can be scripted, then maybe we can include th

Re: Removal of beast

2010-09-23 Thread Claude Paroz
Le jeudi 23 septembre 2010 à 13:55 -0300, Jonh Wendell a écrit : > Hi, i18n team. > > Given the response I got from > https://bugzilla.gnome.org/show_bug.cgi?id=630422 I ask beast to be > removed from DL. It must be translated using transifex, according to its > author. OK, removed from DL. Ther

Re: Removal of beast

2010-09-23 Thread Johannes Schmid
Hi! > Given the response I got from > https://bugzilla.gnome.org/show_bug.cgi?id=630422 I ask beast to be > removed from DL. It must be translated using transifex, according to its > author. The far more important question is if we might want to migrate to some better infrastructure or modernize

Removal of beast

2010-09-23 Thread Jonh Wendell
Hi, i18n team. Given the response I got from https://bugzilla.gnome.org/show_bug.cgi?id=630422 I ask beast to be removed from DL. It must be translated using transifex, according to its author. Thanks, -- Jonh Wendell http://www.bani.com.br ___ gnome-

Re: String additions to 'anjuta.master'

2010-09-23 Thread Johannes Schmid
Hi! > It isn't necessary to review things by hand only. I wrote a page on the > wiki a while ago about testing i18n. A big part of this is about > spotting strings not marked for translation: This is even more manually actually. In a 100 000+ lines applications you hardly ever see every dialog.

Re: String additions to 'anjuta.master'

2010-09-23 Thread F Wolff
Op Do, 2010-09-23 om 09:53 +0200 skryf Johannes Schmid: > Hi! > > > Sure, now I see that there are devhelp messages as well. I don't blame > > you for fixing this, obviously, but I do think it is disrespectful to > > translators that NONE of the developers on either of the development > > teams th

Re: String additions to 'anjuta.master'

2010-09-23 Thread Johannes Schmid
Hi! > Incidentally, "alfanumeric" should be "alphanumeric". If nobody comes up, I will fix that later (and update all translations using some sed magic. Regards, Johannes ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/l

Re: String additions to 'anjuta.master'

2010-09-23 Thread Johannes Schmid
Hi! > Sure, now I see that there are devhelp messages as well. I don't blame > you for fixing this, obviously, but I do think it is disrespectful to > translators that NONE of the developers on either of the development > teams thought to look for this before now. That is far from easy to catch.