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.

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

Postby CBenson » Wed Jan 30, 2013 11:14 pm

My gut reaction is just to change E, N, S and W. My vote would be to use the capital letter inside single quotes, but GizmoGuy stated that the recommendation to waze was to use double quotes. I don't remember (if I ever knew) why the preference for double quotes.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 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-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 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-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 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-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Fri Feb 08, 2013 8:00 am

So I just came across the first UR that I have seen that objects to the spelling of an abbreviation. The UR states: "xing is not how you spell crossing!'" The TTS here does speak "xing" as "crossing." So this objection is purely a display objection. Should we not use the abbreviation "xing" if users (or at least one user) objects to the spelling but the TTS is correct?
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Fri Feb 08, 2013 2:42 pm

orbitc wrote:Also, Colony Crossing is an actual street name, therefore, it should be Colony Crossing.

Its not Colony Crossing Street

I think of "Colony" as the name and "Crossing" as the road type.
Thus:
Colony Street - Colony St
Colony Drive - Colony Dr
Colony Boulevard - Colony Blvd
Colony Avenue - Colony Ave
Colony Road - Colony Rd
Colony Crossing - Colony Xing

I
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Sat Feb 09, 2013 11:39 pm

xteejx wrote:No shit Sherlock. I have been posting in this thread previously.

Why? I thought this was a thread about US abbreviations.
xteejx wrote:Enough with the stupid replies yeah?

Can someone proper confirm this dash behaviour please?

Sorry, I can't. I only really use dashes in routes like "I-97" "US-50" or MD-3." I've never noticed a pause with these and have not noticed a change in behavior with these. Not sure why you would expect a better answer in this thread.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Wed Aug 14, 2013 11:00 am

Penn is still spoken as Pennsylvania.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Fri Oct 11, 2013 9:46 pm

jasonh300 wrote:
txemt wrote:
taddison1 wrote:I had a couple of odd abbreviation behaviors today:

- In this street name: to Downtown / Cesar Chavez N, the "N" at the end was pronounced as the letter N instead of "North". Any idea what could cause that, seeing as the N is not in quotes?
Permalink: https://www.waze.com/editor/?lon=-96.78 ... s=62245993


I've just gotten a report about this today where the "N" was reading as "en" and not "north." It is unknown if the other directional letters are doing the same thing or not.


There's a whole thread about this somewhere. It seems to be when roads have unconventional names. Such as US-11E N or Cesar Chavez N. If it was Cesar Chavez Dr N, it probably wouldn't do it.

Here's a report that it is doing it after "Pkwy."
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

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

Postby CBenson » Tue Feb 04, 2014 6:02 pm

I'm not sure I've ever seen that page before. What is the providence of this:
For example: California would be abbreviated to C.A. not CA and Victoria to VIC.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9031
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 745 times
Been thanked: 1799 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users