I believe that you can block already translated strings so that they cannot be replaced by another translation (I have seen this in other projects using Weblate).

However, your idea of limiting translation suggestions could really hinder the accessibility of the project, and in my opinion, one of the strengths of Lemmy is that it is available in many languages, thanks to the fact that it has always been accessible. As soon as I saw that nobody had translated Lemmy into Basque, I decided to help the developers. And I am aware that some of the translations I did could be improved, because the context is ambiguous and sometimes there are several ways to interpret a text string. But if the translations had been “locked”, I would not have contributed to the project. And I think many users will think the same if that is done.

I don’t know what you think about what I say, but I would like to hear your opinion about it. I think the best solution is to create a group dedicated to translators in Matrix as @nutomic@lemmy.ml said and create a consensus on how text strings should be translated or oriented.