Waze: outsmarting traffic together
https://www.waze.com/forum/
Well, it certainly pronounces 'Close' better for me, but I'll wait for some AMs/CMs to come along and commentabigaile wrote:Hi everyone
Yesterday, Google TTS responded to my bug regarding this and said they won't be able to fix it. They explained that the way the system is set means the word "to" will always trigger the verb pronunciation of close.
Currently our abbreviation for Cl is klos which sounds bad.
In my opinion the abbreviation we used before "klohwss" sounds a bit better.
I've been trying to find other ways to spell "close" to get the correct pronunciation but nothing worked. But I have another idea. When I checked "Malham Close turn right into Close" it sounded much better.
I can create an abbreviation that will look for "to/onto Cl" and turn it to "into Close"
Here's a recording of how it would sound:
What do you think?
That does indeed sound much better, and also fits well when the Close is a cul-de-sac. Please make it so!abigaile wrote:I can create an abbreviation that will look for "to/onto Cl" and turn it to "into Close"
Phew! I thought I was hearing things for a while.Dave2084 wrote:So ... this went live today, but seems to have broken TTS completely (every street gets to have 'Close' in it!).
I've asked Abigail to revert it!
"Take the second exit to close Finkle Hill". "In 1000 feet, turn right onto close A19"... Thanks for fixing!