Denis Barbier wrote: > > Do you really need to include the pot file in CVS? Can't it be generated > > from the templates file at build time or when a translator needs a pot? > > Sure it can, but it is much easier for translators to rename foo.pot into > ll.po and work on that file; it could also in the future be retrieved from > a web page similar to the Free Translation Project, visit > http://www2.iro.umontreal.ca/~pinard/po/registry.cgi?team=fr > and click on some program names, a link to the POT file is available.
I'm not convinced. How does having the file in my cvs repository (which is a bit of a bear to access anonymously[1]) make it easier for a translator to get at the pot file, compared with apt-get source; cd source; debconf2pot. Given the simplicity of generating a pot file with that command, there doesn't even seem to be much value in generating the pot file at package build time and including it in the tarball or diff. I've never been asked to put a pot file in cvs for debconf's own po directory, or even include it in the tarball; translators seem to have no problem with make -C po debconf.pot. And if I want to submit a pot to the free translation project, I can just do it, and bloating my tarball with it thereafter becomes even less useful. -- see shy jo, unconvinced [1] http://kitenet.net/programs/sshanoncvs/
msg22225/pgp00000.pgp
Description: PGP signature
