On Tue, Feb 14, 2006 at 09:35:18AM +0100, Christian Perrier wrote: > Sure, if someone jumps on your non translatable templates, then you > may get a bug report asking for marking them as translatable...which > you will then answer by mentioning that you did this on purpose..:-)
Exactly this is what I am trying to avoid. Additionally, the transitions between translateable and untranslateable are a possible source for bugs and errors. And you don't get to check your maintainer and build scrips for correctness if you don't have translateable templates. > > Please, there must be a way to avoid bothering with translations and > > wasting translator's time for a package that is work in progress. > > I think that not marking templates as translatable is the best way to > do so when the package is new and has no existing translations. This will, however, delay discovery of packaging bugs. > > The same issue will come up with exim4 soon. > > Yep. For exim4 the problem is trickier as you already have > translations which you don't want to lose. In that case, I think that > warning debian-i18n is the best thing to do. There should be an automated way to do so, like a "in flux" flag on a package. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
