beej666 wrote:i still don't understand how the fix gets made. i've been made to understand that somebody from the Google Waze team will need to fill out some sort of request upstream with the TTS provider. who is that person? how does my request get in their inbox?
Normally things like local street names don't get fixed. We usually only fix things of significant exposure, so a name on a few streets, in only a few places is jot likely to get fixed at all.
If it's a more popular name as sketch suggested this is, then it can be corrected.
- The process start with you posting here. (Done)
- Some research into the popularity of the name, and any potential conflifts with other names. Also research on proper pronunciation in different regions. (If a name is pronounced differently in doesn't locales it likely won't be fixed either since it will always be wrong somewhere.)
- Once it's determined a fix is required, a group of champs who spend a lot of time on this project (incl. GizmoGuy411, sketch) can then craft a string that will sound right when read by the TTS engine, and test it in various contexts. (Bueno might be converted to "bwen oh" for example)
- Code is developed to determine when the name should be replaced in context.
- That pair of name and converted string with the filtering code for when to use it is then submitted to Waze staff for inclusion in their TTS software as a custom abbreviation.
Reach of these steps takes time and effort, and some names are higher priority, with a larger effect than others. Obviously the higher priority names go first.
You have made the right steps, now things just have to run their course.
Thanks for your report and enthusiasm. Happy wazing.
Sent using Tapatalk for Android 4.4.2