> > > Proposed solutions which does not work well IMHO: > > > - keep as we are: bugs are repported against the package containing it: > > > every translation team have to have the needed manpower to monitor *all* > > > bugs submitted against *all* Debian package. > > > - keep as we are, but use the 'upstream' tag for translations issues. > > > That means that translators are denied the use of the BTS and have to > > > handle bugs without the coresponding tools. > > > - don't use the BTS, but the bug tracking system from the DDTP: > > > works only for pkg descriptions, debconf templates (?), and so, but not > > > for man pages, program messages, and so on. > > > > one note: > > The bug tracking system from the DDTP work for debconf templates, but > > the package maintainers don't know all this translations and they > > don't use this translations. > > What kind of debconf templates are you translating? The ddtp page is not > clear about that, and I seem to remember that you still translate debconf > templates of the old generation, ie, the ones handled by debconf-utils. you can btw test the first files, see http://ddtp.debian.org/debconf/template_unstable/base-config/templates-de.po Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debsupport.de PGP: finger grisu@db.debian.org -- Linux Sysadmin -- Use Debian Linux Perl ist der geglückte Versuch, einen braindump direkt ausführbar zu machen. -- Lutz Donnerhacke
Attachment:
pgplpwP9CnN6A.pgp
Description: PGP signature