Re: String freeze (was Re: Debian Debconf Translation: Compromise)
- To: debian-devel <email@example.com>, firstname.lastname@example.org
- Subject: Re: String freeze (was Re: Debian Debconf Translation: Compromise)
- From: Christian Perrier <email@example.com>
- Date: Tue, 13 Jan 2004 07:18:32 +0100
- Message-id: <20040113061832.GR12171@mykerinos>
- In-reply-to: <20040112202709.GC32736@zobe.linuxfr.org>
- References: <firstname.lastname@example.org> <20040107161453.GB23118@riva.ucam.org> <email@example.com> <20040107210417.GA3325@quetzlcoatl.dodds.net> <20040108180313.GA31779@zobe.linuxfr.org> <20040109062540.GH6323@mykerinos> <20040109091945.GA14900@projectcolo.org.uk> <firstname.lastname@example.org> <20040109130320.GB17289@azure.humbug.org.au> <20040112202709.GC32736@zobe.linuxfr.org>
Quoting Denis Barbier (email@example.com):
> Sounds fair. I will go through the BTS and collect l10n related
> bugreports so that they can be worked on. If there are other people
How the hell will you do this as there is no "i18n" tag in the BTS
(wild wide ranting)?
I'm prety sure, you'll find a way, Denis....but by losing a lot of
A very valuable DDD will lose a lot of time because the damn i18n tag
does not exist in the BTS.
I maybe am underestimating the work needed and implied by adding a new
tag to the BTS, but this is asked for months now (no BTS currently
available for checking the exact bug number, but it's easy to
find.....this is a BR from Martin Quinson against the BTS).
Other valuable tags have been added in the meantime (d-i,
confirmed...) and I don't really understand why not this one.
Several of us are using tricks (such as [intl:xx] markers in BR
subjects), but that's not really satisfactory as all i18n related bug
reports are far from being marked like this.
And, please don't answer me "DIY". I'm definitely unaware of what is
needed for adding a tag to the BTS. Chacun son métier...:-)