I completely agree that the main problem here has been resolved for you, @chas521 - but the conversation we're having is still a worthwhile conversation to have, just so we can better understand how things work in order to resolve future issues. And we're also not 100% sure that commenting that one line from the voice file won't have any negative results at some point.

That being said, unless we can change things in the Nuance TTS engine files, there really isn't much we can do about the differences between the WinCE and Android Nuance TTS engines.

Obviously, the TTS engines must be handling things differently if the same voice file behaves differently in Android and WinCE.

By the way, when I test this stuff, instead of trying to plan routes that use the street names you are trying to test, you can simply put what you want to test right in the "testsound" parameter in info.ini. Then, just selecting the voice in iGo will say the word/phrase you want to test. For example, to test these street name issues, I just change the testsound to "1st 2nd 3rd 107th" to see how the voice says the different street names. Much easier than trying to plan a route that touches the streets you want to test! :-) I did the same thing when diagnosing the US/USouth issues I was having. Makes testing these type of voice changes really quick and easy!

I have tons of Android devices, I guess I should setup iGo on one of them, just for testing purposes - would come in handy.

Sent from my HP SlateBook 10 x2 PC using Tapatalk