Page 64 of 159

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Oct 31, 2012 9:55 pm
by harling
AlanOfTheBerg wrote:I spell out "Branch" and "Bridge" because Br is a valid abbreviation for both. I've see Brg for bridge, but haven't looked at the list to see if Waze pronounces it properly. It probably does.
I can tell you definitively that Brg = "bridge".

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Fri Apr 18, 2014 12:56 pm
by HavanaDay
sketch wrote:Other considerations too, like do we really want LA to say "Louisiana"? Everyone here says "L A one", "L A forty-eight", and so forth.

I believe the idea was to get this done so we could use state abbreviations for state highways. Not that that's perfect. Some states would prefer SR or SH I'm sure — but the benefit of that is that we could get state-specific shields for every state. BUT of course it won't work for Nebraska.
I would just like to get the generic shield for NC-XX. That would be a good start for me. I think we may have lucked out down here becacuse NC-XX says "enn ceee 'state highway number' and the is how most say it down this way.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Sun Apr 20, 2014 1:13 am
by HavanaDay
CBenson wrote: Can anyone add the period to this road?
Was this posted before or after we talked in chat today?

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Apr 30, 2014 1:45 am
by HavanaDay
I will check again tomorrow on my way home but I think NC-XX is still saying enn cee xx.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Sun May 04, 2014 12:38 am
by HavanaDay
To follow regarding the TTS for NC-XX I have a slightly different experience.

The two that I tested was this

a Ramp off A freeway - Exit 50: NC-51 / Blair Rd
and
a turn onto NC-24 / 27

On the ramp it said "Exit 50 enn cee 51 {pause} Blair Rd
On the turn it said "Turn Left North Carolina 24 {pause} 27

So I think I have experienced the reverse of what was posted above. I take that exit everyday during the week so I will reverify but I am prety sure that was what it said.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Mon May 30, 2016 6:26 pm
by herrchin
PesachZ wrote:Cir was omitted accidentally, I have now replaced it in the wiki list for Jane. Cir does work and is recommended for Circle.
"Cir" appears to have gone missing again from the Jane wiki list?

Hogestown TTS

Posted: Mon Dec 26, 2016 7:58 pm
by HillsSnackBar
Hogestown should be pronounced Hoagstown. As an example in local media: http://fox43.com/2015/10/07/car-slams-i ... unty-home/

Currently, it is being mispronounced as Ho-guesstown.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Aug 17, 2016 2:14 am
by hippocampusLol
Sam Eig was a famous real estate developer in the DC area, and Sam Eig Highway in Gaithersburg MD is an extension of I-370 and a major route. It should be pronounced "Sam Eyeg" but the last name is currently spelled out instead.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Fri Jan 11, 2013 3:49 pm
by hmarian
The same for me.
"Pkwy" is reading out "Parkway" on the client and is more consistent with road signage.
Could someone finish this test and add to the TTS Log FIle?

Once it is done there will be some work to change the segments to Pkwy.

Thanks,
Hagay.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Tue May 14, 2013 3:33 pm
by hmarian
I support jasonh300 and think it is not such a great suggestion.
Working with Waze to fix this is the way to go.

Hagay.