Support for translated versions of Flight Simulator was "somewhat" introduced in version 5.3.1. What this means is EditVoicepack can now store phrases in multiple languages, and apply the correct string based on the language of Flight Simulator being used.
The problem is the translations - I simply do not speak German, French, and Spanish - so I can't write the translated text.
This gives 3 possibilities I can think of:
1) Professional translation.
Giving the technical requirements for the translation (it's not simple sentences) this is somewhat expensive compared to the revenue generated from EditVoicepack.
2) Crowd Sourcing.
I already attempted to build this into Evp, and did get the first string translated.
But it has some problems: a) It is not visible enough, b) Not enough users run EditVoicepack often enough with translated Flight Simulators (many users only run it once). I can fix a), but due to b) I am not convinced it is the best use of my time at this moment - spending time here would delay another important feature.
3) Someone volunteers to translate the phrases.
Not exactly a fun task, and it is limited what I can pay (a free license of Evp for sure, but that is pretty much it).
The mentioned limitation is for the phrase field - so what is written in the ATC dialog. As Flight Simulator is somewhat dated
it use a problematic way to handle text. So if for example ö is used in the phrase, a Japanese system would not be able to display it. As the English version is used throughout the world, it has to be restricted to text that all systems can display - which means the ASCII character set.
The same limitation does not apply to the translated phrases. Microsoft made the (reasonable) assumption that the German version would only be used on a system running the default German code page (which determines how old applications like Flight Simulator displays text). So the German phrase can contain the typical German characters.