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: Jackson, krankyd, rondesta, adriansinger

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

Postby AndyPoms » Sun Nov 11, 2012 5:19 pm

GizmoGuy411 wrote:Typically they are one file number different from each other. One will contain just the names of the segment and the other will have the names prefaced with the word "at" like the files in my message about boro, par, and ph saying borough, parade, and phone in one file but borough, par and p h in the other

Sent from my Galaxy Nexus using Tapatalk 2


I found the one I was looking for (using the TTS.db file to turn Words into file names), sorted the audio files by name, found the one I was looking for, played it, then went up and down the list looking for the 2nd one - couldn't find it...

The files I have for testing Captain:
1350890107-241200-1.tts = "at Capt Andrew Road" (Capt)
1352209891-134545-2.tts = "at Captain Andrew Road" (Capt.)

The files that share filename (except the last digit):
1352212687-976610-2.tts = "at Wilson Street"
1352212687-976610-3.tts = "at Grenhart Road"

More last digit changes & the files around them...
1343979810-878014-6.tts = "at Sherman Ave"
1343979854-936669-7.tts = "at Airport Road"
1343979854-936699-8.tts = "at I-91 S / SR-15 S"
1343979854-936699-9.tts = "at I-91 S / New Haven / North Why City"
1343979854-936730-10.tts = "at I-91 S"

Still no duplicate files...
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Thu Nov 15, 2012 8:58 pm

jasonh300 wrote:It's most likely because the word "To" on the ramp is capitalized, which doesn't conform to the standard.

I'm going to send a PM to the editor in question and make sure this is just a typo and not widespread.
Remember there was a period of time when auto-capitalization just started where the word "to" was not exempt & it was automatically changed to "To", so there may be more ramps out there like this...
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 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
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Fri Jan 11, 2013 7:41 pm

Only tested "Pkwy" (first letter capitalized, rest lowercase) in response to another thread...

On a side note "Waze" isn't pronounced correctly - not even close.
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Fri Feb 08, 2013 9:59 am

CBenson wrote: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?

Xing is a standard MUTCD abbreviation, so I don't see why it shouldn't be used. http://mutcd.fhwa.dot.gov/htm/2003/part1/part1a.htm
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Tue Oct 22, 2013 1:43 am

Seems like "Dr." may not work on forcing a "Doctor" - see the UR HERE (BETA for Conversation)
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Tue Nov 05, 2013 9:56 am

sketch wrote:
AlanOfTheBerg wrote:
qwaletee wrote:It would be interesting to know the distribution of signs using Br for Bridge versus using Br for Branch, so that we could know which to assign causing the fewest issues.

As noted elsewhere, when in doubt, spell in out.

"Br" is apparently the abbreviation for "Branch" according to both the USPS and MUTCD. This is what Waze's TTS abbreviations are apparently based on.

If a local authority disagrees with the USPS and the MUTCD, well, what can we do.
I thought we only found "Br" = "Branch" in the USPS abbreviations, not in the MUTCD. I know in CT (there's a link to the state listing in the TTS spreadsheet) that "Br" is officially "Bridge" (and it's used extensively in the northeast US that way too).
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Mon Nov 11, 2013 12:26 am

bart99gt wrote:I read through the first few pages, and last few pages of this thread, and didn't see this mentioned.

Is Waze in the process of adopting standard USPS two letter state identifiers to TTS? As I'm sure everyone is aware, Waze currently just says the letters individually, it would be nice to have it actually pronounce the actual state name, either when used as part of a highway name, or as a City, State type reference.
This has been requested. However Waze doesn't say the letters in all cases, "CT" is pronounced "Court", "NY" is pronounced "North Why", etc.

We've also made a request to have things such as "CA-##", "NY-##", "MI-##", "LA-##" translate into the local "Route"/"Highway"/"El Ay"/etc name as well. This one is much longer term.
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby AndyPoms » Mon Nov 11, 2013 1:18 pm

bart99gt wrote:
AndyPoms wrote:
bart99gt wrote:I read through the first few pages, and last few pages of this thread, and didn't see this mentioned.

Is Waze in the process of adopting standard USPS two letter state identifiers to TTS? As I'm sure everyone is aware, Waze currently just says the letters individually, it would be nice to have it actually pronounce the actual state name, either when used as part of a highway name, or as a City, State type reference.
This has been requested. However Waze doesn't say the letters in all cases, "CT" is pronounced "Court", "NY" is pronounced "North Why", etc.

We've also made a request to have things such as "CA-##", "NY-##", "MI-##", "LA-##" translate into the local "Route"/"Highway"/"El Ay"/etc name as well. This one is much longer term.


Very good, I figured that it probably had been, but sifting through 50 some pages would have been a bit tedious.

A lot of the State name stuff is covered in the Spreadsheet (linked to in the VERY first post).
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5923
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 882 times

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

Postby banished » Thu Jan 19, 2012 3:28 am

Jr. = Junior in TTS, as in Martin Luther King Jr. Blvd. I didn't see it in your list. I found that without the period, "Jr" induces TTS to say "jay are".

I expect the same result for "Dr." as in "Dr. Martin Luther King Jr. Blvd". Since most every town has a street honoring MLK, it's appropriate to include it in your extensive list. Nice work, by the way.
Country Manager & Southeast (Alabama, Florida, Georgia) Regional Coordinator
@WazeNWFL I've died and gone to Waze. Pray for my family.
-- I Waze, therefore I am --
banished
Global Champ Mentor
Global Champ Mentor
 
Posts: 617
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 96 times
Been thanked: 84 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: sketch