[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#512210: lintian: [checks/po-debconf] Extend template check for updated strings



On Mon, 19 Jan 2009 14:54:26 -0800
Russ Allbery <rra@debian.org> wrote:

> Neil Williams <codehelp@debian.org> writes:
> > Russ Allbery <rra@debian.org> wrote:
> 
> >> If I check the generated templates in the binary deb, how do I check
> >> that the string was marked for translation?  We don't want to trigger
> >> this tag on strings that aren't intended to be translated.
> 
> > TBH I was expecting that all questions would be translated - at least
> > the help text (Description), even if not the possible answers.
> > Otherwise, doesn't it tend to indicate that debconf is being used as a
> > registry?
> 
> Private templates are extremely common.  We can't realistically do
> anything that would warn about private templates.  It will just annoy a
> lot of people.

OK, I think there is a way of identifying private templates. It could
be as simple as agreeing (after Lenny) that a particular Description is
uniformly used for all private templates. That would help translators
too. Most already seem to use "for internal use". After all, the
description itself is completely arbitrary as far as internal templates
are concerned.

Indeed, simply adding one line to the test script could be enough:
                next if ($line =~ /^Description: .*[for ]?internal use/);

Which gives: (excluding debconf.templates as you described)

tasksel.templates failed
dbconfig-common.templates failed
linux-image-2.6.24-1-amd64.templates failed
linux-image-2.6.25-2-amd64.templates failed
linux-image-2.6.26-1-amd64.templates failed

dbconfig probably needs an override and the others look like correct checks.

Until there is consensus on the syntax for private templates, the
lintian test could stay at lower severity.

> Description: For internal use only

That would match too - so it would be ignored for the test.

> I think this sort of thing is quite common.

As long as a particular identifier can be used for all (and the lintian
test can provide information on that identifier in the guide text),
that shouldn't be a problem.
 
-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpQ_sdGKfEJr.pgp
Description: PGP signature


Reply to: