PA at the end of a string is pronounced "Pah" rather than "Pennsylvania"
https://www.waze.com/editor/?env=usa&lo ... st=5036871

(PA at other points in the string is pronounced Pennsylvania)

PesachZ wrote:

voludu2 wrote:PA at the end of a string is pronounced "Pah" rather than "Pennsylvania"
https://www.waze.com/editor/?env=usa&lo ... st=5036871

(PA at other points in the string is pronounced Pennsylvania)

I am not getting this error in testing. Are you experiencing it?

The only way I know to test this is in WME, and I don't trust WME to tell me what the app is going to say. So I took the UR information at face value.

King of Prussia pronounced "King of Prussias" in some instances. What I hear in WME seems identical to what I heard in the app.

Turning right onto this segment, Prussia was pronounced "Prussias". It is before a "/" here
Prussias

When I removed the "/" from the string and tried again in WME, Prussia was pronounced correctly.

Whereas, staying right onto this segment, Prussia was pronounced correctly. It is the end of the string here:
Prussia

Issue: Captain is pronounced Captainine
Voice: in app: USA/Jane. Also in WME
Device: iphone or WME

https://www.waze.com/editor/?env=usa&lo ... =502198635
https://www.waze.com/editor/?env=usa&lo ... st=5170352


The abbreviation Capt is pronounced as Captain
https://www.waze.com/editor/?env=usa&lo ... =502198661
It is really as if TTS expands the abbreviation "Capt" within the word "Captain" in order to get an extra syllable in the middle.

cshinn89 wrote:

PesachZ wrote:

cshinn89 wrote:what does ready to submit mean on the wiki list?

It means we have diagnosed the issue and the fix but are waiting for the backlog to clear for that type of issue before submitting new ones. Most pronunciation issues get sent to the vendor for fixing, so we send a batch, wait for results before sending more.

Sent from Android using Tapatalk

so i just noticed that this is fixed on my drive home. thanks!!

I have also noticed that Paoli is pronounced correctly, as well, so I can tell that progress is being made.
Yay!

Initially reported here two years ago
IPA rendering of this place / street name is: ˈjuːklən

voludu2 wrote:Uwchlan
Jane pronounces it "U.W. clan"
Should be "you-chlƏn" (schwa sound in second syllable)

https://www.waze.com/editor/?env=usa&lo ... s=75534767

Already submitted to the beta app form.

I can hear this pause in WME. So it's not like its caused by a bad value in your TTS cache.

Same pause in the other ramp to US-501

I hear something similar
on this exit from I-95 to US-202. It actually sounds like the "0" is being drawn out.

Strangely, I don't hear that pause in "202" in these ramp segments

Two questions for the TTS chumps:

1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

2) On some of the ramps I've seen, the ramp name is "Exit 70A-B:...", but it is read as "exit 70ayybee" without any break between the ayy and bee. If I add a space before and after the dash Waze says "Exit 70ayy to bee. What do you guys recommend in such a situation?

Spil wrote:Sorry, no input on the first one, but I'll take up this one for you:

Wajo357 wrote:2) On some of the ramps I've seen, the ramp name is "Exit 70A-B:...", but it is read as "exit 70ayybee" without any break between the ayy and bee. If I add a space before and after the dash Waze says "Exit 70ayy to bee. What do you guys recommend in such a situation?

In most such situations, the "Exit 70A-B" part of the ramp should be left unnamed, allowing TTS to use the appropriate "Exit 70A" or "Exit 70B" ramp name from the upcoming offramp. There may be some instances where the "Exit 70A-B" might be needed, though -- can you provide a Permalink to the interchange in question here?

Permalink here: https://www.waze.com/editor/?zoom=6&lat ... s=57801554

ncc1701v wrote:If "Exit 70A-B" is what the sign says, as a driver my personal preference would be to have Waze say the same thing, as opposed to leaving the ramp unnamed. That is, first I get told to keep right for 70A-B, then left for 70A to Minnewaska.

Sent from my Nexus 10 using Tapatalk HD

The question I have is should we write:

a) Exit 70A-B > Which is read as "Exit 70ayybee"
b) Exit 70A - B > Which is read as "Exit 70ayy to bee"