When activated and using imperial (miles and yards) voice guidance with street names provides very specific distances ie.: "After 1.463636363636364 miles, turn left."
When activated and using voice guidance with street names the software reads abbreviated directional portions of street names phonetically (i.e. "N Main Street" is read as "nuh main street"). Most US map data has the directional part of street names abbreviated.
I second mclovin's text-to-speech comment. BTW the phone also does this when you ask it to tell the current time ... eg for 9:46pm it'll say "Nine Fourty Six pum". I understand that Maps mobile is beta so there will be bugs like this, but hopefully this time they'll actually fix some bugs before releasing.
I get the same as Bipolarchucker too.
The abbreviations problem should be fixed with the latest voice files we deployed. Please get the latest and greatest voice files from the server and the problem should be gone.
We are constantly working on thoose quality problems and try to enhance the number of available languages for the release.
Actually our TTS implementation is a different one than the device engine, so we can fix the bugs independantly and hopefully quicker ;-)
Please don't stop to post....
My voice file is only about a week old and still does it.
mbrett
N97 RM-505 (Product Code: 0585262 (Vodafone UK)) FW 11.0.021
N95 8Gb (Product Code: 0558787 (UK)) FW 31.0.015
A week is old ;-)
I just downloaded the new voice file yesterday (English UK with street names) and I still have the abbreviations problem. My particular example: For highway named "N Capital of Texas Hwy" it says, "En Capital of Texas Highway". Seems like the postfix abbreviations are fine, but the prefix abbreviations are said as-is.
And it still says all 16 or so digits of precision for distances. Cracks my friends up every time, but it's getting pretty annoying to me.
Ravi