# Test of Text-to-Speech (TTS) Abbreviations in Waze Clients
**URL:** https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949
**Category:** United States
**Created:** [January 18, 2012, 7:07pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949 "2012-01-18T19:07:25Z")
**Posts on this page:** 20
**Page:** 62
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 25, 2015, 10:21am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1221 "2015-08-25T10:21:36Z")
> [@whatnt](#):
>
> No. Regular n rather than ñ, and neh like “never”. And stress on the second syllable: mih-'neh-tah
>
> If it helps, the name is Japanese.
OK does [this](https://dl.dropbox.com/s/0a5z86mgvqezek7/Turn%20right%20to%20Mineta%20Airport%202.mp3) sound better?
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 25, 2015, 10:40am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1222 "2015-08-25T10:40:37Z")
> [@dsfargeg](#):
>
> So my turn onto Latta Road was:
> from [Manitou Rd Southbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275916)
> To [Latta Rd Eastbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275915)
I’m not hearing it wrong, or I’m not understanding what you’re hoping to hear. Are you able to get the tts file that sounds wrong, and one that sounds right from your phone?
---
### Author:  [@dsfargeg](https://www.waze.com/discuss/u/dsfargeg)
#### Post date: [August 25, 2015, 11:05am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1223 "2015-08-25T11:05:28Z")
> [@PesachZ](#):
>
> > [@dsfargeg](#):
> >
> > So my turn onto Latta Road was:
> > from [Manitou Rd Southbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275916)
> > To [Latta Rd Eastbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275915)
>
> I’m not hearing it wrong, or I’m not understanding what you’re hoping to hear. Are you able to get the tts file that sounds wrong, and one that sounds right from your phone?
Files attached.
1440499777-887347-10.tts: Correct pronounciation when reading the address of the destination on Latta Road.
1440499779-24500-21.tts: Incorrect pronounciation when turning from Manitou to Latta.
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 25, 2015, 11:26am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1224 "2015-08-25T11:26:14Z")
> [@dsfargeg](#):
>
> > [@PesachZ](#):
> >
> > > [@dsfargeg](#):
> > >
> > > So my turn onto Latta Road was:
> > > from [Manitou Rd Southbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275916)
> > > To [Latta Rd Eastbound](https://www.waze.com/editor/?env=usa&lon=-77.74877&lat=43.25315&layers=1933&zoom=4&segments=62275915)
> >
> > I’m not hearing it wrong, or I’m not understanding what you’re hoping to hear. Are you able to get the tts file that sounds wrong, and one that sounds right from your phone?
>
> Files attached.
> 1440499777-887347-10.tts: Correct pronounciation when reading the address of the destination on Latta Road.
> 1440499779-24500-21.tts: Incorrect pronounciation when turning from Manitou to Latta.
The pitch and tone of the prompt is different, but neither sounds more like landa than Latta to me. I’m not sure we’ll be able to do anything on this one.
Sent using Tapatalk for Android
---
### Author:  [@dsfargeg](https://www.waze.com/discuss/u/dsfargeg)
#### Post date: [August 25, 2015, 11:33am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1225 "2015-08-25T11:33:56Z")
> [@PesachZ](#):
>
> > [@dsfargeg](#):
> >
> > Files attached.
> > 1440499777-887347-10.tts: Correct pronounciation when reading the address of the destination on Latta Road.
> > 1440499779-24500-21.tts: Incorrect pronounciation when turning from Manitou to Latta.
>
> The pitch and tone of the prompt is different, but neither sounds more like landa than Latta to me. I’m not sure we’ll be able to do anything on this one.
>
> Sent using Tapatalk for Android
Guess we’ll have to agree to disagree. How should I respond to the ur?
Sent from my XT830C using Tapatalk
---
### Author:  [@whatnt](https://www.waze.com/discuss/u/whatnt)
#### Post date: [August 25, 2015, 2:15pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1226 "2015-08-25T14:15:50Z")
> [@PesachZ](#):
>
> OK does [this](https://dl.dropbox.com/s/0a5z86mgvqezek7/Turn%20right%20to%20Mineta%20Airport%202.mp3) sound better?
Sounds great!
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 25, 2015, 10:22pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1227 "2015-08-25T22:22:17Z")
> [@dsfargeg](#):
>
> > [@PesachZ](#):
> >
> > The pitch and tone of the prompt is different, but neither sounds more like landa than Latta to me. I’m not sure we’ll be able to do anything on this one.
> >
> > Sent using Tapatalk for Android
>
> Guess we’ll have to agree to disagree. How should I respond to the ur?
>
> Sent from my XT830C using Tapatalk
The difference is just not distinct enough for me to be able to work on a replacement. Potentials. Legal someone else will be able to figure it out, but not I. You can respond that the wrong pronunciation is so close to the correct pronunciation that out will be hard to fix in the near future.
Sent using Tapatalk for Android
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 25, 2015, 10:22pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1228 "2015-08-25T22:22:37Z")
> [@whatnt](#):
>
> > [@PesachZ](#):
> >
> > OK does [this](https://dl.dropbox.com/s/0a5z86mgvqezek7/Turn%20right%20to%20Mineta%20Airport%202.mp3) sound better?
>
> Sounds great!
Ok is on the list
Sent using Tapatalk for Android
---
### Author:  [@dsfargeg](https://www.waze.com/discuss/u/dsfargeg)
#### Post date: [August 27, 2015, 4:46pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1229 "2015-08-27T16:46:48Z")
So driving around, i’ve found 3 more TTS problems. It seems like this could get out of hand easily. Do we have a “good enough” threshold, or do we want to report everything?
Sent from my XT830C using Tapatalk
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [August 27, 2015, 7:10pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1230 "2015-08-27T19:10:34Z")
> [@dsfargeg](#):
>
> So driving around, i’ve found 3 more TTS problems. It seems like this could get out of hand easily. Do we have a “good enough” threshold, or do we want to report everything?
>
> Sent from my XT830C using Tapatalk
Personally if it isn’t confusing, or obviously wrong, I don’t bother.
---
### Author:  [@SocalToe](https://www.waze.com/discuss/u/SocalToe)
#### Post date: [August 27, 2015, 8:35pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1231 "2015-08-27T20:35:15Z")
I’d go with good enough…
I’ve heard some that are slightly off, but wouldn’t be able to describe what’s wrong.
I think some of the ‘slightly off’ ones have the correct syllables, but the timing is off slight pauses, or lack of pauses
---
### Author:  [@dsfargeg](https://www.waze.com/discuss/u/dsfargeg)
#### Post date: [August 27, 2015, 8:39pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1232 "2015-08-27T20:39:40Z")
Opinion wanted:
Jane pronounces Hylan drive in Henrietta NY so it rhymes with Dylan. Should be HIGH-lin. Confusing enough to change? If so i’ll provide the segment links and TTS files.
Sent from my XT830C using Tapatalk
---
### Author:  [@bummerdude69](https://www.waze.com/discuss/u/bummerdude69)
#### Post date: [September 8, 2015, 2:36am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1233 "2015-09-08T02:36:56Z")
[https://wiki.waze.com/wiki/Abbreviations\_and\_acronyms](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?
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [September 8, 2015, 3:22am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1234 "2015-09-08T03:22:53Z")
> [@bummerdude69](#):
>
> [https://wiki.waze.com/wiki/Abbreviations\_and\_acronyms](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](https://wiki.waze.com/wiki/Abbreviations_and_acronyms/USA#Standard_suffix_abbreviations) (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
---
### Author:  [@bummerdude69](https://www.waze.com/discuss/u/bummerdude69)
#### Post date: [September 8, 2015, 5:34pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1235 "2015-09-08T17:34:47Z")
> [@PesachZ](#):
>
> 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”](https://www.waze.com/editor/?env=usa&lon=-110.96461&lat=32.18134&zoom=3&venues=163184962.1632111762.434579) is being pronounced as Virginia rather than just VA (“vee” “aa”).
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [September 8, 2015, 6:45pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1236 "2015-09-08T18:45:57Z")
> [@bummerdude69](#):
>
> > [@PesachZ](#):
> >
> > 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”](https://www.waze.com/editor/?env=usa&lon=-110.96461&lat=32.18134&zoom=3&venues=163184962.1632111762.434579) 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
---
### Author:  [@bummerdude69](https://www.waze.com/discuss/u/bummerdude69)
#### Post date: [September 8, 2015, 7:21pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1237 "2015-09-08T19:21:16Z")
> [@PesachZ](#):
>
> > [@bummerdude69](#):
> >
> > > [@PesachZ](#):
> > >
> > > 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”](https://www.waze.com/editor/?env=usa&lon=-110.96461&lat=32.18134&zoom=3&venues=163184962.1632111762.434579) 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]
---
### Author:  [@PesachZ](https://www.waze.com/discuss/u/PesachZ)
#### Post date: [September 9, 2015, 1:05am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1238 "2015-09-09T01:05:09Z")
> [@bummerdude69](#):
>
> 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.
---
### Author:  [@gunnargsd](https://www.waze.com/discuss/u/gunnargsd)
#### Post date: [September 11, 2015, 11:56pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1239 "2015-09-11T23:56:11Z")
Reporting a TTS issue:
- Britton Pkwy
- Being pronounced “Britt”
- BRIH-tuhn - [http://inogolo.com/pronunciation/Britton](http://inogolo.com/pronunciation/Britton)
- [https://www.waze.com/editor/?env=usa&lon=-83.13960&lat=40.07516&zoom=5&segments=77923959](https://www.waze.com/editor/?env=usa&lon=-83.13960&lat=40.07516&zoom=5&segments=77923959)
Thank you
---
### Author:  [@taco909](https://www.waze.com/discuss/u/taco909)
#### Post date: [September 12, 2015, 2:46am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/1240 "2015-09-12T02:46:41Z")
Recent change…
“Verdugo” = “Ver-doo-go”
Recently been throwing in an extra syllable “Verdoodigo”
[Previous page](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949.md?page=61)
[Next page](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949.md?page=63)