Thanks GizmoGuy411. I was using the wiki link immediately above the google spreadsheet link. The current list actually shows entries for both PTS (Points) and PT (Point), but neither work as they show as n/a.

Looking forward to having these resolved as "Divers" is fairly common in my driving area and sounds pretty dumb when the signposts show Diversion.

Kayos

Is it possible to apply the same logic as St. for Saint vs St for Street? This would make it Divers for Divers and Divers. for Diversion... doctorkb may also want to have some input on what to do here.

Kayos

I found a couple of TTS errors:

"to Hwy 91A N / Annacis Island" is translated as "to highway nighty one eh en" pause "annacis island"
"to Hwy 13 / 264 St / Aldergrove" is tanslated as "to highway thirteen thousand two hundred sixty four street" followed by the pause for the second slash an "aldergrove"

These are both segments starting with "to" Could this be what is causing the issue?

Kayos

For the last few months (I don't know exactly how long as I don't take this route often) this exit has been voiced as "to highway ninety one eh en, annacis island". Segment name is "to Hwy 91A N / Annacis Island"

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

and this one as "exit eleven, highway ninety one eh en, annacis island, new westminster". Segment name is "Exit 11: Hwy 91A N / Annacis Island / New Westminster"

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

Do these segments need to be changed to have the N voiced as "north"?

Thanks,
Kayos

taco909 wrote:St Augustine is coming through as "Street Augustine"

The syntax to fix this is the segment name should be "St. Augustine" The period is used to distinguish between Saint and Street.

Kayos

PesachZ wrote:

codgerd wrote:Brg is pronounced correctly as 'bridge' when in the course of normal instructions, but is pronounced on my client as B-R-G when it occurs in the little summary spoken prior to starting a route. e.g. "Let's get started! Let's take Burrard B-R-G". Then later, "turn left on Burrard Bridge".

Brg is not a recommended abbreviation, you should be using Br. Unless you can show the BGS actually says Brg.

Sent from Android using Tapatalk

I also experienced this and reported it to the beta team, but unfortunately they were unable to replicate the issue. It seemed to only happen with the "Lets take..." and "Continue straight..." strings and would occur with both B R G and H W Y abbreviations. Doing a complete uninstall and a fresh install seemed to fix the problem for me, but I wanted to do the uninstall to clean up some other issues as well.

With respect to the Brg abbreviation, we use the Canada Post addressing guidelines for abbreviations and some are not common between Canada and the US. The Brg abbreviation is in the localization file and is supported in Canada. Another somewhat unexpected abbreviation is Pky for Parkway, where most signage and typical abbreviation is Pkwy. Both are in the localization file.

Kayos

Good point! I didn't think of doing that myself...

Kayos

Tlwy says something like "Tl-whY"

(Line 622)

GizmoGuy411 wrote:

LittlestLou wrote: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)

I was doing some testing for some updates I was planning on for the WI wiki page. I named my street CR-CT and Waze said to turn on County Road Connecticut.

Totally caught me off guard.