Readding a string recently removed == breaking string freeze ?
Geert Janssens
janssens-geert at telenet.be
Thu Nov 18 12:20:21 EST 2010
On Thursday 18 November 2010, Mark Haanen wrote:
> Op donderdag 18-11-2010 om 15:47 uur [tijdzone +0100], schreef Christian
>
> Stimming:
> > Zitat von Geert Janssens <janssens-geert at telenet.be>:
> > > This is related to bug
> > > https://bugzilla.gnome.org/show_bug.cgi?id=634906. (...)
> > > Restoring the option also means re-introducing the translatable
> > > strings. Although they used to be translated, they aren't anymore now.
> > > So I guess restoring the option results in a string freeze break,
> > > right ?
> >
> > Technically, yes, but it concerns only those translations which have
> > done a "msgmerge" in the time since 2.3.16. This is happened only for
> > nl.po, the Dutch translation by Mark Haanen. He's been the most active
> > translator, so I guess he will even pick up the re-adding quite fast.
>
> I was under the impression that the translations for obsolete strings
> were kept with a ~-prefix, in which case it should pose no problem at
> all...
>
> Push comes to shove, I'll send the adjusted translation straight to this
> list.
>
> --
> Mark
>
Mark,
It looks like you know it best. The strings are indeed still in the po file,
prefixed with a ~.
I have now restored the option (in r19828). I assume the next pot file update
will remove the ~ prefixes ?
Geert
More information about the gnucash-devel
mailing list