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 ottonomy » Mon Oct 19, 2015 1:55 am

whatnt wrote:No. Long e's and emphasis on first syllable. And hard V like vē.

'lēvs-lē

How about this?
ottonomy
Global Champ Mentor
Global Champ Mentor
 
Posts: 755
Joined: Thu Oct 11, 2012 6:31 am
Location: Los Angeles CA
Has thanked: 1441 times
Been thanked: 638 times

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

Postby Panda47 » Sun May 20, 2012 1:10 am

Hi. Can we get the following special character in it? I know you have it already surrounded by single quotes, but what about w/o the quotes? What about with a street name?

Character = ½
Example: 30th ½ St
Example: 31st ½ St

Thanks, and keep up the good work.
Panda47
 
Posts: 124
Joined: Tue May 01, 2012 7:59 am
Location: Mission, Texas, USA
Has thanked: 0 time
Been thanked: 0 time

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

Postby PesachZ » Fri Apr 18, 2014 4:48 pm

AlanOfTheBerg wrote:
sketch wrote:Interesting. Wonder if it's relevant that it's the last word in the string.

My thought exactly. I defined the rule similarly to how N=north is defined, which is different than all the other cardinals, which may also explain why @txemt has noted that is seems "xyz Pkwy N" pronounces "enn" rather than "north." I will be checking on this.

Just to another to the list, travelling up onto the Hutchinson River Pkwy N from the Whitestone Brg produced a "Hutcinson River Parkway enn" Verbal instruction on March 24th. Mentioned in the UR there.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Wed Apr 30, 2014 11:50 pm

AlanOfTheBerg wrote:A couple thoughts which may already be addressed: 1) saying the full name of a state for the two letter abbreviation is different than saying the appropriate phrase for "XY-###" where XY is the state abbreviation (or just M for michigan). The key is defining the abbreviation with and without the hyphen. I think we should all agree, and it won't cause too much angst, that state routes should use a hyphen to help with abbreviation rule; 2) as noted above and later "BUS" only fails if it begins or ends a segment name; 3) "N" failing to say "north" happens when it is preceded by a custom abbreviation.

Is "Pkwy" a custom abbreviation? I just experienced the second Pkwy which had the entrance ramp spoken as "... Parkway enn". The first was Hutchinson River Pkwy N, and today Bronx River Pkwy N.
If it is should we be doing anything to fix it in the segment names?

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Thu May 01, 2014 12:04 am

AlanOfTheBerg wrote:Yes, noted in the thread with pkwy example specifically.

In the meantime should the name be changed to spell out 'parkway' or 'north'?

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Thu May 01, 2014 4:31 am

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.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Thu May 01, 2014 4:44 pm

GizmoGuy411 wrote:
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.

I cleared my cache and got a bar at the top that it was preparing navigation voice. I waited till after the bar went away then drive through.
[ img ]
It said " Keep left at eye 87 South, Maj Deagan Expressway, Manhattan, Queens "

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Tue May 06, 2014 4:14 pm

GizmoGuy411 wrote:
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


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.

I agree that this is an important discuss we should have. I'll give my 2 cents here, to expand on what your saying.

I recommend that any 2 letter abbreviation (XX) could be expanded to the name of an entity.

When there is more than one entity sharing the same abbreviation, we should give preference to the compass directions, followed by governmental hierarchy. So NorthEast would take precedence over Nebraska for "NE". A State/Province would take precedence over a city name, followed by a county, town, village, etc. in order.

I suggest that punctuation should matter.

  • "XX[space]" or "XX" at the end of a segment name should be expanded to the entity name (I.e. "...Richmond VA / Andrews ..." Would sound like "... Richmond Virginia, Andrews ..."). It is more likely IMHO that entity abbreviations like this may be at the end of a string, than abbreviations which we would want to pronounced as the literal letters.
    .
  • "XX-##", " XX-#", or "XX-###" should say the literal letters I.e. "LA-13" Would sound like "El Aye Thirteen"). IMHO we would want the letters pronounced usually in relation to a numbered route. If a certain entity prefers through regional consensus to have the entity name verbalized, they would just need to set a regional standard of naming routes with a " " [space] between the letters and numbers instead of a "-" (hyphen).
    .
  • When two entities share an abbreviation, the non-primary one (the one which is not granted the XX expansion in the TTS) may be enabled using a different punctuation to be defined in the wiki when added to the list I.e. "L.A. 13 Would sound like "Los Angeles Thirteen").

These could then be listed clearly as global guidelines (allowing for regional exceptions by consensus) with the full list in the wiki, and any regional special punctuation exceptions repeated in that region's wiki.


Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Thu May 15, 2014 2:32 am

This ramp segment named "to I-87 N / I-278 E / Bronx / Upstate NY / New England" is being pronounced as "... Eye two seventy eight east <short pause> Bronx <short pause> Upstate New York comma New England"
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

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

Postby PesachZ » Thu May 15, 2014 3:31 pm

qwaletee wrote:So TTS finds two-letter state names comma-cle?

I'll see myself out.
LOL

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
 
Posts: 4464
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1996 times
Been thanked: 2299 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users