Abbreviations and acronyms: Difference between revisions Discussion View history

m (→‎{{@|Recommended abbreviations}}: expand BGS acronym on first usage)
m (fixed capitalization, semicolon and phrasing of mbox)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{mbox|text=This page is being developed for use with the '''Jane voice''' in the USA, it is also applicable to any country where the new TTS voices are in use. A few of the listed abbreviations are specific to the USA, but most will work in any country with english voice.}}
{{mbox|text=This page is being developed for use with the '''Jane voice''' in the USA; it is also applicable to any country where TTS voices are in use. A few of the listed abbreviations are specific to the USA, but most will work with any English-speaking TTS voice from any country.}}
{{construction
{{construction
| contact    = http://www.waze.com/forum/ucp.php?i=pm&mode=compose&subject=A%20TTS%20Wiki%20Question&username=PesachZ
| contact    = http://www.waze.com/forum/ucp.php?i=pm&mode=compose&subject=A%20TTS%20Wiki%20Question&username=PesachZ
Line 5: Line 5:
| draft      = no
| draft      = no
| open        = no}}
| open        = no}}
This article discusses the application and use of abbreviations and acronyms in segment and place names for Waze, and their impact on the [[Glossary#TTS|TTS engine]]. In the interest of preserving screen real-estate wherever reasonable we prefer to use fewer characters while still achieving the same result. For consistency these guidelines should be followed everywhere so users have a seamless experience.


:''For information on abbreviations and acronyms used in the various communication platforms among Waze editors, please see the [[Glossary]].


== {{@|Standard suffix abbreviations}} ==
== {{@|Standard suffix abbreviations}} ==
Line 30: Line 32:
#* East 207 St. should be written as <code>E 207th St</code> in Waze.
#* East 207 St. should be written as <code>E 207th St</code> in Waze.


== {{@|Recommended abbreviations}} ==
{{anchor|Recommended abbreviations}}
== {{@|Recommended abbreviations and acronyms}} ==


The abbreviations and acronyms in [http://docs.google.com/spreadsheets/d/19NK4-yAlV6gUhlZdjUGHtnfNgZRdAThT_ZUlhd-Dg5Y/pubhtml?gid=1582266922&single=true this following table] have been tested and are recommended to be used wherever applicable in Waze. The only exceptions to their usage should be when the [[Glossary#Big_Green_Sign|big green sign]] (BGS) uses a different abbreviation, '''and''' the abbreviation used on the BGS is supported by the TTS engine.
The abbreviations and acronyms in [http://docs.google.com/spreadsheets/d/19NK4-yAlV6gUhlZdjUGHtnfNgZRdAThT_ZUlhd-Dg5Y/pubhtml?gid=1582266922&single=true this following table] have been tested and are recommended to be used wherever applicable in Waze. The only exceptions to their usage should be when the [[Glossary#Big_Green_Sign|big green sign]] (BGS) uses a different abbreviation, '''and''' the abbreviation used on the BGS is supported by the TTS engine.
Line 38: Line 41:


'''NOTE:''' Pay special attention to any punctuation in the abbreviation column. These abbreviations are case sensitive, and require any punctuation shown to be used in order for them to work.
'''NOTE:''' Pay special attention to any punctuation in the abbreviation column. These abbreviations are case sensitive, and require any punctuation shown to be used in order for them to work.
{{Anchor|TTSwarning}}
{{mbox|type=critical|text=The TTS results from the [[Image:TTS button.jpg|20px| ]] test button in WME are '''{{red|not always customized}}''' by Waze. To ensure you get localized TTS results in WME you must first click {{key press|Apply}},  and then open the address editor again to play the TTS. Otherwise the TTS may not recognize the abbreviations in this list. These abbreviations all still work in the client.<br>
{{U|Please do not "fix" street names because the TTS seems broken when testing it in WME; test in the client first to confirm.}}}}
{{#widget:Iframe
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/19NK4-yAlV6gUhlZdjUGHtnfNgZRdAThT_ZUlhd-Dg5Y/pubhtml?gid{{=}}1582266922&single{{=}}true|border=1
|url=https://docs.google.com/spreadsheets/d/1-K3YMyIgos-fidRtMbKHFpIRzlAQu9DGYFk7PoedwzY/pubhtml?gid{{=}}1231483217&single{{=}}true|border=1
|width=500
|width=500
|height=1000}}
|height=1000}}
Line 65: Line 72:




Forum Thread: '''[http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients]'''}}
Forum Thread: '''[https://www.waze.com/forum/viewtopic.php?f=129&t=253185 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients]'''}}


=== {{@|Pronunciation fixes}} ===
=== {{@|Pronunciation fixes}} ===


