Hello,
On Mon, Jan 04, 2010 at 07:57:37AM +0100, Christian PERRIER wrote: > > (thread originating in #562708 : the main point being that translation > status tools such as l10n status pages do refer to unstable while some > team do their development in experimental) Gathering the material from experimental is already possible for the i18n scripts (i.e. the one generating http://i18n.debian.net/material/) It would also be easy to generate statistics from the experimental distribution (i.e. the same statistics as in http://i18n.debian.net/debian-l10n-stats/unstable/year/main.html) However, translators usually use (and should use) the pages such as http://www.debian.org/international/l10n/po-debconf/fr It would be more difficult to merge there the information from experimental without: * a single way of handling experimental by maintainer * an hard coded list (resp. blacklist) of packages for which the data from experimental should be merged (resp. should not be merged) I've seen experimental used by some maintainers to start packaging a new upstream version while the branch in unstable still evolve for a long time, and where the translatable content in experimental is not ready at all (and not really taken care of at that time). Another idea could be to indicate (with a small character/icon) in the pages like http://www.debian.org/international/l10n/po-debconf/fr that an experimental package (with an higher version) exists with an incomplete translation (and the package would be raised in its list, as are the packages with errors currently). This would let the final decision to a human being, which would make me more comfortable currently. Best Regards, -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org