Duly noted, but full disclosure we're still waiting for many pronunciation fixes to be implemented for many months so considering this is not a critical request it will likely be a while for a fix.skreidle wrote:This TTS issue likely affects any drivers who travel I-95 in VA and use exit 89 (Lewistown Rd). subs5 suggested I post this here.
UR: https://www.waze.com/editor/?zoom=5&lat ... 87&env=usa
Waze app (iOS, app v4.7.0.2) has been mispronouncing "Lewistown" as "Luh-WEES-town" -- until I got to the exit ramp, at which point it was the correct "LOO-iss-town". Spelling and punctuation are consistent; TTS cache has been cleared w/no change.
(I've experienced a similar issue approaching Lewiston Rd from Fairview Rd here -- https://www.waze.com/editor/?env=usa&lo ... s=73424264 -- at least twice, but a cache clear resolved that. (It was pronouncing "LOO-iss-tun" as "Luh-WEES-tun".))
Sent from Android using Tapatalk
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien