Quoting Ian Jackson (ijackson@chiark.greenend.org.uk):
> Christian PERRIER writes ("Re: Bug#660965: Exploring the possibility of an l10n upload of xfonts-traditional to fix pending po-debconf l10n bugs (and debconf templates changes)"):
> > But, as there are many packages which I want to focus on (with the
> > release in perspective), I would really love to have one less..:-)
>
> How about you focus on a different package and if I haven't done
> anything reasonable within the next few weeks you do an NMU if you
> feel like it. To be honest there are other packages whose users are
> much more likely to benefit from you translation effort and I would
> urge you to spend your time there.
Well, OK. This doesn't have my preference but I always give
maintainers opinion the priority about these topics.
My main problem comes when all maintainers do the same
answer..:-). I'm then left with always the very same set of packages
and I'm supposed to wait petiently for maintainer's good will..
Anyway, the freeze hasn't started so I'll move to other targets but
that's a matter of weeks....
> > On the other hand, I'm reluctant to NMU because I still have doubts
> > that the very final version of debconf templates is really what you
> > want to have. Also, I'm reluctant because NMUing a quite active
> > maintainer is not something I'm really happy to do...
>
> If you don't update the English language texts then I have no problem
> at all with an NMU. If I do update the English language templates
> myself later, I can unfuzz the translations myself (since you have
> helpfully told me how to do that).
The main problem is: if I don't change English texts *at all*, then
translations *will* be fuzzy as they're based on other (significantly
different) texts. So, if you apply English changes later, particularly
if you do to use all changes which the translations are based upon,
then the risk of inconsistency between English and translations
grows....and unfuzzy is maybe not the good solution (or maybe even not
possible, for instance if the number of strings changes).
So, really, it's much better if English changes *and* translations
come together. Thus, I'll leave them up to you, including the unfuzz.
Thanks for your quick answer, as my main goal was to raise the
incertainties I had with this package.
Attachment:
signature.asc
Description: Digital signature