Reported by McDutchie at https://translatewiki.net/wiki/Support#Can_we_stop_offering_notranslate_messages_for_translation?
Description
Details
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Tag {{notranslate}} messages as ignored | Pppery | translatewiki | master | +8 -0 |
Related Objects
Event Timeline
This is an absolutely ridiculous situation - there are thousands of messages where the "ignored" or "optional" status is inconsistent with the templates in the documentation.
See P94102.
Generated by code in P94103
(This is far bigger a problem then I care to systematically deal with, so unassigning myself)
I did the specific case of {{notranslate}} -> ignored as that is the one McDutchie complained about and is relatively smaller. I don't plan to do the others as it's more work than the extent to which I care.
Change #1301728 had a related patch set uploaded (by Pppery; author: Pppery):
[translatewiki@master] Tag {{notranslate}} messages as ignored
"ignored" and "optional" are added to the translatewiki.net configuration file manually based on the message content. The message documentation could be a hint but is never the main criterion.
Change #1301728 merged by jenkins-bot:
[translatewiki@master] Tag {{notranslate}} messages as ignored
It would be good, however, to have both reflect the same state, probably the state from the extension (i.e. hide {{optional}} if the message isn’t really optional based on some magic word like {{TRANSLATIONSTATE}}). There is also a more general problem of translatewiki messages not being deleted after the message gets deleted from the repository (which also makes tracking errors in message documentation worse), but that’s harder to solve than this.
Would it be possible to show a warning on import if the documentation contains these templates but they are not marked as optional/ignored in the config, or vice versa? I’m not entirely sure how the import goes, but it contains a manual step, doesn’t it?