Re: String freeze break in GCC

[Kjartan Maraas <kmaraas broadpark no>]

man, 16.02.2004 kl. 11.23 -0500, skrev Jody Goldberg:

> On Sun, Feb 15, 2004 at 02:56:52AM +0100, Danilo Segan wrote:
> > Jody, translators,
> > 
> > The following change is breaking the string freeze:
> >   http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvs/gnome&subdir=gnome-control-center%2Fcapplets%2Fdefault-applications&command=DIFF_FRAMESET&root=/cvs/gnome&file=gnome-default-applications-properties-structs.c&rev1=1.6&rev2=1.7
> > 
> > I'm talking about following new messages (it's not outright obvious
> > from the diff):
> > 
> > #: capplets/default-applications/gnome-default-applications-properties-structs.c:12
> > msgid "Firebird/FireFox"
> > 
> > #: capplets/default-applications/gnome-default-applications-properties-structs.c:17
> > msgid "W3M Text Browser"
> > 
> > 
> > We should probably wait on Christian Rose (menthos@gnome.org) to
> > decide what to do about this breakage, but since status pages are
> > malfunctioning, it's increasingly tougher to detect them now, and I
> > don't want to forget about this one.
> > 
> > Provided this change is approved, there are two new messages for
> > translators.
> > 
> > (Btw, Christian's host menthos.com seems to be down atm, so his
> > @gnome.org alias delays the mail, and I don't know if and when he'll
> > receive all this.)
> 
> Neither of those messages absolutely requires translation as they
> are refering to the names of the browser appliction.   If people
> prefer I'll reword them that way.  All of this code is somewhat in
> flux anyway as that hard coded list is being moved into gconf.

I think that they should be marked and there's a good chance people will
want to translate them anyway (at least the latter of the two). The
challenge here is that every time people add strings translators have to
update from CVS, update the po file, open editor of choice and look at
the strings before deciding if it's worth translating. So the above
argument doesn't necessarily mean there's no work involved on the
translators side. Furthermore it affects stats for all languages :-)

That said, I think this is a worthwhile change and we're still just
entering the freeze period so I think we should fix as many of the
remaining string-involving bugs as possible before entering hard freeze.

...which leaves the question of having a slushy period before the freeze
in the actual schedule so we can plan ahead when prioritizing these
kinds of changes?

Cheers
Kjartan