Page 11 of 159

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

Posted: Tue Jan 15, 2013 9:50 pm
by Alice2
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.

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

Posted: Wed Oct 19, 2016 9:26 pm
by Alpha_VA
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.

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

Posted: Mon Apr 02, 2012 9:57 pm
by AndyPoms
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

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

Posted: Mon Apr 02, 2012 10:43 pm
by AndyPoms
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...

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

Posted: Mon Jun 18, 2012 12:03 pm
by AndyPoms
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.

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

Posted: Mon Aug 13, 2012 5:49 pm
by AndyPoms
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...

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

Posted: Tue Sep 04, 2012 3:43 pm
by AndyPoms
"Int'l" for "International" added to WME on 8/28/2012... Made map update on 9/4/2012... TTS reads it the same as "Intl" saying "untell"...

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

Posted: Thu Sep 06, 2012 3:34 pm
by AndyPoms
I can report that "St Mary St" in Hamden, CT says "Saint Mary Street" in TTS... I drove it twice to confirm... (Permalink)

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

Posted: Thu Sep 06, 2012 4:59 pm
by AndyPoms
GizmoGuy411 wrote:Ill add it to the list to show obedience that actually works correctly. Is that the exact capitalization and punctuation?
That's why I permalinked it, so others could look... It is "St Mary St" without the quotes... 2 of the 3 segements were last updated on Mon Jun 25 2012 & the 3rd (middle) was last touched even earlier (Thu Mar 08 2012)...

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

Posted: Mon Sep 10, 2012 11:35 pm
by AndyPoms
jondrush wrote:How do I keep Penn St from being announces as Pennsylvania street?
Is it "Penn Street" or "Penn State" you are trying to do?

Are you sure "Penn" comes out as "Pennsylvania"? That style abbreviation isn't on the TTS test list for state names at all... I guess I'll have to add "Conn" to see if it comes out "Connecticut", although I'd think it either comes out "Conn" or "Connector"...