Mr. Ach,
appreciation for your hints.
The thought is more based on building up on plugin like translate. Edition is actually very similar to it.
If doing and focus on "localization" or if wishing to understand the meaning of a text, it's useful to display, read, "original text" and this or that translation.
When translating it's useful to have the source parallel, scroll while strings, similar like in the comparison view, are on same position.
The certain htlm-solutions, limited to view and would require to put all translations into one page, is no useful way, given it's about tons of text.
As dokuwiki itself has much interest in localization, the team knows the situation, it was thought to be of interest to go after such.
It might work somehow like the comparison view with possible access to modify a string or section for translation easy.
Translations, the certain language, chosen in the dropdown menu might allow the selection of two languages displaying then "content lang-x-ns-page" and "content lang-y-ns-page".
With such a possibility translations can be easier checked as well.
Just visions and since thought of use for many into translation/localization here verbal expressed.
Here sample pages of a text translated:
http://accesstoinsight.eu/en/lib/thai/chah/insimpleterms
http://accesstoinsight.eu/de/lib/thai/chah/insimpleterms
Now if wishing to prove against each other, it's not so easy.
The practical hint by Mr. Michael matches the way people might do it, displaying the whole website parallel for edits. Is not possible for mobil devices and one doing so might know the scroll/sting by string burden, when comparing or editing.