Test of Text-to-Speech (TTS) Abbreviations in Waze Clients
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.)[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)
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".
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien