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?

Hi everyone

I'm really sorry about this.
I found what was causing it and fixed it.

My tests show it is now resolved and the regex only works for cases where Cl comes after to or onto.

The pronunciation of Close is ok too?

Hi,

Thank you for this information. We are looking into this and, and we will work on solving this issue.

xteejx wrote:Rebecca, I implemented a fix for this with Orit before.

Substitution for this should be

"Cl" = "klohwss"

Can you let us know when it has been changed so we can clear our TTS caches?

Thank you.

Yes, I will definitely let you know when this has changed!

Zirland wrote:Just curious question from someone who is not native in English...
What is the pronunciation difference between Close {not open} and Close {not far}??

Odesláno z mého A511 pomocí Tapatalk

It should be pronounced ‘close’ /kləʊs/ (Link to correct pronunciation) as the opposite of far but instead is pronounced ‘close’ /kləʊz/ (Link to incorrect pronunciation) as the opposite of open.

Bump.

This is still broken.

It did get fixed, then it got broken again (for the third time).

I've sent another reminder to the localisation team at Waze ...