On Jun 14, Martin Pitt <[EMAIL PROTECTED]> wrote:

> Please generate a POT file during the package build. This is a
> template file that is used as a basis for translating this software
> into other languages. It is important that the POT file is always up
> to date and exactly matches all the strings (including strings from
> Debian-specific changes), so it is not enough to just put a static one
> into the package. Apart from being used manually, this POT file can
I know. But why should I force rebuilding it if I'm sure that released
packages will always have an up to date .pot file?

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature

Reply via email to