Re: Request string freeze break in Anjuta

2013-09-10 Thread Petr Kovar
Piotr Drąg piotrd...@gmail.com, Sat, 7 Sep 2013 15:45:57 +0200:

 2013/9/7 Sébastien Granjoux seb@free.fr:
  In order to adapt to languages having difference plural forms, we have
  to use ngettext instead of gettext to fix a message as described in
  this bug: https://bugzilla.gnome.org/show_bug.cgi?id=707562
 
  I think this change is a string freeze break.
 
  This message is in a removal confirmation dialog which is not used very
  often. Moreover it is used only when 2 or more elements are removed so I
  think it's not an issue for most common languages. I will add a comment
  for translator for this.
 
  Then could I push the complete patch using ngettext instead of gettext
  or should I wait the next cycle?
 
 
 As a maintainer of one of the supposedly not common languages, I
 wholeheartedly give you my +1.
 
 So you have 1/2 from i18n.

2/2 from i18n.

Cheers,
Petr Kovar
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.


Re: Request string freeze break in Anjuta

2013-09-10 Thread Sébastien Granjoux

Hi,


Le 10/09/2013 20:29, Petr Kovar a écrit :

Piotr Drąg piotrd...@gmail.com, Sat, 7 Sep 2013 15:45:57 +0200:

2013/9/7 Sébastien Granjoux seb@free.fr:

In order to adapt to languages having difference plural forms, we have
to use ngettext instead of gettext to fix a message as described in
this bug: https://bugzilla.gnome.org/show_bug.cgi?id=707562

I think this change is a string freeze break.

This message is in a removal confirmation dialog which is not used very
often. Moreover it is used only when 2 or more elements are removed so I
think it's not an issue for most common languages. I will add a comment
for translator for this.

Then could I push the complete patch using ngettext instead of gettext
or should I wait the next cycle?


So you have 1/2 from i18n.

2/2 from i18n.


Thank, I have pushed the corresponding commit 
(https://git.gnome.org/browse/anjuta/commit/?id=e55dafa59cc8fc94025214ebd73a9bbb14f8f5a0)



Regards,

Sébastien
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.


Request string freeze break in Anjuta

2013-09-07 Thread Sébastien Granjoux

Hi,


In order to adapt to languages having difference plural forms, we have 
to use ngettext instead of gettext to fix a message as described in this 
bug:

https://bugzilla.gnome.org/show_bug.cgi?id=707562

I think this change is a string freeze break.

This message is in a removal confirmation dialog which is not used very 
often. Moreover it is used only when 2 or more elements are removed so I 
think it's not an issue for most common languages. I will add a comment 
for translator for this.


Then could I push the complete patch using ngettext instead of gettext 
or should I wait the next cycle?



Regards,

Sébastien
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.


Re: Request string freeze break in Anjuta

2013-09-07 Thread Piotr Drąg
2013/9/7 Sébastien Granjoux seb@free.fr:
 In order to adapt to languages having difference plural forms, we have to
 use ngettext instead of gettext to fix a message as described in this bug:
 https://bugzilla.gnome.org/show_bug.cgi?id=707562

 I think this change is a string freeze break.

 This message is in a removal confirmation dialog which is not used very
 often. Moreover it is used only when 2 or more elements are removed so I
 think it's not an issue for most common languages. I will add a comment for
 translator for this.

 Then could I push the complete patch using ngettext instead of gettext or
 should I wait the next cycle?


As a maintainer of one of the supposedly not common languages, I
wholeheartedly give you my +1.

So you have 1/2 from i18n.

-- 
Piotr Drąg
http://raven.fedorapeople.org/
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.