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

[sbelekevich]

Tlwy says something like "Tl-whY"

(Line 622)

[sbelekevich]

Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...

Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".

+1

Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)

[simonhowes]

Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!

I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.

We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.

[sketch]

I have a "Robert E Lee Blvd" which TTS would prononuce as "Robert East Lee Boulevard", so I added a period after the E -- "Robert E. Lee Blvd" -- and now it pronounces it as "Robert East. Lee Boulevard"; the same, but with a pause in the middle.

[sketch]

Interesting. So the period also converts to a pause? Perhaps this might be an idea for the other post re: ramp naming.... "Exit 123: I-70 W. Grand Junction"

A possibility, but I dislike this almost as much as I dislike commas, from a logical standpoint

[sketch]

Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.

[sketch]

WeeZer14 just found an issue in New York City with signs that say "NYC". Waze does not pronounce it properly at all.

I'm adding them all the list, however which of the following should we request:
a) NYC = "New York City"
b) NYC = "NYC" (the letters)
c) N.Y.C. = "New York City"
d) N.Y.C. = "NYC" (the letters)
e) other

I'm thinking b and c.

(As a side note, Excel says "New York City" for "NYC" and says the letters "N", "Y", "C" for "N.Y.C")

"NYC" should be pronounced "N Y C", as should "N.Y.C." If a sign says "New York City", we should put "New York City" in the name, not "N.Y.C."

[sketch]

I agree. I also stated "N.Y.C." should be read like that, though. No need for it to unabbreviate it at all.

[sketch]

For the record:

"Intl" is pronounced like "Entull". It would be nice to have it pronounced as "International".

The example that led me here is doubly problematic, in fact: an exit is signed as "N.O. Intl Airport". If I label it "N.O. Intl", it'll say "North Oh Entull", but if I say "NO" it'll just be "No Entull". I'm going to label this segment "New Orleans International" for now, but it would be nice to have it somehow workable.

[sketch]

Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.

CBenson suggested that some time ago, however it has not been tested yet.

Don't you or jasonh300 ever get a chance to hear it?

At the rate that our map tiles are getting updated, I could drive down to Baton Rouge and learn the results faster!

Haha, probably! I don't get to Baton Rouge much, and I don't think Jason does either, to be honest. I may or may not be heading that way tomorrow, so I'll check it if I have a minute.