Continuing the discussion from Backend translations current state:
For the UI translation, a lot of labels need to be created. We need a scheme to address them and will have to find the right compromise between re-using labels and spot-on translations.
Having the exact same string in two labels is not a big problem, as Crowdin will hide those by default and re-use the translation of one for the duplicate(s). And of course when translating the translation memory will suggest things that have been translated already.
But when adding translate VH calls to templates, it would be helpful if one could reuse labels that exist (like
clickToDelete) instead of having to add them to the XLIFF files again and again.
Right now it is too hot here for me to come up with a suggestion, but at least the topic has been brought up now.