Page 1 of 159

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

PostPosted: Sun May 22, 2016 2:10 pm
by abc1357
Newhall Street in Santa Clara, California. https://www.waze.com/editor/?env=usa&lo ... lter=false

Currently being pronounced as "New-hal" - rhymes with "pal"
Correct pronunciation is "New-hall" - rhymes with "ball"

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

PostPosted: Wed Aug 03, 2016 6:35 am
by abc1357
Machin Ave in Novato, CA, is pronounced as "Makin".

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

PostPosted: Tue Jan 17, 2017 2:20 am
by abc1357
Jane voice. UR reports that "Gateway" is wrongly pronounced as "Gate-wah".

Permalink

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

PostPosted: Wed Mar 01, 2017 3:25 pm
by abc1357
There is a restaurant named "Va de Vi". Unfortunately, Waze pronounces it as "Virginia de Vi". What's the best way of fixing? Could I put it in as "Va. de Vi" as the primary to aid pronunciation and put in "Va de Vi" as alternate name to enable search?

Unfortunately, unlike road segments, there is no "voice" button next to it to test. So I have to wait for a tile update AND drive over there to test....

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

PostPosted: Thu Mar 02, 2017 1:09 am
by abc1357
Kartografer wrote:Why not just test the name on a nearby road segment, and then if it sounds right put that name on the place?


Duh! Should have thought of that. Interesting - the English voice for "Va de Vi" pronounces it as "V A de Vee". As in the Letter V, Letter A, sound "duh", sound "vee". I tried "Va. de Vi" with a period and it's voiced as "V A de Vee" also. I tried "Vaa de Vi" and it's voiced as "V A A de Vee"

sketch wrote:No, this should be handled by the TTS team. "Va" with no period and a lowercase "a" should be pronounced as a word. (And "Va."—an accepted, if old-fashioned, abbreviation—should be pronounced as "Virginia")


Since the restaurant was about 10 min out of my way, I decided to drive over and hear exactly what was announced. Using English (US) (Jane) on Android Release 4.19.0.3, the app definitely voiced "Virginia duh vee".

So we now have a case where not only is the pronunciation on the app incorrect, but the pronunciation by WME is different from what is voiced by Jane.

Given that I can't get a pronunciation of "Va" (rhymes with "far"), I'll leave this up to the TTS team.

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

PostPosted: Wed Jan 18, 2012 8:04 pm
by AlanOfTheBerg
Was this also to end up being an official list to help them differentiate things like Penn vs. Pennsylvania, St vs. St. (saint) and Dr vs Dr. (doctor)? I think we need to add those too, unless I'm missing the purpose of the full abbreviation list.

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

PostPosted: Fri Jan 20, 2012 6:20 pm
by AlanOfTheBerg
gettingthere wrote:May need to use a single or double quote around the street name so that Waze understands that it's not an abbreviation that needs to be expanded.

Do quotes still result in being backslash-escaped to \' and \" ? I haven't tried recently.

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

PostPosted: Sun Jan 22, 2012 2:19 pm
by AlanOfTheBerg
I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect. Not sure how they work at the end or in the middle of the name.

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

PostPosted: Mon Jan 23, 2012 1:32 am
by AlanOfTheBerg
banished wrote:
AlanOfTheBerg wrote:I know that NW, SW, NE, SE work fine as a prefix and are fully pronounced as you'd expect.


Yes, I meant to include those. But other than a very small set of abbreviations, such as those, it makes sense to put a period after words not contained in that set, e.g., "Dr." for doctor and "Dr" for drive; "Wash." for Washington, and "wash" (no period) for wash, as in Wash Ave.

I feel, as mapcat noted, that we should not be going hog wild on things like Wash. vs Wash and Geo vs. George. The smaller set of abbreviations, the better. If it's Wash, it's always Wash, otherwise spell out Washington if that's what it is.

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

PostPosted: Mon Feb 27, 2012 4:56 pm
by AlanOfTheBerg
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.