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.

Moderator: delilush

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

Postby CBenson » Mon Feb 20, 2012 6:49 pm

I recently passed through this ramp and noticed that "Hwys" does not work as an abbreviation. As far as the "trwy" goes, it sounds like "Trueway" to me.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Sat Feb 18, 2012 3:39 pm

GizmoGuy411 wrote:I did not think it was important enough to keep track of.

Sound quite reasonable, given all that you are keeping track of.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Sat Feb 18, 2012 2:10 pm

Not that the info is too useful, but when there is no TTS available, does that mean the TTS engine tries to sound out the entry as a word or does it try to spell out the entry as letters?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Sat Feb 18, 2012 12:01 pm

Whats does "n/a" in the confirmed results column mean?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Fri Feb 17, 2012 3:49 pm

Yep, no problems with fractions here.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Sat Jan 21, 2012 2:49 am

The credits for the Android Waze 2.9.99.120 says: "Text to Speech: (c) Copyright 2011 Nuance Communications, Inc."
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Fri Jan 20, 2012 5:58 pm

How should the street between "M St" and "O St" be input so that it is not spoken "North St?"
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby CBenson » Wed Jan 18, 2012 7:54 pm

I'm not sure how waze plans to handle regional/national/language diffences, but I am assuming that currently we are dealing with US English. If that is the case I would add in the state abbrieviations. For instance "MD" is pronounced "emm-dee" by waze. "Penn" is a problem and is pronounced "Pennsylvania."

I would also add the following:
Alternate - ALT
Bound - BND
Crossing - X-ING
Expressway - EXPWY
International - INTL
National - NATL
Route - RT
Throughway - THWY

I would also note that some abbrieviations are ambiguous: ST for Saint or Street and DR for Doctor or Drive. Also some streets are lettered thus there are "E St (or Ave, Blvd etc.)," "N St," "S St" and "W St" out there. Ultimately, there will need to be a method for distinguishing "St" when it means Saint and "St" when it means Street and "N" when it means North and "N" when is should just be "N." If this is done with punctuation then we need to test "St" and "St." etc. If this is done by parsing the phrase, that is "N" is N if followed by a road designation, but north otherwise, then we will need to indicate the different results depending on the phrase.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

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

Postby Cardyin » Fri May 06, 2016 4:07 pm

https://www.waze.com/editor/?env=usa&lo ... st=5159700

Fairman St

is being pronounced as

Fireman Street
ImageImage
AM, Southern CA
Cardyin
Map Editor - Level 4
Map Editor - Level 4
 
Posts: 57
Joined: Tue May 12, 2015 12:05 am
Location: Southern California
Has thanked: 22 times
Been thanked: 72 times

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

Postby bummerdude69 » Tue Sep 08, 2015 7:21 pm

PesachZ wrote:
bummerdude69 wrote:
PesachZ wrote:First of all you are looking at an outdated page ...

Second this does NOT apply to all abbreviations, it is specific to cardinal directions.

Third is there a specific use case, or abbreviation which is being an issue for you that you are trying to override?

Thanks, I missed the difference between the two pages.

VA in "Southern Arizona VA Medical Center" is being pronounced as Virginia rather than just VA ("vee" "aa").

Should it be named with VA in the primary name, or would it be more appropriate to use the full Veterans Affairs, and put VA as an alt name.

If not you can put a space between the VA like "Southern Arizona V A Medical Center"

Trying not to highjack this thread too much, so I'll chase down those other options in other places.

But my main question (confusion?) still stands. What is the best way to avoid the TTS Abbreviation translation? Using '.' for the cardinals works, but what about for everything else? Or is there not, just one best way? [Which, looking at the Big List, seems more likely]
ImageImageImage
bummerdude69
Map Raider
Map Raider
 
Posts: 172
Joined: Mon Jan 27, 2014 9:01 pm
Has thanked: 220 times
Been thanked: 46 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users