Thank you @Rachel for your investigation on this… I get your point and also agree with your conclusion for now. So this option of having an automated translation is not relevant for now. But I think we could still evolve toward having only one version we maintain and update, and then local versions we ONLY translate basically, especially as we evolve from instance guides to language guides. And we can then use easily DeepL for instance but still check and correct automatic translation.
I will go back to the other discussion to comment more generally on this and your point @lin_d_hop so let’s keep the conversation there : User Guide as a Living Document - how to keep it current/rich/relevant? and there User guide harmonizations : what could be our new common skeleton?