I agree. I do translations myself, and this is a problem. Unfortunately there is no obvious solution. I don't think that we can remove a page from the translation system once it has been added (other than possibly by deleting existing translations, which might create even more problems).
We could create a Category for such pages, but that would only be useful if we remember to check that a page is not in this no-translate category before starting to work on it. Do you think it would be a good idea to do that?
Hi Claus, Thanks for having answered. I would avoid multiplicity of categories. When one translates, it moves generally all categories from the EN page to the translated page (that is the local one) which at this second level becomes a nonsense (i have seen cases 'this category is only for the main/EN page' and I was attempting to recopy it on the FR page!).
If you know -thanks to your experience- that a page is obviously not good, i would rather recommend you to write a warning/comment at the top of the main/EN pages saying something like "Do not translate yet ! this page is too old and needs to be reactualized before being valid for translation." without requiring translation. Thus the process is locked at the level of the EN page. And when I check the FR pages to be translated, I dont see in the statistics this page which is still waiting for validation, because I am aligned with the old version. For translators it is better i think. No ?
We do exactly what you suggest with new pages being written. However this is an old page and is already in the translation system. We could add a warning at the top of the page, but the page would still be in the translation system and would still show up in the translation statistics. I'll try to investigate a bit more over the weekend and see if I can come up with something better.
Identifying old pages that shouldn't be translated is a major undertaking and we lack the manpower. Currently we simply deal with pages one at a time as they are reported.