This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.
There have been following string additions to module 'glib.glib-2-28':
+ "No PEM-encoded private key found"
Note that this doesn't directly indicate a string freeze break, but it
might be worth investigat
Hi,
I used latest Gnome UI translations to examine how frequently translators
modify formatting directives. There are only about 300 modifications in all
languages taken together, but over 90% of them are likely unintentional
(typos or unfuzzying glitches), so I thought of reporting. The list of a
En/na F Wolff ha escrit:
Op Sa, 2011-07-23 om 10:55 +0200 skryf Jordi Mas:
Hello,
I have just frozen the strings for gbrainy version 2.01. Only bug fixes
will be committed from now.
Hi Jordi
Bug 650579 is still not fixed. We need msgctxt to split that into two
strings. Is it possible to sti
On Wed, Jul 27, 2011 at 4:28 AM, F Wolff wrote:
>
> Hi everybody
>
> GNOME 3.0 came and went, and i18n seemed to never be a goal of GNOME
> 3.0. I'm hoping things can improve in future releases, so I'm trying to
> follow up on some bugs that affect i18n that I have reported before
> which haven't
Hi!
> GNOME 3.0 came and went, and i18n seemed to never be a goal of GNOME
> 3.0. I'm hoping things can improve in future releases, so I'm trying to
> follow up on some bugs that affect i18n that I have reported before
> which haven't received attention yet.
Well, that's not true, i18n was and is
On Wed, 2011-07-27 at 07:54 +0200, Antonio Maya wrote:
> please dont send me more mails, thanks
We cannot. Please unsubscribe yourself.
The link is at the bottom of any email:
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > http://mail.gnome.org/mailman/listinfo/gnome-i18n
andre
--
mai
Hi F Wolff,
On Wed, Jul 27, 2011 at 10:28, F Wolff wrote:
>
> Hi everybody
>
> GNOME 3.0 came and went, and i18n seemed to never be a goal of GNOME
> 3.0. I'm hoping things can improve in future releases, so I'm trying to
> follow up on some bugs that affect i18n that I have reported before
> wh
Hi everybody
GNOME 3.0 came and went, and i18n seemed to never be a goal of GNOME
3.0. I'm hoping things can improve in future releases, so I'm trying to
follow up on some bugs that affect i18n that I have reported before
which haven't received attention yet.
In which cases are we allowed to fix
