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

[ img ] This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderator: MapSir

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby sketch » Sat Mar 03, 2012 7:26 pm

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
Waze Global Champs
Waze Global Champs
 
Posts: 6006
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1477 times
Been thanked: 2022 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby GizmoGuy411 » Sat Mar 03, 2012 9:24 am

R4CLucky14 wrote:With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?


Yes we have asked for an exception field, and Waze has said here in the forums that a solution is coming. (can't find the post at the moment). It may also come along with the ability to test the results immediately.

However the issues with TTS abbreviations, and TTS for full words are not exactly the same.

There are multiple layers to how the TTS engine works. Waze uses a product from Nuance that is sold customized for mobile use. Waze also has the ability to further customize what the TTS can say.

When they provide us with an exception field, was can over-ride the delivered TTS and have it say what we want for all the special cases we encounter, such as alternate local pronunciations, non English language words, and other similar infrequent cases.

Abbreviations however are used very frequently, and need to be available without always needing to use an exception field.

The abbreviation list we are building here is intended to test what Waze currently recognizes and to test future possibilities. Everything that we test is NOT necessarily what we would like Waze to actually use for TTS.

As others have mentioned above. we hope to get Waze to change the TTS for those abbreviations that we feel are most likely to be encountered in North American that are commonly used on signs.

The exception field can then be primarily for full words and hopefully only needed for abbreviations in rare exceptions.

So the combination of a Waze customized set of abbreviations, along with our ability to further customize anything in an exception field should provide the best solution.

While this will be important for North America, the exception field will be even more important for the rest of the world. The ROTW may well need their own custom abbreviation list too. And that is best left for discussion in another forum!
Last edited by GizmoGuy411 on Sun Mar 11, 2012 9:33 pm, edited 2 times in total.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1412
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 434 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby R4CLucky14 » Fri Mar 02, 2012 4:19 am

banished wrote:
AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."


I am uncertain if spelling or standard abbreviations is taught at Street Sign School. :lol:

Normally, Trail would be Trl, Terrace would be Ter

https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).


With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to
implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?
R4CLucky14
 
Posts: 356
Joined: Fri Nov 25, 2011 10:21 pm
Has thanked: 0 time
Been thanked: 2 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby banished » Fri Mar 02, 2012 4:15 am

AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."


I am uncertain if spelling or standard abbreviations is taught at Street Sign School. :lol:

Normally, Trail would be Trl, Terrace would be Ter

https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).
banished
Waze Global Champs
Waze Global Champs
 
Posts: 783
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 229 times
Been thanked: 170 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby AlanOfTheBerg » Thu Mar 01, 2012 6:37 pm

I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby jenncard » Thu Mar 01, 2012 6:07 pm

I just encountered a "Ste" (someone had intended as state) which I am pretty sure was pronounced as "suite"
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 11 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby bgodette » Mon Feb 27, 2012 9:04 pm

jasonh300 wrote:Not sure if anyone else confirmed this, but last night, I found that St. is pronounced as "Saint". This was in "Bay St. Louis". I don't know whether it's the positioning or the period that makes it work. It pronounces Louis "Lou-ee", but that's another issue.

Sketch pointed out yesterday in another thread that "Iberville" is pronounced "d'Iberville", which is surprising. We pronounce the street "EYE-ber-vil" whereas d'Iberville, like the town in Mississippi, is usually pronounced "dee-IHB-er-vil".

Didn't I already say Wanda is a French-Canadian Mexican?
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3420
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 110 times
Been thanked: 511 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby jasonh300 » Mon Feb 27, 2012 5:40 pm

Not sure if anyone else confirmed this, but last night, I found that St. is pronounced as "Saint". This was in "Bay St. Louis". I don't know whether it's the positioning or the period that makes it work. It pronounces Louis "Lou-ee", but that's another issue.

Sketch pointed out yesterday in another thread that "Iberville" is pronounced "d'Iberville", which is surprising. We pronounce the street "EYE-ber-vil" whereas d'Iberville, like the town in Mississippi, is usually pronounced "dee-IHB-er-vil".
jasonh300
 
Posts: 7568
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 408 times
Been thanked: 984 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby harling » Mon Feb 27, 2012 5:14 pm

AlanOfTheBerg wrote:
CBenson wrote:I just discovered that "Pr." is on a few BGSs around here as an abrieviation for "Prince." The TTS says "pea are."

Another one to just spell out? Though I'm not sure what "pr" would otherwise conflict with.

Puerto Rico? Pier? Pair?

I could see having TTS pronounce 'Pr.' as "Prince" in TTS... but at only six letters, and the possible interference with highway names all over Puerto Rico :) , it might make more sense to just spell out "Prince" where it is needed.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby AlanOfTheBerg » Mon Feb 27, 2012 4:56 pm

CBenson wrote:I just discovered that "Pr." is on a few BGSs around here as an abrieviation for "Prince." The TTS says "pea are."

Another one to just spell out? Though I'm not sure what "pr" would otherwise conflict with.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users