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

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

Moderators: rondesta, support, adriansinger, Unholy, krankyd, Jackson, The Fej

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

Postby rcenteno_davis » Sun Jan 06, 2013 6:37 pm

I have confirmed (as others) that Intl is pronounced as "Intel". So, despite what the road signs say, should we expand Intl as International (for airports)?
Area Manager: Union City, Fremont, Newark CA
Image
rcenteno_davis
 
Posts: 30
Joined: Sun Jul 22, 2012 2:53 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby Wolfeye » Sun Jan 06, 2013 7:21 pm

Int might work for international?
IA is also an abbreviation for international airport.
Image
INTL: Sweden, Hörnefors-Umeå
Area Manager: Umeå
Waze Champ: Sverige
Svenska Wikin
Wolfeye
 
Posts: 283
Joined: Thu Jul 14, 2011 10:21 am
Location: INTL:Sweden, Hörnefors-Umeå
Has thanked: 1 time
Been thanked: 3 times

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

Postby jasonh300 » Sun Jan 06, 2013 7:28 pm

Wolfeye wrote:Int might work for international?
IA is also an abbreviation for international airport.


I don't think Int is any kind of standard abbreviation for International. IA is the abbreviation for the state of Iowa, so that wouldn't work in the U.S.

How about Int'l?
Image
New Orleans, Louisiana Waze Champ, USA Region 4 Coordinator (South-Central)
Points & Beta Editor Expert.
Waze FAQ ... Best Map Editing Practice ... Waze chat on IRC.
jasonh300
Waze Champs
 
Posts: 5658
Joined: Fri Oct 28, 2011 4:26 pm
Location: Region 4 Coordinator - New Orleans, LA USA
Has thanked: 73 times
Been thanked: 212 times

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

Postby CBenson » Sun Jan 06, 2013 9:26 pm

The last time I checked Int'l was sounded out as "Intel" as well.
Routing Expert
Area Manager: Annapolis, Maryland, US
Verizon, Droid Razr Maxx HD, Android 4.1.2, Waze 3.6.99.110
CBenson
Waze Champs
 
Posts: 3981
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 119 times
Been thanked: 133 times

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

Postby txemt » Fri Jan 11, 2013 9:23 am

I have confirmed, today, that "SH" for "State Highway" is NOT working. :(
Just wazeting my time to help you waze your route smoothly.
Area Manager for Texas.
Country Manager for USA
Tapatalk--can I shoot the person who got me addicted to this?

Image
txemt
Experts
 
Posts: 2029
Joined: Tue Jul 17, 2012 7:03 pm
Location: San Antonio, Tx
Has thanked: 11 times
Been thanked: 195 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 12:56 pm

txemt wrote:I have confirmed, today, that "SH" for "State Highway" is NOT working. :(


Correct. Along with "SH" I have also just tested for "SH-123" also, and can re-confirm that is still does not work either.

I've also tested for various forms of abbreviations for "Township" and "Township Road" and did not find any that worked.

I'll add these results to the list shortly.

What I did discover was another anomaly, for differing results between the two audio files that are created for any given segment. One file always says just the "Street Name" property contents, while the other file says, the word "At" followed by "Street Name" property contents.

The test for "SH-123" resulted in one audio file that said "At ess-aitch one two three" and the other file said, "ess-aitch one hundred twenty three". Very curious.

The last such similar anomaly was with a test of “Borough”, “Parade”, and “Parish”, by using the abbreviations of "Boro par ph".

One file said "At borough parade phone, and other other said, "borough par pea-aitch".
Image
CM: U.S.A./Canada
AM: NW Ohio, NE IN, & SE MI tri-state area.
Waze Champ, etc.
Verizon: Samsung Galaxy Nexus/Android 4.1.1 & iPad "3"/iOS 6.0.1
GizmoGuy411
Waze Champs
 
Posts: 852
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 2 times
Been thanked: 7 times

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

Postby AndyPoms » Fri Jan 11, 2013 1:13 pm

Pkwy confirmed by several people as Parkway.
Image
Waze Champ & Forum Moderator
USA Country Manager & Region 1 Coordinator: Alaska, Idaho, Oregon, Montana, Washington, Wyoming
Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Champs
 
Posts: 3330
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 15 times
Been thanked: 150 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 2:07 pm

AndyPoms wrote:Pkwy confirmed by several people as Parkway.


Andy, do you happen to know which capitalization variations were confirmed?

Unfortunately, the TTS results are often defendant on capitalization, punctuation, and position with other words, not to mention the other issue I just mentioned in my previous post.

These make the TTS list that much larger and complicated, as most of the early tests did not take any of these depandancy issues into consideration.
Image
CM: U.S.A./Canada
AM: NW Ohio, NE IN, & SE MI tri-state area.
Waze Champ, etc.
Verizon: Samsung Galaxy Nexus/Android 4.1.1 & iPad "3"/iOS 6.0.1
GizmoGuy411
Waze Champs
 
Posts: 852
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 2 times
Been thanked: 7 times

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

Postby CBenson » Fri Jan 11, 2013 2:33 pm

"Pkwy" with the initial capitalization and no punctuation (as used here) gives me TTS of "parkway."
Routing Expert
Area Manager: Annapolis, Maryland, US
Verizon, Droid Razr Maxx HD, Android 4.1.2, Waze 3.6.99.110
CBenson
Waze Champs
 
Posts: 3981
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 119 times
Been thanked: 133 times

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 S3 (4.1.1)
Waze Version: 3.6.0.0
Country Manager: Canada
Area Manager: Greater Toronto Area
hmarian
 
Posts: 164
Joined: Mon Jan 25, 2010 4:46 pm
Has thanked: 0 time
Been thanked: 2 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: CopGTP