yes I had to add this "versions" parameter. Because I need to separate what texts TTS file contain. I decided to always do internal version of texts based on common translation and also these TTS files. If I find TTS file in users language and in version that contain required feature, i'll use this file, otherwise internal translation will be used.
So to be more specific. If user enable TTS for POI alert and has set Japan as langauge, I first check for ja.tts file, then if this file is in version 2. If any of this is not success, I'll use texts generated from translation from crowdin. Simple and I'm sure it will work.
I also spend quite a lot of time on making whole TTS indepenent on navigation, so I think, we should now extend TTS to other tasks in Locus if there will be need ...