I will do that if I get anymore updates or UR's.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
so i just noticed that this is fixed on my drive home. thanks!!PesachZ wrote:It means we have diagnosed the issue and the fix but are waiting for the backlog to clear for that type of issue before submitting new ones. Most pronunciation issues get sent to the vendor for fixing, so we send a batch, wait for results before sending more.cshinn89 wrote:what does ready to submit mean on the wiki list?
Sent from Android using Tapatalk
If you put single quote marks around the E like this 'E' then the TTS works. N, S, E and W work the same way.taddison1 wrote:A street near me, called "Ira E Woods" was/is being pronounced "Ira East Woods". The "E" is a middle initial, not a direction, so it needs to say "eee" instead of "East".
I looked at the spreadsheet, and it seems to suggest that adding a period after the E would cause it to say "eee", but then there's an accompanying note that says "n/a See East" which seemed contradictory.
Regardless, I recently added the the period, but last time I drove there it still said "East". Should this have worked? Do I just need to clear my tts cache and try again? If it makes a difference, I'm on IOS, not Android.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien