Quoting Marc Haber ([EMAIL PROTECTED]): > On Tue, Feb 14, 2006 at 08:05:21AM +0100, Christian Perrier wrote: > > Then, please do no mark templates as translatable instead of using > > tricks. > > The last time I uploaded a package with templates marked as > untranslateable, this resulted in a "please apply patch to allow > translation" bug in no time.
:-) Sure, the context may vary. The main "problem" is now that as soon as translatable templates reach unstable you'll get some translators working on them....so I prefer recommending not marking work in progress as translatable. 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..:-) > 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. > 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
