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

[GizmoGuy411]

I've edited the BIG TTS List to correct an error regarding the sources of abbreviations for Bridge. The chart below also shows the corrected abbreviation sources and current usages.

Please note that nothing has ever been submitted to Waze for change for "Branch" or "Bridge". The current Waze abbreviation usage shown below is how it has always been. That implies that Nuance matched the USPS over MUTCD for their abbreviation choices for their mobile customized version of their Vocalizer TTS product. This does not mean that we can't fix it for Waze.

I agree that we should probably follow actual signs, along with MUTCD before USPS and Canada Post as much as is practical when there are conflicts.

I proposed the change below if we can confirm that signs use "Br" for "Bridge" and that there is more use of "Bridge" than "Branch".

Abbreviation Source - Word >	Branch	Bridge
MUTCD	n/a	Br
USPS Standard	Br	Brg
USPS Common	Brnch	Br
Canada Post	n/a	n/a
Waze Current	Br Brnch	Brg
Waze Proposed Change	remove Br	add Br

[GizmoGuy411]

While perusing the "big list" I came upon a misspelling. It should be "crescent" with a c after the s. This is so minor it hardly seems worth mentioning, but it is a reference...

Done.
Thanks. Corrections however small appreciated.

[GizmoGuy411]

Try "CR-C T" it should give you the results you want.

I was just doing some testing, thanks though. I only mentioned it since it didn't look like it had been confirmed in the list.

Try "CR-C.T." to force it tp pronounce the letters as we have done that for other letters that we would like pronounced.

[GizmoGuy411]

Just a quick note to update for the big list I had to rename some ramps, "IS" and "Is" say is, instead of island.

Could you provide a PL example? There could be an issue related to other text in the Ramp name.

[GizmoGuy411]

Please check the Big List before making suggestions to add an abbreviation.

As an example, "Rev." already says "Reverend" and I just re-tested it to confirm it.

Please report the Permalink for any specific instances where the TTS results are different that what was expected.

[GizmoGuy411]

After over two years, the Big List, finally now has every entry tested.

The list may not yet include all of the latest suggestions we are preparing to submit to Waze.

[GizmoGuy411]

Cord St near Middle River, MD is pronounced as "County Road" in TTS.

Reporter on July 31, 2014
The text to voice says "county road street"

I'm aware that "Co" (and "CR") is pronounced "county", and "rd" as "road", however I didn't know it would parce groups of letters in the middle of a word (not separated by a space).

Thank you. Good observation.

I think you actually discovered a previous existing abbreviation that we had not yet discovered!

Currently the following are documented in the "Big List" to exist or we have had Waze add them:

"Co" says "co" as in the word "cooperate"
"Cor" says "Corner"
"CR" says "County Road"
and now you have found that
"Cord" also says "County Road"

This will be added to the "Big List" and we will also add it the submission list to Waze for removal as an abbreviation.

[GizmoGuy411]

Reading GizmoGuy411's post, it indicates everything has been tested. The list on the first post in this thread has not been updated, hence the request to see the current list.

Thanks,
Kayos

I've checked the link in the opening post, and it links correctly for me. Is there any chance that you are viewing a cached copy and not the latest version.

Since I do not intend on updating it within the day or so, the version date/time you should see is,
"Updated: 2014-08-18T04:00Z"

This Big List version shows both "Diversion" and "Points" as being tested. Neither have a functioning TTS abbreviation at the moment. I will bring up both as suggestions for additions.

Hope that helps.

[GizmoGuy411]

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

These errors have been found in several Ramp names where a combination of abbreviations that work elsewhere, do not with in ramp names where the slash mark appears.

Would you mind sending the Permalink for these examples to me directly and I will add it to our list of such examples that we will present to Waze to figure out?

[GizmoGuy411]

It was fixed for instances where they existed as the sole abbreviation.

The combinations of abbreviations did not work.

All bets are off at the moment to what STILL works.

We will just have to submit the examples we have and see if they can figure it out.

So if you have more examples, add them here I guess and we can compile them and send them next week then that team is more accessible.