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: MapSir

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

Postby orbitc » Thu Jan 31, 2013 4:17 am

Thanks a lot for these extensive tests GizmoGuy411.

As you may know, we've tested couple of options as well. I believe, -if that's OK to proceed- we should go ahead and change those roads with single letter like Avenue S to Avenue 'S'. It seems that's the general consensus at this point.

Also, one might argue, while we are fixing Avenue 'S', why not change it to Ave 'S'
Regional Coordinator for Northeast (DE, NJ, NY, PA) & New England (CT, ME, MA, NH, RI, VT)
• ßeta Tester
• iOS ßeta: Always the latest version
• WME ßeta

Image
WME | Mentoring | AM | USA
orbitc
Master Raider
Master Raider
 
Posts: 5678
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 1980 times
Been thanked: 4674 times

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

Postby RoyaltyWoody » Thu Jan 31, 2013 6:12 am

AlanOfTheBerg wrote:
orbitc wrote:I agree with Alan. Few of us tested these with few different combination. The Best option, IMO, should be either with single quotes or double quotes.

I like single. Because they are thinner.


I'd prefer single for an additional reason: only requires one keystroke instead of two-simultaneous (as is required for the double. (At least, that's the way it is on every full sized keyboard I've ever used.)
Image
Using Waze on HTC One M9
RoyaltyWoody
Area Manager
Area Manager
 
Posts: 109
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 39 times
Been thanked: 3 times

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

Postby floppyrod84 » Thu Jan 31, 2013 9:46 am

There are only so many combinations you can use before it affects other combinations. If single quotes work, just use that. Double quotes are bigger text wise.
Still waiting on Street and Saint working over here.

Sent from my GT-I9100 using Tapatalk 2
floppyrod84
 
Posts: 2583
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 44 times

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

Postby orbitc » Thu Jan 31, 2013 10:08 am

Like I said, that's the general consensus at this point. More people seem to prefer single quotes as well.

In order to address the local issue here, we should start naming just those 4 letters using single quote without shortening the name.
Like this:

Avenue S will be: Ave 'S'
Regional Coordinator for Northeast (DE, NJ, NY, PA) & New England (CT, ME, MA, NH, RI, VT)
• ßeta Tester
• iOS ßeta: Always the latest version
• WME ßeta

Image
WME | Mentoring | AM | USA
orbitc
Master Raider
Master Raider
 
Posts: 5678
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 1980 times
Been thanked: 4674 times

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

Postby CBenson » Thu Jan 31, 2013 11:42 am

CBenson wrote:Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington."

OK, I can confirm that the sound file is used as the destination location if you select your destination by press and holding the location on the map. If you search for a destination, the announced destination location appears to be the search result you select. However, if you press and hold to give the destination, waze creates the destination location announcement. However, as waze gives the street name anyway this is redundant.
So if I press and hold to route to a location on F St NW, when I get there waze says: "You have reached your destination eff street en double you Washington at eff street northwest." Sometimes if waze determines the street number it seems to include the number: "You have reached your destination 601 eff street en double you Washington at eff street northwest."
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10074
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2233 times

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

Postby sketch » Fri Feb 01, 2013 7:22 pm

CBenson wrote:This exit has been named "Exits 13A-B-C: US-301 / MD-3 Richmond / Crofton" to match the BGS for quite some time. I drive through it regularly. TTS says: "Exits thirteen ayybeesea...youess threeohone...emdee three Richmond...Crofton." It sounds fine to me. I've never seen or heard a complaint.

That's how it should be done (more or less — it should be "Exit" rather than "Exits", if that's what the big green sign says). Read the fifth bullet point in this section of the road naming wiki: http://www.waze.com/wiki/index.php/Road ... n-ramps.29
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5662
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1227 times
Been thanked: 1679 times

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

Postby CBenson » Fri Feb 01, 2013 7:40 pm

sketch wrote:it should be "Exit" rather than "Exits", if that's what the big green sign says

Just to clarify, you are saying it should be what the big green sign says, correct?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10074
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2233 times

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

Postby sketch » Fri Feb 01, 2013 7:52 pm

CBenson wrote:
sketch wrote:it should be "Exit" rather than "Exits", if that's what the big green sign says

Just to clarify, you are saying it should be what the big green sign says, correct?

Correct. I think this varies by state. In Louisiana, it'll say "Exit 232A-B", for example.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5662
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1227 times
Been thanked: 1679 times

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

Postby txemt » Fri Feb 01, 2013 8:01 pm

sketch wrote:Correct. I think this varies by state. In Louisiana, it'll say "Exit 232A-B", for example.


It should say "Exit 223A-B: LA-xx / Williams Blvd / New Orleans International Airport" :D

I can't remember what state highway Williams Blvd is.
Just wazeting my time to help you waze your route smoothly.
txemt
Area Manager
Area Manager
 
Posts: 4769
Joined: Tue Jul 17, 2012 7:03 pm
Location: Miami, Fl
Has thanked: 42 times
Been thanked: 1032 times

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

Postby CBenson » Fri Feb 01, 2013 8:19 pm

CBenson wrote:So I think I can confirm that "'E' St NW" is now pronounced "ee street northwest."* Unfortunately, I tested E St and I'm finding it really difficult to hear the difference between "ee" and "east." I'll try 'N' now.

"'N' St SW" is pronounced "en street northwest" in the turn instructions.
I'm planing to change E, N, S and W street to include the single quotes.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10074
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2233 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users