Some names and words are not pronounced properly by the TTS engine, in these cases we can work to fix them. These should be reported via the [[#Discussion|forum linked above]]. Once they are reported the TTS team will review them, and work on finding a proper solution. All the names which have been reported to have their pronunciation fixed will be added to a working spreadsheet for tracking.
Some names and words are not pronounced properly by the TTS engine, in these cases we can work to fix them. These should be reported via this [https://goo.gl/forms/9EAYiYW5R6hdewjJ3 form]. Please add your username in the Comments block in case there are followup questions. Once they are reported the TTS team will review them, and work on finding a proper solution. All the names which have been reported to have their pronunciation fixed will be added to a working spreadsheet for tracking.
{{Expand|nt=yes|
{{Expand|nt=yes|
{{#widget:Iframe
{{#widget:Iframe

Latest revision as of 16:20, 19 November 2018

This page is being developed for use with the Jane voice in the USA; it is also applicable to any country where TTS voices are in use. A few of the listed abbreviations are specific to the USA, but most will work with any English-speaking TTS voice from any country.
This new page is currently undergoing modifications. The information and guidance is currently considered accurate enough to be followed now. Content is being prepared by one or more users. Do not make any changes before you send a private message to this user.

This article discusses the application and use of abbreviations and acronyms in segment and place names for Waze, and their impact on the TTS engine. In the interest of preserving screen real-estate wherever reasonable we prefer to use fewer characters while still achieving the same result. For consistency these guidelines should be followed everywhere so users have a seamless experience.

For information on abbreviations and acronyms used in the various communication platforms among Waze editors, please see the Glossary.

Standard suffix abbreviations link to this section

Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road").

Notes:

  1. Abbreviate only suffixes (except as indicated below).
    • "The Avenue", "The Green", etc. should not be abbreviated.
    • "Circuit Avenue Road" is abbreviated "Circuit Avenue Rd", not "Cct Ave Rd".
    • A road named "Service Road" should not be abbreviated, while "Pipeline Service Road" should be (as "Pipeline Service Rd").
    • Prefixes should be abbreviated only when they appear abbreviated on signage.
      • If the signage says "Ave A", then it should be "Ave A" in Waze.
      • If the signage says "Avenue A", then it should say "Avenue A" in Waze.
  2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens).
  3. In the event that the original suffix is a plural (ends in s) and only its singular form is present as an abbreviation, simply adding an "s" to the end of the abbreviation may or may not work as expected unless specified below.
  4. When the letters N, S, E, or W should NOT be pronounced as compass cardinal directions, the letter should be followed with a . (period).
    • George W. Bush Blvd
    • West W. Lee Ave
    If the cardinal letter is part of a larger name, (when it is not alone) it does not require any modification at all.
    • CR-N will be read as County Road en.
  5. Numbered street names which appear on signs as digits should be followed with an ordinal.
    • 8 Ave. should be written as 8th Ave in Waze.
    • East 207 St. should be written as E 207th St in Waze.

Recommended abbreviations and acronyms link to this section

The abbreviations and acronyms in this following table have been tested and are recommended to be used wherever applicable in Waze. The only exceptions to their usage should be when the big green sign (BGS) uses a different abbreviation, and the abbreviation used on the BGS is supported by the TTS engine.

This list is not yet complete, there are other recommended abbreviations from the main Abbreviations and acronyms page which do work, but have not yet been added to this list. They will be added soon.


NOTE: Pay special attention to any punctuation in the abbreviation column. These abbreviations are case sensitive, and require any punctuation shown to be used in order for them to work.

The TTS results from the test button in WME are not always customized by Waze. To ensure you get localized TTS results in WME you must first click Apply, and then open the address editor again to play the TTS. Otherwise the TTS may not recognize the abbreviations in this list. These abbreviations all still work in the client.
Please do not "fix" street names because the TTS seems broken when testing it in WME; test in the client first to confirm.

More information link to this section

Other localities link to this section

Other countries may have differing guidance; refer to the main Abbreviations & acronyms article to see a list the country-specific pages for any local guidance.

Discussion link to this section

Use the following forum thread for discussions and requests related to TTS and abbreviations or acronyms.
  • To report an abbreviation, acronym, or other TTS name which is not working as it should.
  • To request a new abbreviation or acronym be added to the list.
  • If you have any further questions on this topic.
  • To view the current "Work in progress" list of abbreviations that are being tested, currently available, and proposed.


When reporting an issue please make sure to include:
  • The exact spelling of the full segment name as it appears in WME
  • What is wrong about how it is said
  • How it should be said
  • A permalink to the segment in WME


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

Pronunciation fixes link to this section

Some names and words are not pronounced properly by the TTS engine, in these cases we can work to fix them. These should be reported via this form. Please add your username in the Comments block in case there are followup questions. Once they are reported the TTS team will review them, and work on finding a proper solution. All the names which have been reported to have their pronunciation fixed will be added to a working spreadsheet for tracking.

Click Expand for details on the list of all the requested pronunciation fixes, and their current status.

Glossary link to this section

Refer to the Glossary page for definitions of many terms used in Waze.