Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Tue Dec 31, 2013 10:13 pm
OK. I'll make sure you get added. Thanks for your interest.qwaletee wrote:Android. Very old version if that matters (time for an upgrade!)
Waze: outsmarting traffic together
https://www.waze.com/forum/
OK. I'll make sure you get added. Thanks for your interest.qwaletee wrote:Android. Very old version if that matters (time for an upgrade!)
I'll add you to the list as wellPhantomSoul wrote:I'll try the new voice if you still need testers. iPhone here.
I guess you didsketch wrote:I'll try it too, if you need me. I have an iPhone.
Is there a thread for this somewhere I missed?
I sent the email. I'll check and let you know.sketch wrote:It's not there in my client.
This is regarding the BUS issue.We need to create a rule to override it in the server at this time it didn't work and our developer is trying to fix it
How about this?whatnt wrote:No. Long e's and emphasis on first syllable. And hard V like vē.
'lēvs-lē
Just to another to the list, travelling up onto the Hutchinson River Pkwy N from the Whitestone Brg produced a "Hutcinson River Parkway enn" Verbal instruction on March 24th. Mentioned in the UR there.AlanOfTheBerg wrote:My thought exactly. I defined the rule similarly to how N=north is defined, which is different than all the other cardinals, which may also explain why @txemt has noted that is seems "xyz Pkwy N" pronounces "enn" rather than "north." I will be checking on this.sketch wrote:Interesting. Wonder if it's relevant that it's the last word in the string.