Is it possible that frequently encountered TTS data - like, say, reading the same phrases over and over again because you keep driving to work the same way - causes that TTS data to be accessed from a local cache?
In an unrelated observation, we seem to have a bunch of Tnl abbreviations on the Turnpike in northern NJ being read as its letters (tee en el), as opposed to Tunnel. This makes the Turnpike's references to the Holland and Lincoln Tunnels sound really weird. Is this a known bug/limit of the TTS and the Tnl abbreviation?
In an unrelated observation, we seem to have a bunch of Tnl abbreviations on the Turnpike in northern NJ being read as its letters (tee en el), as opposed to Tunnel. This makes the Turnpike's references to the Holland and Lincoln Tunnels sound really weird. Is this a known bug/limit of the TTS and the Tnl abbreviation?
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien