Is there any progress on the task? Have the performance problems been resolved?

In T323430#8539353, @Wangombe wrote:

So far, while the issue can be reproduced, we haven't been able to identify where the second !!FUZZY!! is added from. The poimport.php file is not called as the user interacts with the Special:ImportTranslations page so that might not be the culprit we are looking for. Will keep investigating.

As i see in the scripts/poimport.php, the importing of fuzzy translations strings is doing with such code:

			// Fuzzy messages
			if ( preg_match( '/^#, fuzzy$/m', $section ) ) {
				$translation = TRANSLATE_FUZZY . $translation;
			}

This is categorically wrong, because this kind of "dirty hack" does not recognize the fact that existing translations can be already marked as fuzzy, which causes duplicate !!FUZZY!! tags. Marking should not be done by the import script in this way, but with src/Synchronization/MessageWebImporter.php, where it should be done with the translate-manage-action-conflict as default action for fuzzy strings.

Was fixed in Qt 5.15.6, but the ARM build is still needed

In T199497#4479796, @Petrb wrote:

I actually think that Huggle can do most of the requested features.

1. that's basically checking the diffs of edits with specific filter isn't it?
2. you would need to describe how to do that, but probably can be scripted
3. well, that's basically just a normal revert or not? Does the content model of TWN prevent rollback API or reverting of edits?
4. Can be done simple
5. If you explain or describe some APIs that can do that it can be scripted
6. Can be scripted too
7. That's already implemented

So, I think Huggle can do all of that, but there might need to be some scripting involved.

In T199500#4422234, @Petrb wrote:

Hm, any ideas how to do that? Which APIs should be used for that and based on which conditions? I suppose it should be related to different content model?

In T200637#4459976, @Petrb wrote:

hmm, I wonder why there is any such "unbreakable space" thingie? how about HTML? https://en.wikipedia.org/w/index.php?title=User:Petrb/test1&diff=852487179&oldid=852487100

ok, then let's exclude the use of warn users functions and if in Huggle there will be exactly the functionality that I described above, then we connect it to read-write. I think Huggle can be used in that cases and functionality is not much needed to be coded

What features would I like to get using Huggle on TranslateWiki:

1. Ability to track new and edited translations in languages that will be set by me (with diff view)
2. Ability to edit translations from queue as with Special:Translate page as action=edit
3. Ability to rollback incorrect translations in cases of vandalism or machine translation
4. Ability of placing pages on speedy deletion with {{Delete}} template
5. Ability to review translations (like patroling)
6. Desirable: ability to mark translations as fuzzy (by adding !!FUZZY!! at the beginning of the article text)
7. Optionally: ability to warn users, who make vandal or machine translations

Yes, there is no need fol a lot of special or warning templates, https://translatewiki.net/wiki/Template:Delete is enough.

Great, so you just need to get consent :) And implement filters in Huggle, that can use translations=only and trailer=/$language in filters options

Let ask them. As I know there were a lot of vandalism/machine translating edits on TranslateWiki, especially in the Russian language section, so Huggle monitoring may be extremely useful for this project. @Nikerabbit, can you implement this?