CBenson wrote:Do we have any current indication that waze is working to fix the bug? N is voiced "en" for this segment named "Baltimore-Washington Pkwy N / to I-95 / Baltimore" as well.
This has fallen back into my lap. Waze IS aware that a problem exists. However they are waiting for me to send specific examples.
I have somewhat narrowed the issue down to some combination of abbreviations and the slash mark.
Without out trying to narrowed the issue further, I will try to compile my findings along with theseveral recent examples and send them.
No action on abbreviations has been possible for the last few months as Waze was making changes. Just in the last couple weeks they now are ready to resume TTS issue resolutions.