I am still experiencing TTS not speaking road shield (strategic route numbers) properly. For example, Permalink is a FW and it contains road shield “{7}” in the segment name.
With English TTS, it only speaks “Keep Right” but unable to speak the segment name at all. I would expect it to speak “Keep Right onto Route Seven Kwun Tong, Tseung Kwan O, Hong Kong (East)”, or at least skipping the route number (like it normally would skip any Chinese text that TTS is unable to pronounce), instead of skipping the segment name entirely.
However, sometimes I do hear English TTS speak the segment name including strategic route number without problems if that FW segment is the beginning of a FW (e.g. previous inbound segment is a PS or mH).
With Cantonese TTS, it never was able to speak any road shield numbers regardless of previous segment’s type.
It would be more user-friendly if TTS could speak the strategic route number in FW junction and exit (including ramps).
How do we contact Waze staff to correct the TTS issue? Without solving this issue, all segment names cannot include strategic route numbers, and the road shields could only serve cosmetic appearance purpose on the map, but not helping navigation.
Hi Keith,
I have passed on your query to Waze and hopefully someone will respond here.
Cheers,
Leo
Oh btw, did it happen before or just recently?
And which voice you chose? I’ll try to reproduce it and record it and send the video to Waze.
I use Kate for English and 靜宜 for Cantonese. It’s not something that changed recently. It has been the same since day 1, and a few weeks ago I did ask whether route shield numbers’ TTS are only available in certain segment types. At first I thought it never work on ramps, now I think it doesn’t work on some FWs too. It’s either because the segment name is too complicated (mixed with commas, Chinese text etc) or some other reasons. I haven’t figured out why. We need to trial and error it more
Sent from my iPhone using Tapatalk
Sorry forgot to reproduce the issue. Quite busy last night and big snow here. Get home quite late last night. This morning I needed to spend extra hour to get to work due to snow. Anyway, I’ll try to do this tonight after work.
Sent from my 9001X using Tapatalk
No worries. Take your time. It’s not something very urgent. I have a feeling it has been here for a long time, so it doesn’t matter to wait a little bit longer. 
I just want to get it fixed, especially the Cantonese TTS
Keith, do you know about Transifex. We use it to translate Waze to Chinese. You can join us to the Localization Team to help in translation.
Oh I have created a new post here about Transifex and Localization Team.
https://www.waze.com/forum/viewtopic.php?f=146&t=248772
Update:
The problem with TTS not being able to speak road name when road name contains road shield number seems to be fixed, probably because of Waze’s new release of Chinese HK voice. I can see TTS pronouncing the road shield number recently, yet it only speaks the number. For example, {5} it speaks “five”, but not “route five” as it used to be.
I am using English (UK) Kate. Have not experimented it yet with Cantonese TTS.
Chinese HK has not been launched yet as you may realise that we are still discussing the Name for each Chinese dialects. May be Waze has done something behind the scene that already taken effect but I believe Waze says the ‘5’ just because it is actually 5 in the sentence and the feature ‘route 5’ has been removed.
I have reported the Route number thing to Waze. Hope they can fix it.
Would be good if they can translate route numbers in cantonese too.
For example,
{5}
translates to
5 號幹線
Thanks for the reminding. Yes, Waze is dealing with it but I have a feeling they are quite busy atm. Possibly preparing the meeting.
oh so quick this time. Waze informed me that it is fixed now. try to clear cache again and test it
For English, it is fixed. For Cantonese, it still say the number only.