Neil Williams <codeh...@debian.org> writes:
> 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.
Well, it shouldn't help translators because those templates should not be
marked as translatable anyway. It would just be an additional requirement
that we're adding for people writing debconf templates so that they don't
get Lintian warnings.
> Most already seem to use "for internal use". After all, the description
> itself is completely arbitrary as far as internal templates are
> concerned.
Some examples of untranslated templates that don't use that string are:
cdebootstrap (a udeb special case)
cpufrequtils
etcinsvk
kickseed (maybe an actual bug)
lowmem
Many of them use variations on it. Those are just the ones that I can
find because they don't use po-debconf at all and hence Lintian currently
warns (but won't after I fix #492626).
Looking in more depth, while Lintian currently uses the internal use part
to suppress checks for grammar and the like, there is currently no check
in Lintian for a template that isn't marked as translatable but should be.
I think we therefore have no idea how many false positives we're likely to
uncover. We could introduce this as experimental first and see what
lintian.d.o digs up, though.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
