I hope this hasn’t been discussed previously (I did a bit of a search, but didn’t find anything directly related).
For duplicate cities/suburbs which have states in the name field, the TTS does not always pronounce the names correctly (ACT, for example, which it pronounces as the word “act”, rather than the abbreviation “A.C.T.”).
I would like to float the idea of adding periods to the troublesome states/territories to force Waze to enunciate the abbreviation correctly.
The variations can be tested here: http://www.nuance.com/vocalizer5/flash/index.html
In my view, TAS, ACT and SA should be corrected with periods and the rest of them are ok (and I’m assuming Vic is better pronounced as “Vic”, as it presently is, than “V I C”.
Hi Osprey06,
I can’t think of any ACT roads that have ACT in the road name. If its a ramp with a destination, the State/Territory) would be unnecessary. Do you have some examples?
I certainly would not like to see the city names changed to add full stops, they look bad enough on the display when the “, ACT” is included, but if there are just a handful of road names that would be seem ok to me.
Cheers
AliG
Sorry, I meant to Cities, not streets. I updated this error in the post, but forgot the title.
I can’t think of an example off the top of my head, but occasionally I have been given an instruction along the lines of “turn left towards [city name]”, which is when the mispronunciation occurs.
Ahh, ok. Since there is no specific tts language for Australia, we usually go off UK tts language as the road descriptions are closer to ours than USA tts. There has been talk in the Dev forums to give each country a specific lang file (to fix pronouncation issues) , but this hasn’t happened yet.
The limitations of tts language.
