I would like to have a phonetic spelling option added to the map editor so that the text to speech engine can properly pronounce landmarks properly. Local editors should be able to update streets and city names using phonetic spelling to match local pronunciation. Waze should default to the proper spelling, but if a phonetically spelled name exists, it should override the default.
iPhone’s now have the ability to add phonetic spelling for contacts. Seems like the same feature should be able to be applied to the voice navigation…?
I like this idea – we have names in three or four languages here – I think that one of the possible concerns is the vast scope for vandalism, with the phonetic spelling being something entirely different to the original word. “Turn right into stupid stupid stupid avenue”. A few basic checks that the consonants appear in the same order, and without too many omissions would pretty much eliminate that problem.
A lot of consonants can be omitted from the pronunciation of words which are French or British in particular. How would you write Knee, Colonel, Wednesday, Worcester, Versailles, Bordeaux, Champagne, Louisiana, and numerous others?
The whole point of having a phonetic spelling is because many names are not pronounced the way they are spelled.
Entering a malicious pronunciation is no different from other vandalism. Anyone who vandalizes and gets caught will be banned.
I would be more interested in how you will solve questions like the correct pronunciation for a place like Baltimore, New Orleans, or many others.
Hah. Well, there are some things which can be solved easy—like, it’s definitely not pronounced “Esplanahhhhde”. We can worry about the subtleties like “Bur-GUN-dy” and “CAL-li-ope” later.
Phonetic pronunciation provided by map editors would be really beneficial.
Seems like a user could suggest a phonetic pronunciation (for example, Lampasas should be lampassas, not lampahsas.) Have a way to preview what your suggested phonetic pronunciation would sound like. If you like it, submit it. Have other editors have the option to vote up the suggested pronunciation. If it receives X votes, it replaces the TTS version.
If there are regional differences (like, New Orleans), seems like multiple pronuncations could be suggested, and the vote battle would take care of which one should be used. Whatever one most people want to hear.
I think this is also needed for mis-interpreted abbreviations. I have a nearby road that is entered as “Culebra Rd St Mary’s Univ” which of course she pronounces as “Street Mary’s Univ”.
It is beneficial to maintain the text on the roadsigns, but editors need to let the voice navigation know what to say.
How would this work for someone using an ‘out of market’ voice? i.e. I live in Canada and use a UK voice, or sometimes a German or Spanish voice when I feel like it. Different voices have their own pronounciation rules. Would we all have to learn the phonetics alphabet? How do you type that upside down 3 or a я without changing keyboard layouts?