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 t0cableguy » Sun Sep 20, 2015 7:58 am

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


ALT SR-A1A

The ur explains it all. I am trying to find out if they are using Jane, but since Sam has been retired i cannot imagine they are using anything else.

Also Alt - Alternate is spelled wrong in the wiki sheet for US abbreviations.
t0cableguy
 
Posts: 1081
Joined: Tue May 27, 2014 11:05 pm
Location: Lake Wales, FL, USA
Has thanked: 328 times
Been thanked: 445 times

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

Postby ErikSTL » Wed Sep 16, 2015 5:43 pm

In St. Louis, MO, there's a road spelled "Ladue" that is pronounced "la-DOO". Waze wants to use the French pronunciation, which is incorrect.

Road name: Ladue

Correct pronuncation: la-DOO

Incorrect way it's currently pronounced: lad-way.

Sorry, I've been told that a PL helps. Here ya go:

https://www.waze.com/editor/?env=usa&lo ... s=27814195
ErikSTL
Area Manager
Area Manager
 
Posts: 9
Joined: Thu Aug 20, 2015 3:05 pm
Location: St. Louis, MO
Has thanked: 1 time
Been thanked: 0 time

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

Postby taco909 » Sat Sep 12, 2015 2:46 am

Recent change...
"Verdugo" = "Ver-doo-go"
Recently been throwing in an extra syllable "Verdoodigo"
taco909
Map Editor - Level 4
Map Editor - Level 4
 
Posts: 2230
Joined: Sun Jun 01, 2014 4:05 am
Location: Los Angeles Area
Has thanked: 720 times
Been thanked: 641 times

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

Postby gunnargsd » Fri Sep 11, 2015 11:56 pm

Reporting a TTS issue:

- Britton Pkwy
- Being pronounced "Britt"
- BRIH-tuhn - http://inogolo.com/pronunciation/Britton
- https://www.waze.com/editor/?env=usa&lo ... s=77923959

Thank you
gunnargsd
Area Manager
Area Manager
 
Posts: 53
Joined: Fri Dec 24, 2010 1:41 pm
Has thanked: 98 times
Been thanked: 14 times

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

Postby PesachZ » Wed Sep 09, 2015 1:05 am

bummerdude69 wrote: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]

The '.' does not work, it is exclusively for cardinals. For most others we just try not to have abbreviations which cause conflicts with real names, that's why we like to be informed when those conflicts are discovered. This allows to reevaluate whether the abbreviation should be modified to avoid conflicts. We can generally find ways around it when necessary, but there is no one size fits all solution.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4401
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1992 times
Been thanked: 2235 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]
bummerdude69
Map Raider
Map Raider
 
Posts: 162
Joined: Mon Jan 27, 2014 9:01 pm
Has thanked: 202 times
Been thanked: 44 times

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

Postby PesachZ » Tue Sep 08, 2015 6:45 pm

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"



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

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

Postby bummerdude69 » Tue Sep 08, 2015 5:34 pm

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").
bummerdude69
Map Raider
Map Raider
 
Posts: 162
Joined: Mon Jan 27, 2014 9:01 pm
Has thanked: 202 times
Been thanked: 44 times

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

Postby PesachZ » Tue Sep 08, 2015 3:22 am

bummerdude69 wrote:https://wiki.waze.com/wiki/Abbreviations_and_acronyms
When 'N', 'S', 'E', or 'W' should NOT be pronounced as compass directions, enclose the letter in single quotes.

Does this apply to all abbreviations? If so, should that be noted on the page?

First of all you are looking at an outdated page which no longer applies to the USA. For the USA please see guidance on the Abbreviations and acronyms/USA page (item #4).
We are no longer using single quotes, when you want a cardinal direction to be spoke as aleter it should be followed with a period. For example "George W. Bush Blvd"

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?

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

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

Postby bummerdude69 » Tue Sep 08, 2015 2:36 am

https://wiki.waze.com/wiki/Abbreviations_and_acronyms
When 'N', 'S', 'E', or 'W' should NOT be pronounced as compass directions, enclose the letter in single quotes.

Does this apply to all abbreviations? If so, should that be noted on the page?
bummerdude69
Map Raider
Map Raider
 
Posts: 162
Joined: Mon Jan 27, 2014 9:01 pm
Has thanked: 202 times
Been thanked: 44 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users