No need to. We usually "bogus" translation bugs, it's simple not up-to-date and there are other tools for the translation team to see that.
We shouldn't bogusify all translation bugs. A typo is a typo. The best is to leave the bug to the translators.
But when it is simply outdated, there is no need to leave the bugs open, as
we have revcheck.
Right, and that's the case here. We can perhaps add subcatgories for the different translations, so that the correct mailinglist get's the email. Whould that work?
a BIG yes.
For a short term solution, yes. In the long term, it would be nice to be able to classify bugs in more dimensions. Website bugs need different categorisation depending on who operates the particular site. Most of the people on the website ML cannot do anything with a talks.php.net bug for example, or a bug on a mirror site...
Goba
