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

[ img ] 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 AlanOfTheBerg » Mon Feb 27, 2012 4:56 pm

CBenson wrote:I just discovered that "Pr." is on a few BGSs around here as an abrieviation for "Prince." The TTS says "pea are."

Another one to just spell out? Though I'm not sure what "pr" would otherwise conflict with.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23598
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4781 times

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

Postby CBenson » Mon Feb 27, 2012 3:41 pm

I just discovered that "Pr." is on a few BGSs around here as an abrieviation for "Prince." The TTS says "pea are."
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

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

Postby sketch » Wed Feb 22, 2012 7:43 pm

I agree. I also stated "N.Y.C." should be read like that, though. No need for it to unabbreviate it at all.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5911
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1418 times
Been thanked: 1936 times

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

Postby GizmoGuy411 » Wed Feb 22, 2012 7:17 pm

That is just it. The signs do not say New York City. They just say NYC with no spaces or periods.

So my thinking was that for that abbreviation TTS should just say " en wye cee" to reflect the same brevity.

Sent from my Galaxy Nexus using Tapatalk
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1404
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby sketch » Wed Feb 22, 2012 6:32 pm

GizmoGuy411 wrote:WeeZer14 just found an issue in New York City with signs that say "NYC". Waze does not pronounce it properly at all.

I'm adding them all the list, however which of the following should we request:
a) NYC = "New York City"
b) NYC = "NYC" (the letters)
c) N.Y.C. = "New York City"
d) N.Y.C. = "NYC" (the letters)
e) other

I'm thinking b and c.

(As a side note, Excel says "New York City" for "NYC" and says the letters "N", "Y", "C" for "N.Y.C")

"NYC" should be pronounced "N Y C", as should "N.Y.C." If a sign says "New York City", we should put "New York City" in the name, not "N.Y.C."
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5911
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1418 times
Been thanked: 1936 times

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

Postby GizmoGuy411 » Wed Feb 22, 2012 4:30 am

A section on Abbreviations has been added to the Waze Wiki "Editing Manual" under "How to label and name roads":
http://www.waze.com/wiki/index.php/How_ ... reviations

The lead post here has also been edited and updated.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1404
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby GizmoGuy411 » Tue Feb 21, 2012 4:16 am

WeeZer14 just found an issue in New York City with signs that say "NYC". Waze does not pronounce it properly at all.

I'm adding them all the list, however which of the following should we request:
a) NYC = "New York City"
b) NYC = "NYC" (the letters)
c) N.Y.C. = "New York City"
d) N.Y.C. = "NYC" (the letters)
e) other

I'm thinking b and c.

(As a side note, Excel says "New York City" for "NYC" and says the letters "N", "Y", "C" for "N.Y.C")
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1404
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby GizmoGuy411 » Tue Feb 21, 2012 3:59 am

jasonh300 wrote:Do you have "Trace" on your list? I drew in a new subdivision yesterday and two of the new street names were "Natchez Trace" and "Memphis Trace". I had no idea how to abbreviate them, so I just spelled them out.


Yep the confirmed abbreviation for "Trace" is "Trce", which is not much of a savings. I think I would just stick with "Trace".
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1404
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 428 times

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

Postby jasonh300 » Tue Feb 21, 2012 1:49 am

Do you have "Trace" on your list? I drew in a new subdivision yesterday and two of the new street names were "Natchez Trace" and "Memphis Trace". I had no idea how to abbreviate them, so I just spelled them out.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 402 times
Been thanked: 978 times

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

Postby jenncard » Tue Feb 21, 2012 1:08 am

Timbones wrote:It seems that "Cr" is being now pronounced as "Country Road", so what would be an acceptable abbreviation for "Crescent"?

Gizmo has confirmed that "CRES" is pronounced as Crescent... at least on the NA server :?
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 11 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users