Re: [DL]String additions to 'glib.glib-2-70'

[Philip Withnall <philip tecnocode co uk>]

On Thu, 2022-01-20 at 14:18 +0100, Claude Paroz wrote:
> Le 20.01.22 à 14:00, Alexandre Franke a écrit :
> > On Thu, Jan 20, 2022 at 11:55 AM Philip Withnall
> > <philip tecnocode co uk> wrote:
> > > Oops, I didn’t notice this backport was a string freeze break.
> > > The new
> > > string is an error message which is very unlikely to be seen by
> > > users.
> > >
> > > Options are:
> > >   - Unmark the string for translation and always display the
> > > error
> > > message in English
> >
> > Untranslated strings that can not be translated are always worse
> > than
> > untranslated strings because the work has just not been done.
> > Please
> > don’t do that, ever.
> >
> > >   - Leave the string marked as translatable, and be happy with
> > > the fact
> > > that most translators probably won’t update it and it will be
> > > displayed in English
> >
> > Happy is not the term I would use, but I can live with it. Let’s
> > call
> > this an exception plea and here is 1/2 from i18n.
>
> In fact, glib is historically not subject to the string freeze, even
> if 
> we let the breakage mail appear on this list to let translators
> informed.

I guess that settles this then. I’ll continue to try and avoid string
additions/changes in the stable branch, as before. Sorry I didn’t
notice this one before merging.

Ta,
Philip