This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Locked

Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Post by
[Please note that this lead post is edited periodically to reflect updated information, with any changes highlighted in the color of the date that follows:]

Post edit history:
2014-08-24 The Big List is now maintained entirely as a Google document and it no longer sourced from an Excel file.
2014-08-16 Every entry in the Big List has now finally been tested. A number of new entries also added.
2014-03-06 Column added to List to differentiate ROUTING TTS from DESTINATION TTS results.
2013-09-16 Minor rewrites of various paragraphs.
2012-10-31
2012-09-24
2012-09-06
2012-08-20
(earlier post edit history not maintained)
This is a list of abbreviations and acronyms that are being added to two sandbox test rigs, to be tested in the Waze clients to learn their TTS output results for North America. (Jenncard maintained a second test rig.)

All tests are with the Nuance female "Samantha" voice only as used in North America. While we expect that the other English voice choice for NA, "Tom", is likely to use the same TTS databases, we have not tested for it.

The list includes all the official and alternate abbreviations of the United States Postal Service, all the English abbreviations for Canada Post, a subset of the French abbreviations for Canada Post, a subset from the U.S. Federal Manual on Uniform Traffic Control Devices plus a number of others suggested by Waze users. (Additional abbreviations from the MUCCD for individual U.S. States and from any equivalent list for Canadian Provinces, have not yet been compiled.)

Official abbreviation list sources for specific states or providences are linked from their respective names in the test list.

If you already know or learn any TTS results, please post them here. Please submit only results that you are absolutely sure of, with the exact spelling (including any capitalization) of the abbreviation, and the confirmed TTS output result.

Also submit any additional abbreviations that you feel should be part of the list for testing and/or for future inclusion in the TTS system.

Some current abbreviations such as "Penn" (which generates "Pennsylvania") should probably be removed from the TTS system in favor of using the capitalized two letter State and Province abbreviation standards. We should also discuss others for consideration that may need to be removed from the TTS.

To hear the most current TTS results from your Waze client device, it may be necessary to clear your current TTS cache. Enter "cc@tts" without quotes in the Navigation search to clear the cache. Waze should reply with a "TTS cache has been cleared!" popup box. Then wait for "Searching ..." to end.

This list will be updated periodically. (The initial list was submitted 2012-01-18, which took a month for Waze to process, and for us to test in the Waze Clients.)

Once we learn what the TTS currently knows, we can add the results of this list to the Wiki, plus
we can use it to submit our requested TTS "wishlist" changes to Waze. Please note that entries in this are for testing purposes and do NOT automatically imply that we endorse them. This list is primarily to research as many possible abbreviations that we can test to learn what Waze currently recognizes or not.

To learn how to hear the TTS files on your Android device manually, read the side notes in the following post: http://www.waze.com/forum/viewtopic.php ... 96#p144296

A section on Abbreviations has been added to the Waze Wiki. The link below takes you to a selection of countries. Select your country from the list and follow the links to the abbreviations in your country:
Editing Manual > How to label and name roads (by country)

In the United States you can go directly to the US Abbreviations and acronyms list.

Google Drive Spreadsheet:
Text-to-Speech (TTS) Abbreviations in Waze Clients - Test List for North America aka the "Big List" or the "Big TTS Test List".

Last edited by GizmoGuy411 on Wed May 09, 2012 6:42 pm, edited 32 times in total.

Post by AlanOfTheBerg
Was this also to end up being an official list to help them differentiate things like Penn vs. Pennsylvania, St vs. St. (saint) and Dr vs Dr. (doctor)? I think we need to add those too, unless I'm missing the purpose of the full abbreviation list.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23624
Has thanked: 610 times
Been thanked: 3684 times
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ

Post by AlanOfTheBerg
gettingthere wrote:May need to use a single or double quote around the street name so that Waze understands that it's not an abbreviation that needs to be expanded.
Do quotes still result in being backslash-escaped to \' and \" ? I haven't tried recently.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23624
Has thanked: 610 times
Been thanked: 3684 times
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ

Post by AlanOfTheBerg
I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect. Not sure how they work at the end or in the middle of the name.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23624
Has thanked: 610 times
Been thanked: 3684 times
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ

Post by AlanOfTheBerg
banished wrote:
AlanOfTheBerg wrote:I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect.
Yes, I meant to include those. But other than a very small set of abbreviations, such as those, it makes sense to put a period after words not contained in that set, e.g., "Dr." for doctor and "Dr" for drive; "Wash." for Washington, and "wash" (no period) for wash, as in Wash Ave.
I feel, as mapcat noted, that we should not be going hog wild on things like Wash. vs Wash and Geo vs. George. The smaller set of abbreviations, the better. If it's Wash, it's always Wash, otherwise spell out Washington if that's what it is.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23624
Has thanked: 610 times
Been thanked: 3684 times
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ

Post by AlanOfTheBerg
CBenson wrote:I just discovered that "Pr." is on a few BGSs around here as an abrieviation for "Prince." The TTS says "pea are."
Another one to just spell out? Though I'm not sure what "pr" would otherwise conflict with.
AlanOfTheBerg
EmeritusChamps
EmeritusChamps
Posts: 23624
Has thanked: 610 times
Been thanked: 3684 times
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ




Post by abc1357
There is a restaurant named "Va de Vi". Unfortunately, Waze pronounces it as "Virginia de Vi". What's the best way of fixing? Could I put it in as "Va. de Vi" as the primary to aid pronunciation and put in "Va de Vi" as alternate name to enable search?

Unfortunately, unlike road segments, there is no "voice" button next to it to test. So I have to wait for a tile update AND drive over there to test....
abc1357
State Manager
State Manager
Posts: 565
Has thanked: 239 times
Been thanked: 198 times

Post by abc1357
Kartografer wrote:Why not just test the name on a nearby road segment, and then if it sounds right put that name on the place?
Duh! Should have thought of that. Interesting - the English voice for "Va de Vi" pronounces it as "V A de Vee". As in the Letter V, Letter A, sound "duh", sound "vee". I tried "Va. de Vi" with a period and it's voiced as "V A de Vee" also. I tried "Vaa de Vi" and it's voiced as "V A A de Vee"
sketch wrote:No, this should be handled by the TTS team. "Va" with no period and a lowercase "a" should be pronounced as a word. (And "Va."—an accepted, if old-fashioned, abbreviation—should be pronounced as "Virginia")
Since the restaurant was about 10 min out of my way, I decided to drive over and hear exactly what was announced. Using English (US) (Jane) on Android Release 4.19.0.3, the app definitely voiced "Virginia duh vee".

So we now have a case where not only is the pronunciation on the app incorrect, but the pronunciation by WME is different from what is voiced by Jane.

Given that I can't get a pronunciation of "Va" (rhymes with "far"), I'll leave this up to the TTS team.
abc1357
State Manager
State Manager
Posts: 565
Has thanked: 239 times
Been thanked: 198 times