Zombie translation memory

[emmapeel2]

When I started our project in hosted.weblate, I imported a lot of components that needed to have the English strings when there was no translation present (mostly .dtd and .properties files for our Firefox derivative, and also some .json files)

Once I configured them to use the Add-ons:

• Prefill translation with source
• Flag unchanged translations as "Needs rewriting"

And I did a bulk edit to mark the strings with check:same as Needs-editing.

Since then, I have tried to remove the english versions of the strings from the memory, but they keep coming back.

In the Automatic translations tab, sometimes there is a button that offers me to remove a memory entry. But on some other entries from my own project I am unable to remove that entry.

Question 1: How can I configure my translation memory so I always get the orange button to remove an entry from memory?

• I marked translations as 'needs edit' and clicked on the 'Rebuild' button for the translation memory of a component.
• I also configured it not to " Contribute to project translation memory " on Settings/Translation.

I still see suggestions from that memory! For example here: https://hosted.weblate.org/translate/tor/tor-browser/tb-torbuttondtd/kn/?checksum=8f5393fbcef5e712 in the Automatic translation tab I see a zombie suggestion from "Weblate Translation Memory (Shared: tor/tb-torbuttondtd)".

Question 2: How can I get rid of that translation memory?

I feel that memory got stuck in limbo when I moved the component inside a Category, but I am not sure.

[emmapeel2]

Here another string with Automatic suggestions that I cannot remove: https://hosted.weblate.org/translate/tor/tor-browser/tb-tor-browser-ftl/km/?checksum=1b1577d139f1930f

They are coming from a component supposedly from my project Weblate Translation Memory (Shared: tor/tb-aboutdialogdtd) but they don't have a link and I don't get the remove button.

I used to have a tor/tb-aboutdialogdtd component, but it does not exist anymore. How can I prevent that Translation Memory to appear? My problem is because that memory has English strings as translations, which was needed for that component but is not needed on the new components.

[nijel]

#18867 might outline a way to deal with this.