I'm willing to spend some time fixing it in OSMAnd. I just need some input from project devs so i don't reinvent the wheel doing it.
Just take a look at how many modifiers are available for numbers in TTS: https://developer.android.com/reference/android/text/style/TtsSpan.html - all our beautiful languages should be covered. W dniu czwartek, 20 października 2016 19:10:18 UTC+2 użytkownik Karol Grudziński napisał: > > Hi, > This problem exists in another navigations too. I experienced the same > issue recently in Magic Earth, when it said "Jedź prosto, następnie skręć w > czterdziestu czterech" when it obviously should say "Jedź prosto, następnie > skręć w drogę numer 44" ("Drive straight, then turn in road number 44"). I > think our beloved Slavic languages are really hard for voice/language tools > :) (e.g. EN->PL translation in Google Translate sometimes gives really > funny results). > > W dniu czwartek, 20 października 2016 10:13:41 UTC+2 użytkownik gdr gugiel > napisał: >> >> Hello, >> >> I've been using OSMAnd with Polish TTS quite a lot recently. While the >> quality is usually good, there's one annoying feature which sounded >> ridiculous to the bystanders. >> >> It's how it reads "turn left into 297th" - which obviously means road >> #297. The Polish translation is incomprehensible ("skręć w lewo w dwieśćie >> dziewięćdziesiąty siódmy"). >> >> My question is: is it possible to distinguish road numbers in ttsconfig.p >> so that it reads "turn left into road number 297", like all other >> navigation apps do? I can contribute the translation and figure out the .p >> file syntax and make a pull request if that's possible. >> >> Regards, >> GDR! >> https://gdr.name/ >> > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
