Since the old thread was meant for testing the Samantha voice, I thought it would make sense to close that one officially and open a new one for discussing issues with the newer voices.
Please continue to use this form to report issues with the new voices in the United States, but this thread or the #tts discord channel can be used to discuss them further.
First thanks for the new forum.
Second, can we get District of Columbia added as a state?
Bladensburg Rd NE is not pronounced correctly.
Pronounced by Jane with a short a vice a long one.
Incorrect Blad ens berg road northeast
Correct Blade ens berg road northeast.
I added DC to the form and processed your submission
Thank you very much.
I have noticed that Houston was not being pronounced correctly.
It depends on where you are. There are two very famous Houstons in the US. One of them pronounced their name wrong. I won’t say which one. 
:lol: :lol: :lol:
Form won’t open for me so posting here and will transfer once at a computer that allows it.
Update 4/9/18 10:00 EDT Had someone send me full link to the form. Submitted the information there.
Washington, DC
Loughboro Rd NW
It is pronounced like Marl burr oh (Marlboro)
Should be pronounced as Low burr oh
@subs5,
I changed the form link to the full URL instead of the shortened version from WME.
The abbreviation spreadsheet Iframe is not loading from the wazeopedia page. I can’t load it out of a frame either - looks like the sheet itself has problems?
{{#widget:Iframe |url=https://docs.google.com/spreadsheets/d/1-K3YMyIgos-fidRtMbKHFpIRzlAQu9DGYFk7PoedwzY/pubhtml?gid=1231483217&single=true |width=500 |height=1000}}
It loads fine outside of the iframe. There might be issues from the MediaWiki update. Try this link.
So, I have another UR for Houston pronunciation. The reporter submitted a request through the Google Docs link. Thoughts?
Just submitted a pronunciation issue on the form Xander. Let me know if you have any questions pertaining to it.
Over the past six months, I’ve filled out a Google doc request twice now for a street here in Orlando. Not heard anything back and street TTS is still incorrect. Name: N Econlockhatchee Trl (and S)
Currently pronounced incorrectly: Eh kin lat chee
Correct: E con lock hatch e (5 syllables) Long E on both ends
Thank you for any help and advice to get this changed.
Can we get “E-ZPass” added to the Abbreviations and acronyms table since that’s how it needs to be for Jane TTS? I’ve had some ask me what the correct spelling should be. Possibly other toll passes as well, if there is any confusion.
Came across a new (at least to me) abbreviation that could merit some discussion. The street name is published in GIS and on the developer’s on-site map as “Geo. Meyer Ave”, the “Geo.” is short for George (the name of the developer). While no street signs are posted yet, it could be safely assumed that they’ll be printed as “Geo. Meyer Ave”.
The question becomes, do we follow the naming scheme of the LGS/GIS so the map matches the sign, and if so can we get the TTS to pronounce “Geo.” as “George”? I am assuming there are street names with “Geo” (without the “.”) so that should remain pronounced as-is.
You can report the issue on this form.
But normally the abbreviations are for standard abbreviations used nationwide so it may not be added.
Have you looked up the USPS address to see if the use Geo or George?
Ha anyone noticed problems with letters being pronounced in conjunction with exit numbers?
Thanks,
Ted
Have you heard of “A” not being pronounced correctly on exits?
You can report the issue on this form.
But normally the abbreviations are for standard abbreviations used nationwide so it may not be added.
Have you looked up the USPS address to see if the use Geo or George?
[/quote]
[/quote]
I’ve seen users in the UK complaining about this as well