Re: gnome-control-center string freeze breakages
- From: Christian Rose <menthos gnome org>
- To: Jody Goldberg <jody gnome org>
- Cc: GNOME Release Team <release-team gnome org>,GNOME I18N List <gnome-i18n gnome org>, dobey free fr,GNOME Desktop Development List <desktop-devel-list gnome org>
- Subject: Re: gnome-control-center string freeze breakages
- Date: Thu, 08 Apr 2004 16:12:25 +0200
tor 2004-04-08 klockan 15.18 skrev Jody Goldberg:
> > #: capplets/background/gnome-wp-capplet.c:1453
> > #: capplets/background/gnome-wp-capplet.c:1464
> > msgid "Add Wallpaper"
>
> This was inadvertent and will be reverted.
Thanks.
> > The second changed message is this one:
> >
> > #: capplets/keybindings/eggcellrendererkeys.c:21
> > msgid "<New accelerator...>"
>
> > #: capplets/keybindings/gnome-keybinding-properties.glade.h:3
> > msgid ""
> > "To edit a shortcut, click on the corresponding row and type a new "
> > "accelerator, or press backspace to clear."
> >
>
> Both of these are part of the patch for
> http://bugzilla.gnome.org/show_bug.cgi?id=127004
> with the goal of solving some i18n related sizing problems.
>
> They were discussed there then blocked on the code freeze after
> input from you on the strings. The bug explicitly states that the
> patch would be applied for 2.6.1 and you are on the CC list.
> IMO this patch should stay. Without it that label can get
> unusablely long in some locales.
Being on a cc: list is not necessarily equal to "be approving of". I
myself regularily report problems with i18n in Bugzilla and add me to
the cc: lists of such bugs, and that often even without yet having worn
my GTP hat and decided on it considering effects on the freezes of the
fix.
Unless you can find an explicit statement that something has been
approved, please always assume it hasn't.
Also, I don't think a comment to the effects of "Applied" in a bug
report somewhere satisfies the needs of proper advance warning to
translators. Please follow
http://developer.gnome.org/dotplan/tasks.html#ApprovingFreezeBreaks, and
please rather send a mail notice too much about a string change in the
frozen branches, than one too few.
That being said, I think the explanation above for the last two added
messages is reasonable and satisfactory, and that the fix solves a real
problem in the current UI, so you have my approval for breaking the
string freeze in the case of the last two messages. I don't know whether
Kjartan agrees though, or whether the release team/docs people are ok
with the effects on the UI freeze, however.
Christian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]