Page 28 of 159
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Mon Oct 19, 2015 7:15 pm
by chyron8472
Been using Kate (UK) for voice nav. When I get on Hwy 75 in Tulsa to head home from work, she calls the town of Okmulgee "Oak-mull-jee."
It should put the emphasis on the" mull", but /primarily/ (and most annoyingly) pronounce "gee" with a hard G instead of a soft J.
Sent from my XT1254 using Tapatalk
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Tue Nov 18, 2014 10:27 pm
by citeman
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Tue Dec 15, 2015 4:49 am
by citeman
Diana Ave, is being pronounced with a short 'i'... it should be a long 'i' - "eye"
https://www.waze.com/editor/?env=usa&lo ... s=69759734
Thanks,
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Thu Oct 05, 2017 4:28 am
by CitizenTraffic
In Tucson, AZ, they use Stravenue (a cross between Street & Avenue)...a lot. Editors have abbreviated it to Stra, and Jane reads it as it is written. It is the USPS recommended abbreviation, which can be found here:
https://pe.usps.com/text/pub28/28apc_002.htm.
Here is a Wikipedia link for it as well:
https://en.m.wikipedia.org/wiki/Stravenue.
Sample of area with several "Stra" streets:
https://www.waze.com/editor/?env=usa&lo ... 435&zoom=6.
Would like to see an abbreviation standard and include it into Jane voice.
Thanks.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Fri Aug 12, 2016 1:43 am
by COBillK
Limon, CO is pronounced "Liemun" (with a long "i" like "die") rather than "Lihmun" as Waze currently pronounces it.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Mon Jan 04, 2016 6:03 pm
by codgerd
Brg is pronounced correctly as 'bridge' when in the course of normal instructions, but is pronounced on my client as B-R-G when it occurs in the little summary spoken prior to starting a route. e.g. "Let's get started! Let's take Burrard B-R-G". Then later, "turn left on Burrard Bridge".
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Wed May 07, 2014 9:26 pm
by coontex
Any thing new on this FM error. We are getting a lot of UR's around the Houston area of this.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Thu May 08, 2014 2:28 am
by coontex
I will have to check on it with some of the UR tomorrow or Friday. I have never had it happen to me on my iPhone so I have started asking the reporters which device they are using to see if it was happening on just certain ones.
Sent from my iPhone using Tapatalk
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Sat May 10, 2014 6:29 pm
by coontex
ctpoole wrote:mdavidsonjr wrote:Any thing new on this FM error. We are getting a lot of UR's around the Houston area of this.
I have had FM work correctly for me recently. I had dumped my cache on my iPhone just to be sure. I haven't had a UR about it in the Austin area for over 10 days. There were 5 or 6 before that. I didn't think to check to see if "FM nnn" and "FM-nnn" work the same. It is always possible that one works and the other doesn't.
Most of the reports I am getting around the houston area are on samsung s5, at least the ones that have replied.
Sent from my iPhone using Tapatalk
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien
Posted: Sat May 17, 2014 2:45 pm
by coontex
How about the fm roads. Has that been fixed yet, still getting a few reports around houston on this one.
Sent from my iPhone using Tapatalk