Phonetic Entry on map and reading on client

If you think you've found a bug on the website which isn't specifically an App or Map Editor problem, or have a request for new or modified feature of the Community, Forums, or Waze website, use this forum.

Moderators: krankyd, Unholy

Re: Phonetic Entry on map and reading on client

Postby AlanOfTheBerg » Tue Jan 29, 2013 5:11 pm

We've been harping on that since the day TTS came out. Waze says they have it on their plan to add this ability to allow better pronunciation.
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19485
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 653 times
Been thanked: 2255 times

Phonetic Entry on map and reading on client

Postby timbucks » Tue Jan 29, 2013 1:33 pm

It would be nice if there was a possibility to add a phonetic name to streets/cities where the TTS clearly pronounces it wrong and then for the client to read it out if it exists.

Everytime I get directions onto Watling Street it pronounces it Wahtling rather than Whatling (I would do it in IPA but I don't know if the forum will render it correctly!)

As a further example in Milton Keynes there are these three districts - Loughton, Broughton and Woughton [on the Green] - the first ou is pronounced as in loud, in the second it's pronounced as in raw, and in the third it's pronounced as in wuff...
timbucks
Beta tester
Beta tester
 
Posts: 227
Joined: Sat Jan 07, 2012 8:30 pm
Has thanked: 4 times
Been thanked: 2 times


Return to Website & Community Issues and Requests

Who is online

Users browsing this forum: No registered users