Context:
An alternate suggestion I came up with: if an edit is reverted explicitly (via undo, rollback, or some other tool, or maybe even manual reverts), the new version has the fuzzy status copied from the old version. This means that is an outdated translation unit is vandalized, and the vandalism is reverted by some translation-unaware tool then the outdated status would be preserved.
Conceptually the opposite of T367932 (handling fuzzy status correctly when the source text is reverted)
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Update fuzzy and transver tag properly on undo or rollback | mediawiki/extensions/Translate | master | +284 -4 |
Change #1088925 had a related patch set uploaded (by Pppery; author: Pppery):
[mediawiki/extensions/Translate@master] Set fuzzy status to status of prior revision on undo or rollback
The patch related to this task has been reviewed but since this change might have unforeseen side-effects, we want to avoid deploying it before the holidays. Will merge the patch in, in early Jan, 2025.
Change #1088925 merged by jenkins-bot:
[mediawiki/extensions/Translate@master] Update fuzzy and transver tag properly on undo or rollback
(Sorry for the delay, I somehow missed that ping)
Test case on Wikimedia Commons, a wiki that hasn't restricted unfuzzy:
An IP unfuzzies a translation unit: https://commons.wikimedia.org/w/index.php?title=Translations:Commons:Wiki_Loves_Folklore_2025/79/uz&diff=prev&oldid=994572145
I make a dummy edit to make MediaWiki happy: https://commons.wikimedia.org/w/index.php?title=Translations:Commons:Wiki_Loves_Folklore_2025/79/uz&diff=next&oldid=994572145
I use "undo" to undo both our edits: https://commons.wikimedia.org/w/index.php?title=Translations:Commons:Wiki_Loves_Folklore_2025/79/uz&diff=next&oldid=995681473
The manifestation of my edit restores the FUZZY tag: https://commons.wikimedia.org/w/index.php?title=Commons:Wiki_Loves_Folklore_2025/uz&diff=prev&oldid=995681599
And you can also see in the translation UI that it also restored the transver.
That confirms the patch has at least minimally made it to production. I could repeat the other automated test cases on some production wiki but I don't see what that would accomplish. I spent a long time looking for vandalism to a fuzzy tunit in production to revert or see others reverted, but either it didn't happen or my search-fu wasn't good enough.