Hello, I have a user report that states that Bradenton, FL, is being pronounced Brahd-en-ton, instead of the way it should, which is Braid-en-ton. Braid is indeed the correct way. Is this something that can be changed? Thx!
Is there a method for doing this? I see there's a Bradenton Rd in Indiana, Bradenton Ave in OH, for example. No idea how it's said there, though.PesachZ wrote:Theoretically yes it can be changed, but the change will affect the entire country anywhere that word is used. Therefore we must first know if this is something pronounced differently in different regions.BarfmanTheGreat wrote:Hello, I have a user report that states that Bradenton, FL, is being pronounced Brahd-en-ton, instead of the way it should, which is Braid-en-ton. Braid is indeed the correct way. Is this something that can be changed? Thx!
Sent using Tapatalk for Android
Thx
I have a user reporting that voice said Drive instead of Doctor for this segment:
https://www.waze.com/editor/?env=usa&lo ... s=83508873
called "Dr. Martin Luther King Jr St S"
I see that Jr probably needs a period, but why would Dr. say drive?
They were turning right to go north on that segment, and they said it was the default voice.
https://www.waze.com/editor/?env=usa&lo ... s=83508873
called "Dr. Martin Luther King Jr St S"
I see that Jr probably needs a period, but why would Dr. say drive?
They were turning right to go north on that segment, and they said it was the default voice.
It was from June 24. I will provite that fix to them. ThxPesachZ wrote: There was an issue which we fixed, when was the report from.
Tell the reporter to navigate to cc@tts, and it should work properly after that.
Sent using Tapatalk for Android
I have a user saying that Flaghole Rd is being pronounced as Flag Hill Rd. Maybe the TTS is seeing it as Fla-ghole rather than Flag-Hole, and that's making it sound like Flagil. At any rate, is there a way to test this?
https://www.waze.com/editor/?env=usa&lo ... st=4385513
https://www.waze.com/editor/?env=usa&lo ... st=4385513
This wasn't my report, it was from a UR, so I don't know if it is working correctly or not. I will try to have another local editor try it out if I can. ThxPesachZ wrote:Can you confirm this has been fixed now please?BarfmanTheGreat wrote:I have a user reporting that voice said Drive instead of Doctor for this segment:
https://www.waze.com/editor/?env=usa&lo ... s=83508873
called "Dr. Martin Luther King Jr St S"
I see that Jr probably needs a period, but why would Dr. say drive?
They were turning right to go north on that segment, and they said it was the default voice.
Sent using Tapatalk for Android
Mispronunciation of McMullen, spoken as McCullen.
https://editor-beta.waze.com/editor/?en ... st=5060087
User report, and the TTS engine in the editor reproduces it.
bmtg
https://editor-beta.waze.com/editor/?en ... st=5060087
User report, and the TTS engine in the editor reproduces it.
bmtg
Any update on NE being pronounced "Nebraska"? My office is currently on the corner of "Nebraska 17th Court" and "Nebraska 14th Avenue" according to Waze.
"NE 38th St" does not have the issue any longer for some reason. Maybe because it's "St" rather than "Ave" or "Ct"?
"NE 38th St" does not have the issue any longer for some reason. Maybe because it's "St" rather than "Ave" or "Ct"?
I just cleared the cache for the app. I'll see what it does at lunch and then send you a map link if the problem is still there.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien