It has not been the plan: it is a deliberate choice not to do that.
The choice I made was to prefer to support translation (and to continue to improve it as ideas like this come in) rather than have different - even possibly conflicting - descriptions in different language.
Another factor is the sheer availability of translators for OJE. If we chose the “separate translations” path initially, then OJE would have been bare of translations, and sparse indeed for a very long time.
It may be that we are at a tipping point now, I’m not sue.
So it’s technically possible of course, but it will take persuasion that it is the right thing.
This is something we’d really love to support.
If the only way to “remove this barrier” were to have different text in different languages - maybe with a translation provided if there isn’t text in a language - then this is something we should look at.
Am I right in understanding that the essense of the barrier is “achieving natural sounding language with correct terminology”?
I would like to “prove” that we can not do that with prompting before resorting to separarate translations. We had reasonable success with system warnings this way, at least with the “target languages that were complained about”, so it seems conceivable, although Mandarin might be “the hardest we’ve yet to try”.