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

Bug#387360: [checks/po-debconf] Invalid files in debian/po directory



Russ Allbery <rra@debian.org> (13/09/2006):
> Thomas Huriaux <thomas.huriaux@gmail.com> writes:
> > Russ Allbery <rra@debian.org> (13/09/2006):
> >> > W: dpkg-www source: unknown-po-debconf-file debian/po/cs.po.Miroslav_Kure
> >> 
> >> This is an example of an extra file that, on its surface, seems
> >> legitimate.
> 
> > This looks more like an old translation that could be removed.
> 
> Well, yeah, but apparently the maintainer wanted to keep it around for
> some reason.  I may not agree as a maintainer -- it just seems like the
> sort of thing that I could see someone doing.

I don't know, it looks like a misunderstanding introduced by a bad
language code (#293781). The problem is also that if there was no
cs.po file, this outdated translation could have been useful (but this
is not the case here).

> > My main purpose by writing this patch was to detect the following files:
> >   W: setserial source: unknown-po-debconf-file debian/po/setserial.ja.po
> >   W: setserial source: unknown-po-debconf-file debian/po/setserial.pl.po
> > Those one introduce the following fields in the master file:
> >   Description-setserial.ja.UTF-8:
> >   Description-setserial.pl.UTF-8:
> > The translations are then lost (unless a ll.po file also exists, which
> > is here the case for ja but not for pl).
> 
> > or
> >   W: vtun source: unknown-po-debconf-file debian/po/vtun_2.6-3_ja.po
> > introducing the Description-vtun_2.6-3_ja.UTF-8: field
> 
> Would we catch most of these issues by looking for badly-named files that
> end in .po?

If we have a look at the full list, here are the files introducing wrong
fields:
  W: norwegian source: unknown-po-debconf-file debian/po/norwegian-cs.po
  W: setserial source: unknown-po-debconf-file debian/po/setserial.ja.po
  W: setserial source: unknown-po-debconf-file debian/po/setserial.pl.po
  W: vtun source: unknown-po-debconf-file debian/po/vtun_2.6-3_ja.po

The best solution may be to catch files only containing the string
  [_.-]po([_.-]|$)

The *~ files should probably be catched in a more general check.

Cheers,

-- 
Thomas Huriaux

Attachment: signature.asc
Description: Digital signature


Reply to: