Hallo developers.
Since the release of GNOME 3.4 we have received a steady stream of
emails saying "This is not a string freeze break, we just forgot to mark
the strings for translation". So much so, that the statistics e.g. for
my language (which has not been touched since release) now counts
Hello,
On Mon, May 7, 2012 at 1:59 PM, Kenneth Nielsen wrote:
> Hallo developers.
>
> Since the release of GNOME 3.4 we have received a steady stream of emails
> saying "This is not a string freeze break, we just forgot to mark the
> strings for translation". So much so, that the statistics e.g.
Op Ma, 2012-05-07 om 13:59 +0200 skryf Kenneth Nielsen:
> Hallo developers.
>
> Since the release of GNOME 3.4 we have received a steady stream of
> emails saying "This is not a string freeze break, we just forgot to mark
> the strings for translation". So much so, that the statistics e.g. for
Den 07-05-2012 14:04, Jorge González skrev:
Hello,
On Mon, May 7, 2012 at 1:59 PM, Kenneth Nielsen wrote:
Hallo developers.
Since the release of GNOME 3.4 we have received a steady stream of emails
saying "This is not a string freeze break, we just forgot to mark the
strings for translation".
I think it should be a small shell-script that would detect strings
nos marked for translation, using the "_" function.
For example, in gnome-packagekit/src folder, I've ran the following command:
egrep -i "label.*\(\"" * |grep -v "_("
To detect all the «gtk_label_new» without a translatable st
On Mon, May 7, 2012 at 7:59 AM, Kenneth Nielsen wrote:
> So please... If you could make a bit more of an effort of checking your
> sources for non-internationalized strings before release that would be
> great. IMHO 63 is just a bit on the high side of where this number should be
Of course, we s
