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

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

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 10:09 pm

sketch wrote:Is that only for MT in caps though? I'm rather certain "Exit 2xx: N River Rd / Mt Clemens" is pronounced properly, as of late last year.

The list is case sensitive so I don't think "Mt" had ever been officially tested.
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 3:54 pm

Further testing has revealed a couple issues, possibly with exception programming, possibly with the base Nuance system in how it implements grep:
  • "St" at the beginning of a segment name is pronounced "saint"
  • "N" which follows another programmed abbreviation exception is pronounced "enn" (E, W, S are all OK after abbreviations)
  • "BUS" fails to expand to "business" if it is at the segment end.

Notes:
I confirmed my supposition based on the rule structure that in order to pronounce the letter name rather than the cardinal, you just need a non-spoken non-whitespace character in front of the letter. So, in our current naming standard, the closing single quote isn't required by the rules, but I think we keep it in place because it looks more correct:
  • S E St = "south east street"
  • S 'E' St = "south ee street"
  • S 'E St = "south ee street"

The following full test results from today (still have a couple more to do during lunch):
SH-219 S = "state highway two nineteen south"
SH-411 N = "state highway four eleven north"
S 'E St = "south ee street"
SH-8 BUS N = "state highway 8 business enn"
SH-8 BUS S = "state highway 8 business south"
CR-699 BUS N = "county road six ninety nine business enn"
I-5 BUS N = "eye five business enn"
St A St. = "saint a saint"
Hello Natl Thwy S = "hello national throughway south"
'W St. 'N N = "double you saint enn enn"
I-82 BUS E = "eye eighty two business east"
Jr. B St. Dr. = "junior bee saint doctor"
CR-12 BUS S = "county road twelve business south"
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 6:17 pm

sketch wrote:
AlanOfTheBerg wrote:"St" at the beginning of a segment name is pronounced "saint"

I don't believe this to be a problem. As long as "St" is still pronounced "Street" at the end, before a slash, and before another abbreviation, it's fine. There are so many instances of "St", no period, meaning "saint" on the map that it would be a mistake to change the way "St" behaves without addressing them all.

Besides, wasn't the problem that "St"/"St." was being pronounced "Street" in the wrong places, not the other way around?

It may not be a problem generally but 1) we want 100% positional independence, and 2) I bet there is one street named street somewhere. :)
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 8:18 pm

sketch wrote:
AlanOfTheBerg wrote:It may not be a problem generally but 1) we want 100% positional independence, and 2) I bet there is one street named street somewhere. :)

Ehhh... do we really though, in this case? Maybe, but it's going to be a mess. And if there's a street named Street, "Street" wouldn't be abbreviated anyway.

Perhaps not. I was going by our guidelines which have been "abbreviations do not vary based on where they are." We can start making a list of exceptions to this rule, or can stick to it.
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Wed Apr 16, 2014 3:26 pm

sketch wrote:I don't doubt that there is a legitimate interest in divorcing TTS expansion from position. And I'm not saying "St" should never be location-independent. But the map isn't ready.

If "St." is now "saint" we can get going on that sort of edit-a-thon. But I think some time should be allowed to pass before the change to the TTS is made. There should be some sort of balance here.

I say start renaming everything starting with "St" which should be 'saint' now to avoid problems. As it is now, 'saint' is pronounced both at the beginning and sometimes in the middle of a segment name, eg. "Mt St Helens"
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Wed Apr 16, 2014 3:29 pm

Latest testing results, failed items in red.

Mt. St. Helens Rd E = "mount saint helens road east"
Mt St Helens Dr = "mount saint helens drive"
Mt. St Helens Rd N = "mount saint helens road north"
Marx Ste. Marie = "marks sweet maree"


I have also noted that "Mt" and "Mt." both say "mount" but "Mt." sounds ... strange. It takes longer to say "mount" and there's a longer space after the word. "Mt" should be the standard.
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby AlanOfTheBerg » Thu Apr 17, 2014 7:15 pm

sketch wrote:"SR" and "SH" don't depend on whether there's a hyphen, do they? Relying on the hyphen is too opaque imo.

They do. Hyphens are important, if only at least to ensure proper abbreviation usage.

As of this moment, we need to immediately remove the custom abbreviation for "FM" and "NE" as they are both being incorrectly pronounced as state/territory name. Are there any other problematic state abbreviations which conflict with other existing abbreviations that we need to work on in a more detailed manner?

And, yeah, IMO, I don't know why we would ever really need any state name in segment names, but I'm sure it exists somewhere.
Wiki Resources: Map Editing Manual | Oregon Project/To-Do List
Oregon-based US Country Manager | iPhone5 - VZ - iOS 7.0.6 | Waze v3.7.9.992
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 19467
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 647 times
Been thanked: 2247 times

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

Postby Alice2 » Sat Sep 08, 2012 12:54 am

I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?
Alice2
 
Posts: 28
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby Alice2 » Thu Nov 15, 2012 4:14 am

So, what do we do now? Today I heard Samantha say (twice) "keep left at to I 10 west" and it really was unclear if she meant to, two, or maybe too. It gave the impression there were two I 10 west roads. Sounded strange. Maybe she wasn't feeling well!!
Alice2
 
Posts: 28
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby Alice2 » Thu Nov 15, 2012 11:57 am

https://www.waze.com/editor/?lon=-98.59 ... s=48129505 The 2 I-10 west TTS directions came to direct me to the highlighted segment. I have not yet tested any other entrance segments on this stretch of road.
Alice2
 
Posts: 28
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 0 time
Been thanked: 0 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users

cron