That means, if there is among Osm road data a substring e.g "85A", Osmand
passes it to the system TTS, supposing it will be pronounced as expected.
Some TTS engines may pretend they know the context better and pronounce the
ending letters as names of physical units, like if it was a technical text.
How the particular navigation pronounces it depends on what system TTS
engine is set to be used on the Android level, and if the application
installs a/o uses any on its own.
On 29 May 2017 06:29:35 Poutnik Fornntp <[email protected]> wrote:
AFAIK, pronunciation of Osm data is not given by OSMand itself, but by used
voice engine, either as Texttospeach, either as prerecorded voice. Try to
install different TTS engine as the default one.
Osmand IMHO just provides additional data to be spoken e.g. as guidance,
that are not in Osm data.
But in case I am totally wrong and osmand has its own engine built in,
anybody feel free to correct me.
--
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.
