Michal Čihař

The removal should happen by Memory id. It is currently not present in the response, it can be added here (`result.id`): https://github.com/WeblateOrg/weblate/blob/8b97ddaf6b709ffc90485069443c03852378df8e/weblate/memory/machine.py#L68-L74 The client side code to handle this is...

I've just touched related code in dc8266f08def4b03070b17f31712afa8e702d67f and I think the correct approach would be to include removal URL in the response and let the client side handle the removal...

Merged, thanks for your contribution!

I'm not really sure how to deal best with the comments as even current two scope comments seems to be quite unintuitive and bringing another comments into that will probably...

Is this related? https://docs.weblate.org/en/latest/admin/machine.html#youdao-zhiyun-api-machine-translation

Okay, I got confused by zoudao and youdao :-)

Isn't it better for all Python documentation localization to be in a single place? This brings numerous benefits - for example, it is easier to find problematic source strings or...

The problem here is that the "temporary workaround" means quite some development in Weblate. I don't mind getting a pull request implementing this, but it is certainly not something we...

Yes! What needs to be done: * Add new event to the `Change` model to track these (ACTION_STRING_REMOVE) * Adjust delete endpoints to generate change entry Once this is done,...

Thanks, this looks nice. There are few issues with this, though: - the current selection includes all components in the current project, and all with enabled contribution to shared TM....