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 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: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
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: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
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: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
Been thanked: 0 time

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

Postby Alice2 » Thu Nov 15, 2012 9:52 pm

AndyPoms wrote:
jasonh300 wrote:It's most likely because the word "To" on the ramp is capitalized, which doesn't conform to the standard.

I'm going to send a PM to the editor in question and make sure this is just a typo and not widespread.
Remember there was a period of time when auto-capitalization just started where the word "to" was not exempt & it was automatically changed to "To", so there may be more ramps out there like this...

I just drove this route again today, and the TTS was correct this time! https://www.waze.com/editor/?lon=-98.59 ... s=48129505 The "to" is also now lower case in the editor. However I see that there are several (could be many) instances of upper case "To" all around. My experience must have been a one-time thing if no one else has come across the "stay left on to I XX".
Alice2
 
Posts: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
Been thanked: 0 time

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

Postby Alice2 » Tue Jan 15, 2013 9:50 pm

Wonders will never cease!! After weeks of hearing TTS announce U T South A, I finally heard all the letters pronounced as letters - U T S A. It was written as U T s A with no single quotes around the lower case s. Did I miss something about not requiring single quotes to get the letter pronounced as a letter instead of a direction? It still seemed peculiar because it appeared as all upper case letters on the client.
Alice2
 
Posts: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
Been thanked: 0 time

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

Postby Alpha_VA » Wed Oct 19, 2016 9:26 pm

Would it be possible to add

Blvd = Boulevard

to the custom abbreviations list?

It's the only one I noticed with a German TTS voice which is spelled char by char and not translated. It is also missing in the list in the wiki.
Alpha_VA
 
Posts: 133
Joined: Sun Oct 09, 2016 8:48 pm
Has thanked: 50 times
Been thanked: 10 times

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

Postby AndyPoms » Mon Apr 02, 2012 9:57 pm

I have several exits here in CT that say "N. Y. City"... I was listening closely today and I got "North Why City" through the TTS... Without me testing 75 variations, does anyone know a way to keep some form of "N. Y." (NY, N.Y., etc) for the display and get it to read "New York" in the TTS?

Thanks for your help,
Andrew
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7215
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1327 times

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

Postby AndyPoms » Mon Apr 02, 2012 10:43 pm

GizmoGuy411 wrote:
AndyPoms wrote:I have several exits here in CT that say "N. Y. City"... I was listening closely today and I got "North Why City" through the TTS... Without me testing 75 variations, does anyone know a way to keep some form of "N. Y." (NY, N.Y., etc) for the display and get it to read "New York" in the TTS?

Thanks for your help,
Andrew


Look at the abbreviation list linked in the lead post of this thread. I think it has been updated to include the abbreviation for New York that works.

Sent from my Galaxy Nexus using Tapatalk


For New York the doc says:

New York NY CU 2012-02-19 n/a. Says the letters 2012-03-22 GizmoGuy411 A
New York Ny CU 2012-02-19 New York 2012-03-22 GizmoGuy411 R

If I read that correctly, "NY" says "enn why" (and it should be Added) and "Ny" says "New York" but the recommendation is to Remove it?

The other thing I noticed while looking at the State List (and if I'm reading this wrong, please let me know) is that you want to add "Ct" to be "Connecticut" instead of "court" which is currently does. Being from Connecticut, we have many roads named "Something Court" and the USPS abbreviation is "Ct" for "Court" (but it's also missing from the "C" section of the list...
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7215
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1327 times

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

Postby AndyPoms » Mon Jun 18, 2012 12:03 pm

Webs101 wrote:Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Isn't that because it's French? (i.e. Nord, Sud, Est, Ouest = North, South, East, West)

Wouldn't it just be easier to use N, S, E, W as the cardinal (compass) directions in Waze? And then you can change the language in the app to either Engilsh (and get North, South, East, West) or French (and get Nord, Sud, Est, Ouest) - I think, I'm not about to change my Waze to French as I may never get it back to English.
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7215
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1327 times

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

Postby AndyPoms » Mon Aug 13, 2012 5:49 pm

AlanOfTheBerg wrote:
invented wrote:I think it's pronouncing "(E)" as "Eee" again. -.-

Really? That'd be nice. I've been changing many to 'e' (and 'n', 'w' or 's') as that was the only option which worked. Where did you hear/see this?


I have a street in Hartford named "Elliott St E" (just like the road sign says) (Permalink)that is pronounced "eee", but the directions to get on "I-84 E" works properly and says "East" (various locations).

Some days I report to work on "Elliott St E", so I hear it all the time... It's not a major road, so I don't consider this a high priority, but have thought of changing it to "E Elliott St" and seeing what happens...
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7215
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1327 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users