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

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

Moderator: MapSir

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby Onmywaysir » Tue Apr 04, 2017 3:50 am

'keeps saying Skelby instead of Shelby.'

Reporter Sat Apr 01 2017, 23:20
I was using Jane also. Destination was somewhere in Forest City, NC. The only time the word Shelby was spoken was at the exit.

https://www.waze.com/editor/?env=usa&lo ... st=7298855
Onmywaysir
Area Manager
Area Manager
 
Posts: 348
Joined: Tue May 01, 2012 6:52 pm
Location: Asheville
Has thanked: 210 times
Been thanked: 11 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby NJMedic2535 » Sun Apr 02, 2017 1:15 am

I was told this is the right place to post ... if not, let me know and I'll move it.

Encountered a strange mispronunciation with Jane.
https://www.waze.com/editor/?env=usa&lo ... st=7298685

Road is Cookstown (Cook's Town) but was pronounced cukes town (like short for 'cucumber').

Thanks!

-Greg
NJMedic2535
Area Manager
Area Manager
 
Posts: 251
Joined: Tue Oct 27, 2015 12:05 am
Location: North Hanover, NJ - USA
Has thanked: 56 times
Been thanked: 25 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby sikemever » Sat Apr 01, 2017 12:47 am

Pronunciation of "Loudoun" in Virginia. Loudoun is a county in Virginia. Hence, lots of things are named using "Loudoun", (e.g. Loudoun County Parkway). The correct pronunciation is just like the world "loud" with a "un" at the end. Waze however pronounces it as "Load" with a "un". I can't think of a single word in the US English Language that prounounces "xOUD" like "xOAD". Is this the place to get that corrected?
sikemever
 
Posts: 36
Joined: Fri Apr 08, 2016 4:05 pm
Location: Pennsylvania
Has thanked: 6 times
Been thanked: 6 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby xanderb » Fri Mar 31, 2017 11:52 pm

Kartografer wrote:I requested a correction for Coshocton and Scioto a year ago and they still sound like Keyshokton and Seoto. Is there any movement with TTS fixes?


PM me a link to that post please.
xanderb
Local Champ Mentor
Local Champ Mentor
 
Posts: 680
Joined: Sat Jul 10, 2010 6:12 pm
Location: Louisville, KY
Has thanked: 439 times
Been thanked: 343 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby Kartografer » Fri Mar 31, 2017 11:11 pm

Ha yeah I was thinking German. Sometimes I wish English writing was as phonemic as German. But back to TTS problems, I requested a correction for Coshocton and Scioto a year ago and they still sound like Keyshokton and Seoto. Is there any movement with TTS fixes?

Sent from my LG-H811 using Tapatalk
Kartografer
Wiki Master
Wiki Master
 
Posts: 345
Joined: Wed Dec 23, 2015 2:32 pm
Location: Westerville, Ohio, USA
Has thanked: 164 times
Been thanked: 135 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby qwaletee » Fri Mar 31, 2017 9:57 pm

Kartografer wrote:
DrDisaster wrote:Chili is not pronounced like the food or chilly weather. It should be a long I like eye. Ch-eye-l-eye

xanderb wrote:In most cases where a word or road name is very commonly pronounced a certain way, it is impossible to replace for a single road. Those TTS replacements are done for the whole country.

Yes, a word can only be pronounced one way. For example, I'm sure New Yorkers would like Waze to read Houston St as "hauston street," but since Houston is pronounced as "hyuston" in the rest of the US we can't change it without making the pronunciation incorrect to more people.



German hauston?
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2919
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1128 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby DrDisaster » Thu Mar 30, 2017 6:59 pm

I see. Didn't know that.
DrDisaster
 
Posts: 825
Joined: Sun Jan 04, 2015 8:05 pm
Location: Rochester, New York, USA
Has thanked: 547 times
Been thanked: 113 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby Kartografer » Thu Mar 30, 2017 6:57 pm

DrDisaster wrote:Chili is not pronounced like the food or chilly weather. It should be a long I like eye. Ch-eye-l-eye

xanderb wrote:In most cases where a word or road name is very commonly pronounced a certain way, it is impossible to replace for a single road. Those TTS replacements are done for the whole country.

Yes, a word can only be pronounced one way. For example, I'm sure New Yorkers would like Waze to read Houston St as "hauston street," but since Houston is pronounced as "hyuston" in the rest of the US we can't change it without making the pronunciation incorrect to more people.
Kartografer
Wiki Master
Wiki Master
 
Posts: 345
Joined: Wed Dec 23, 2015 2:32 pm
Location: Westerville, Ohio, USA
Has thanked: 164 times
Been thanked: 135 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby xanderb » Thu Mar 30, 2017 6:42 pm

You probably could have combined those into one post since it is all the same road name. In most cases where a word or road name is very commonly pronounced a certain way, it is impossible to replace for a single road. Those TTS replacements are done for the whole country.
xanderb
Local Champ Mentor
Local Champ Mentor
 
Posts: 680
Joined: Sat Jul 10, 2010 6:12 pm
Location: Louisville, KY
Has thanked: 439 times
Been thanked: 343 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby DrDisaster » Thu Mar 30, 2017 6:40 pm

.
Last edited by DrDisaster on Thu Mar 30, 2017 7:05 pm, edited 1 time in total.
DrDisaster
 
Posts: 825
Joined: Sun Jan 04, 2015 8:05 pm
Location: Rochester, New York, USA
Has thanked: 547 times
Been thanked: 113 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users