Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

[mapcat]

Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Isn't that because it's French? (i.e. Nord, Sud, Est, Ouest = North, South, East, West)

Wouldn't it just be easier to use N, S, E, W as the cardinal (compass) directions in Waze? And then you can change the language in the app to either Engilsh (and get North, South, East, West) or French (and get Nord, Sud, Est, Ouest) - I think, I'm not about to change my Waze to French as I may never get it back to English.

No, he's saying that Waze pronounces roads like "Autoroute 20 Est" as "Autoroute Twenty Estate" instead of the preferred "Autoroute Vingt Est".

Unfortunately, the North America server (USA+Canada) only has English TTS at the moment, and until all the Anglo pronunciations are correct, I doubt they'll be able to work on the other languages.

[NicoPapa29]

I live in South Africa and find WAZE a brilliant application.
Problem is that TTS is wrongly describing our HighWays.

All South Africa's National Highways and Roads are "Prefixed" with an "N"
The "N" stands for "NATIONAL"

In Johannesburg the major highways are:
N3
N1

TTS translates this to "North 3"
It should remain as "N3" because the N SHOULD NOT translate to "North" and no one refers to them
as "National 3" so that wouldnt make sense either.

TTS should remain as "N3"

How can this be achieved?

[jasonh300]

Should be pretty simple to fix if the N and the 3 don't have a space between them. (do they?)

Send a request to support via nanorep on the support page.

[gerben]

In The Netherlands, N roads are pronounced correctly, so this should be possible (we do write those as Nxxx, so without a space).

[image619]

I tried to browse the thread and didn't see an answer to this, but I apologize if I'm treading on covered ground.

Is there any way to force the client to not translate a road name? In San Diego, we have a road names Upas St, and the client calls in Underpass St. (according to a problem report).

Here it is, in case you're interested:
https://www.waze.com/editor/?zoom=5&lat ... ts=6989588

[gettingthere]

Is there any way to force the client to not translate a road name? In San Diego, we have a road names Upas St, and the client calls in Underpass St. (according to a problem report).

Here it is, in case you're interested:
https://www.waze.com/editor/?zoom=5&lat ... ts=6989588

I would recommend that you contact Waze support regarding this. I don't know that upas should be an abbreviation for underpass. They should be able to fix this in the English TTS.

www.waze.com/support

Also, thanks for your contributions to the map in San Diego.

[image619]

It is on Gizmoguy's spreadsheet, and listed as USPS standard abbreviation, so it's probably correct. However, it has an unwanted side effect in this case.

[harling]

Upon arrival, TTS announces, "arriving at [name], at [address]", where [name] is the name of the favorite and [address] is the street address. For example, if my "Home" favorite is set to 23 Main St, Boston MA, it will announce, "arriving at home, at twenty-three main street." So far, so good.

For destinations that are not named favorites, [name] is the street address followed by the city. So if 23 Main St, Boston MA is not a favorite and I just navigate to it by address or via a History entry, it announces, "arriving at twenty-three main saint boston, at twenty-three main street". Oops!

I said over and over, and others said over and over, that the TTS rendering of abbreviations should not be positional. This is why.

[xteejx]

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

Sent from my GT-I9100P using Tapatalk 2

[invented]

Waze still won't fix "QEW" to just say the letters. They don't have some kind of substitution power? Like when the software encounters "QEW" it feeds "cue eee double you" to the TTS engine?