Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Image This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderator: delilush

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

Postby hmarian » Fri Jan 11, 2013 3:49 pm

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.

Device: Samsung Galaxy S8 (7.0)
Waze Version: 4.36.0.1
Country Manager: Canada
Area Manager: Greater Toronto Area, Buffalo (NY), Binyamina (Israel)
Android/WME Beta Tester
-----------------------------------------------------------------------------------------
Editing Manual | Editing Best Practice | @Waze_Canada
hmarian
Waze Global Champs
Waze Global Champs
 
Posts: 4128
Joined: Tue Sep 24, 2013 9:08 pm
Location: Toronto, Ontario, Canada
Has thanked: 267 times
Been thanked: 1777 times

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

Postby HippoCampusLoL » Wed Aug 17, 2016 2:14 am

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.
HippoCampusLoL
 
Posts: 12
Joined: Sun Oct 18, 2015 2:05 pm
Has thanked: 15 times
Been thanked: 1 time

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

Postby herrchin » Mon May 30, 2016 6:26 pm

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?
USA Country Manager / UT and IA SM
ImageImageImageImageImageImage
herrchin
Country Manager
Country Manager
 
Posts: 274
Joined: Mon Jun 22, 2015 6:05 pm
Location: Lincoln, NE, USA
Has thanked: 205 times
Been thanked: 151 times

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

Postby HavanaDay » Sun May 04, 2014 12:38 am

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.
USA CM
Primary Focus Charlotte Metro
HavanaDay
Country Manager
Country Manager
 
Posts: 1148
Joined: Fri Sep 03, 2010 6:08 pm
Has thanked: 216 times
Been thanked: 212 times

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

Postby HavanaDay » Wed Apr 30, 2014 1:45 am

I will check again tomorrow on my way home but I think NC-XX is still saying enn cee xx.
USA CM
Primary Focus Charlotte Metro
HavanaDay
Country Manager
Country Manager
 
Posts: 1148
Joined: Fri Sep 03, 2010 6:08 pm
Has thanked: 216 times
Been thanked: 212 times

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

Postby HavanaDay » Sun Apr 20, 2014 1:13 am

CBenson wrote: Can anyone add the period to this road?

Was this posted before or after we talked in chat today?
USA CM
Primary Focus Charlotte Metro
HavanaDay
Country Manager
Country Manager
 
Posts: 1148
Joined: Fri Sep 03, 2010 6:08 pm
Has thanked: 216 times
Been thanked: 212 times

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

Postby HavanaDay » Fri Apr 18, 2014 12:56 pm

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.
USA CM
Primary Focus Charlotte Metro
HavanaDay
Country Manager
Country Manager
 
Posts: 1148
Joined: Fri Sep 03, 2010 6:08 pm
Has thanked: 216 times
Been thanked: 212 times

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

Postby harling » Wed Oct 31, 2012 9:55 pm

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".
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

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

Postby harling » Wed Oct 31, 2012 4:38 pm

GizmoGuy411 wrote:This sounds like another one of those positional issues. I think I recall jasonh300 saying something before about a similar situation.

I'm not even sure how show in the list that "Br" is sometimes "Bridge" and sometimes "Branch" for the very same road segment, depending on how Samatha feels at the moment. I'll have to think on it.

Whether in the middle or the end of the ramp name, "Tobin Br" (as it appears on the signs) went from "Tobin Bridge" to "Tobin Branch" within the past year. Never mind that it also pronounces it "Tobbin" rather than "Toe-bin"... :-p
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

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

Postby harling » Wed Sep 12, 2012 10:44 am

AndyPoms wrote:
AlanOfTheBerg wrote:I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.
+1 for ease of use...

Been recommending that all along.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users