That’s all well and good with the semicolons as separators and it may make sense in some cases.
Nevertheless, I find it somehow selfish from the renderer’s point of view to want to have more options at all costs and to offer the user a user-specific map with names from the user’s supposed preference. This ignores the efforts of genuine bilingual or multilingual regions and the local community, which consciously use multilingual names in the name-tag for very specific reasons, often especially cities and municipalities use these multilingual names highly officially.
If it’s just a matter of making the display of multilingual names in the map image “nicer”: well, my computer science studies were 30 years ago now, back then I was still programming with Turbo Pascal and C++, and today I don’t know anything about it anymore. But I assume that almost all multilingual names also have the specific name:*** tags in the name tag. This allows the name-tag to be broken down into its language-specific components and then reassembled individually, in the desired order or among themselves and with any desired separator.
I even managed to do this with the example of “Cottbus - Chóśebuz” with a small Excel table (data basis: copy of the place=city - node from the editor):
The whole thing works without a single semicolon! So without a semicolon in the name, for the formulas in Excel sheet you need one or the other semicolon of course 
I have not yet taken into account the French name just added by a colleague. 
Translated with DeepL Translate: The world's most accurate translator (free version)