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 GizmoGuy411 » Thu Apr 17, 2014 11:18 pm

CBenson wrote:Its not uncommon around here for BGS near state boaders to include the state for a destination. Thus ramp names that copy the BGS crop up with state abbreviations around here.


sketch wrote:There's definitely an exit on I-59 in Mississippi (or maybe Georgia) that lists "Something, Ala." as one of its destinations served.


Alan raised a good question. I started to wonder myself why I had them all tagged as "A"dd in the test list, and if I did so years ago, just because I thought it was a good idea at the time, or if there were other reasons I don't remember, like possibly for use with route numbers.

In any case, can you guys provide a couple examples? Meanwhile I'll try to start from page one here and see if I can find a better rationale for "A"dding them.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Fri Apr 18, 2014 2:37 am

sketch wrote:Other considerations too, like do we really want LA to say "Louisiana"? Everyone here says "L A one", "L A forty-eight", and so forth.

I believe the idea was to get this done so we could use state abbreviations for state highways. Not that that's perfect. Some states would prefer SR or SH I'm sure — but the benefit of that is that we could get state-specific shields for every state. BUT of course it won't work for Nebraska.


Well if we did make "LA" another exception to say the letters "L A" then it would also work for Los Angles.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Fri Apr 18, 2014 2:18 pm

sketch wrote:All I'm saying is that we should consider each state abbreviation individually. If it's best that MD say Maryland, so be it. If people say "N C x" for NC state highways, keep the letters for that state.

We also don't want to be using "MI" instead of "M" for Michigan state highways because they're unequivocally referred to as "M-x". But for other states, it would be useful, like Maryland.

Obviously we can't achieve full parity because of Nebraska/northeast, so we might as well be accommodating.


Would we ever want "NE-" used for "Northeast-[something]"?

If not, then we actually maybe we can even accommodate Nebraska if the RegEx can be wrote to use "NE-xxx" to say "Nebraska xxx", instead of "Northeast xxx".

That is of course if that is how they refer to them.

And yes. Agreed on "M-xxx" for Michigan.

We should probably take this discussion off to another topic thread, and just point to it from here, since we have almost 70 abbreviations for State/Provinces, etc.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Sun Apr 20, 2014 1:41 am

I'm out of the loop for 12 hours. Alan and I both told Waze that "BUS" failed in several tests, and Alan told them of the "Saint vs Street" failures. So the request for corrections are in the loop.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Sun Apr 20, 2014 1:44 am

And for full disclosure, you can all blame me for the "NE" and "FM" oversights. I was over confident that they had been cross checked a long time ago against any conflicts.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Wed Apr 30, 2014 12:37 pm

Reminder. Don't forget to clear your TTS cache before you retest anything you are watching. Use cc@tts in your search box.


Sent from my iPad using Tapatalk
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Thu May 01, 2014 4:16 am

syborg_sasquatch wrote:
CBenson wrote:But this ramp was enunciated "Exit right to exit to Maryland ... three ... eye ninety seven north ... Baltimore" for me.

Tested Samantha on a couple of exits on I-70 in MD and she enunciated Maryland with a pause afterward for me as well.

But Tom would not enunciate any exits with MD in the string. All I received was "In [distance], exit right."


Can you run with Tom again to see if he EVER uses street names? Beta client?

I have been running Samantha with the Android beta and she is regularly losing street names. No discernible pattern to report it yet however.

We will report the MD issue once some other issues in the que are resolved.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Thu May 01, 2014 4:24 am

vectorspace wrote:I've had more interaction with Bureau of Indian Affairs (BIA) on road systems. A few things seem clear and would appreciate the following being done in the TTS spreadsheet.

(1) Remove ISR-xxx - Indian Service Route. This is archaic and not appreciated by the tribes.

(2) Add NTR-xxx Native Tribal Route. TR is used elsewhere as Township Road.


Alan.

Do we want to address this and the MD issue yet, or wait until the current items in the que are resolved? My last test of "BUS" still failed too.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Thu May 01, 2014 2:51 pm

PesachZ wrote:On April 27th this ramp to the I-87 S was pronounced "Keep left to eye 87 South, Maj Deegan Expressway, Manhattan, Queens". The Maj was not expanded into Major.


Thanks for the link.

Can you clear your TTS cache, and test this again in the next few days to see if anything changed again after the update Alan mentioned? If you can not get to it, let us know and we can try to test it remotely.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

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

Postby GizmoGuy411 » Tue May 06, 2014 2:59 pm

sketch wrote:Blah. LA-3021, which used to say ell eh thirty twenty one, now says "Louisiana (pause) thirty thirty one". I'm not happy about it.

Sent from my iPhone using Tapatalk 2


We need to discuss how we want these CAPITALIZED TWO LETTER abbreviations for the entities names for the U.S. States, Districts, Territories, Possessions, and Canadian Provinces to be pronounced. (Refereed to in this post collectively as "XX" abbreviations.)

Should "XX" be pronounced as the entity name or always as just the two letters?
(In the past, some were spoken as letters and others were attempted to be pronounced as a word. We would never want "XX" to be spoken as a word other than the proper name of the entity.)

Do we want it uniform for the entire NA or different for every entity?

Examples such as this BGS exist to demonstrate why entity name to be pronounced in full for the "XX" abbreviations:
2014-05-06_10h46_36.png
2014-05-06_10h46_36.png (60.91 KiB) Viewed 290 times


Do we want [XX<space>] different than [XX-] ?
Example: "LA<space> could say "Louisiana" and "LA-" could say the letters "L" & "A".

Again, would we want that to be uniform for the entire NA or custom for each entity?

We recently had two specific "XX" abbreviations that were found to be problematic and have been reverted back to their previous TTS without any further considerations of position or punctuation yet:
- "NE" needed to remain "Northeast" instead of "Nebraska".
- "FM" needed to remain "Farm to Market" instead of the "Federated States of Micronesia"

The entire list of these "XX" abbreviations need to be reviewed again to identify others that may also be problematic that we may have missed. (As mentioned before, I personally missed "NE" and "FM" when I reviewed them a couple years ago.)

These "XX" abbreviations start at around line 800 in the Big TTS Test List.

After some initial discussion, we may want to move this discussion to its own topic.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1318
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 383 times
Been thanked: 226 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users