Waze forum

We have a number of "Causeway Blvd" in the Tampa Bay area that are mispronounced as Davisnado mentions above.

Causeway is pronounced correctly. Causeway Blvd is pronounced Causewell Blvd. This is specific to Jane.

Example https://www.waze.com/editor/?env=usa&lo ... %2F2184962

Additional URs reporting that Causeway Blvd is pronounced Causewell Boulevard with the Jane voice

Thanks

Actually, enclosing N/E/S/W in brackets also makes it say the directions.

Is there no way Waze would be willing to allow direct access to the TTS API so this could all be tested easily? Or at least give us a list of the exceptions they have in place. From that, we can conclude that everything else will be said the same as on the Nuance Vocalizer Demo online.

We use a space before and after, not inside the brackets. It does create a slight pause, yes.

Sent from my Telenor_OneTouch using Tapatalk

Can't see from phone if it's there, but Cr gives County Road. Annoying here as it's our convention for Crescent.

Sent from my Telenor_OneTouch using Tapatalk

In that case the first one ()

Sent from my Telenor_OneTouch using Tapatalk

We seem to have lost cardinal directions here ie (N) (S) etc

Sent from my GT-I9100P using Tapatalk 2

Arriving at Street or road without a name is a personal favourite...

Sent from my GT-I9100P using Tapatalk 2

That'll be the asphyxiation

Sent from my GT-I9100P using Tapatalk 2