jondrush wrote:Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?
AlanOfTheBerg wrote:Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan..
dctdye wrote:I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:
https://www.waze.com/editor/?zoom=6&lat ... nts=956781
dctdye wrote:Figured it was something simple like that. That's hopefully fixed now. Thanks
qwaletee wrote:It would be interesting to know the distribution of signs using Br for Bridge versus using Br for Branch, so that we could know which to assign causing the fewest issues.
qwaletee wrote:Update on 9W. Text to speech says West. Ouch. I can't see manually updating every segment to use 9'w' instead of 9w. Also, I believe the quotes do show up, so 9'w' would be a problem. Maybe 'US-9w'?
qwaletee wrote:I have observed that this could be happening when my phone is bogged down with other tasks. Perhaps the thread that expands abbreviations has a low priority, and if it doesn't run in time, Waze just reads it as-is.
orbitc wrote:Here is the link:
Users browsing this forum: No registered users