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 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?
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: 3982
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 120 times
Been thanked: 133 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.
iphone 5 • ios 6.1.3 • waze 3.6.0.0
macbook pro 15" unibody • mac os 10.8.2
new orleans + se louisiana area manager
Image
sketch
Waze Champs
 
Posts: 1483
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 26 times
Been thanked: 24 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.
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 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.
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: 3982
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 120 times
Been thanked: 133 times

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

Postby orbitc » Fri Feb 01, 2013 9:21 pm

We will start changing N, E, W, S letters in NY and NJ starting Monday.
CM: U.S.A. & T.C.
AM: Tri-State
• βeta Tester
• AT&T | iPhone 5: Jailbroken | iOS 6.1.2
Image Image
Wiki Resources: Best Practices | Waze FAQ | NJ Project/To-Do List
orbitc
Experts
 
Posts: 1690
Joined: Mon Jun 25, 2012 1:51 pm
Location: New Jersey, USA
Has thanked: 140 times
Been thanked: 440 times

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

Postby Timbones » Fri Feb 01, 2013 9:36 pm

Anyone tested a backslash preceding the letter, eg \N? It's a long shot, but if we're (very) lucky it'll appear as just N on the client, and pronounced 'en'.

And another thing: we should never need to abbreviate directions when they are used as nouns. "North St" is just fine, and the client doesn't need it to be shorter. IMHO.

via mobile
Timbones • UK Country Admin • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.6 « NEW (Feb 2013)Livemap Navigation v0.72 (Jan 2013)
Timbones
Waze Champs
 
Posts: 2853
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 17 times
Been thanked: 186 times

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

Postby orbitc » Fri Feb 01, 2013 10:33 pm

Hi Tim,

I can setup a rig to test that theory. I'll let you know my findings.

Would you put Avenue S as Ave 'S' or just leave it as Avenue 'S'?

Ps. Great job as always with your scripts. :D
CM: U.S.A. & T.C.
AM: Tri-State
• βeta Tester
• AT&T | iPhone 5: Jailbroken | iOS 6.1.2
Image Image
Wiki Resources: Best Practices | Waze FAQ | NJ Project/To-Do List
orbitc
Experts
 
Posts: 1690
Joined: Mon Jun 25, 2012 1:51 pm
Location: New Jersey, USA
Has thanked: 140 times
Been thanked: 440 times

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

Postby Timbones » Fri Feb 01, 2013 11:55 pm

orbitc wrote:Would you put Avenue S as Ave 'S' or just leave it as Avenue 'S'?

Not sure. Is it "Avenue Ess" or "Avenue South"? Which is the noun? Does it really need to be abbreviated at all? Maybe it's time to get rid of them altogether. Devices have much higher resolutions these days, and there's plenty of space on the screen for full road names... [/rant]

I'd certainly keep "The Avenue" unabbreviated (two of them in my village).

I've noticed that (in the UK) the directions (N) are now spoken as "En" not "North", et cetera :(
Timbones • UK Country Admin • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.6 « NEW (Feb 2013)Livemap Navigation v0.72 (Jan 2013)
Timbones
Waze Champs
 
Posts: 2853
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 17 times
Been thanked: 186 times

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

Postby xteejx » Sat Feb 02, 2013 12:09 am

Because people keep requesting things across the pond and elsewhere without anyone thinking about the consequences for everyone else. I keep saying it but there needs to be a proper requesting system and a structure in place, and testing by Waze on the TTS side.
What I really want to see is the ability for separate countries to have their own TTS rules which would sort all this out completely, and have designated testers and implementers from each country to have direct access, or at least to work VERY closely with HQ so things can be changed easily.

Sent from my GT-I9100 using Tapatalk 2
Area Manager for Kent. Localisation expert and translator for UK English.
Image
UK specific editing: http://www.waze.com/wiki/index.php/United_Kingdom
xteejx
 
Posts: 2337
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 11 times
Been thanked: 15 times

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

Postby orbitc » Sat Feb 02, 2013 12:40 am

xteejx,
Couldn't agree more.

I'm sure, you've seen that we've been testing these in the past 2 weeks. We're also working close with some of the Waze Champs.

Without Waze doing anything initially, we'll fix our local issue by renaming those letters (N,S,E,W) with single letters. Currently, Avenue S in NY pronounced as Avenue South, which is wrong.

Our final conclusion is to use this format:

Avenue S will be Ave 'S'
CM: U.S.A. & T.C.
AM: Tri-State
• βeta Tester
• AT&T | iPhone 5: Jailbroken | iOS 6.1.2
Image Image
Wiki Resources: Best Practices | Waze FAQ | NJ Project/To-Do List
orbitc
Experts
 
Posts: 1690
Joined: Mon Jun 25, 2012 1:51 pm
Location: New Jersey, USA
Has thanked: 140 times
Been thanked: 440 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users