Page 5 of 159

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

Posted: Thu Jan 31, 2013 12:27 am
by AlanOfTheBerg
orbitc wrote:I agree with Alan. Few of us tested these with few different combination. The Best option, IMO, should be either with single quotes or double quotes.
I like single. Because they are thinner.

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

Posted: Mon May 27, 2013 8:33 pm
by AlanOfTheBerg
Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan.



It's the first I've heard of this.

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

Posted: Wed May 29, 2013 6:57 pm
by AlanOfTheBerg
jondrush wrote:Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?
I think those should just be spelled out.

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

Posted: Wed May 29, 2013 7:37 pm
by AlanOfTheBerg
AlanOfTheBerg wrote:Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan..
Looks like this road is using the abbreviation of "CR" and not "Co" per the original tweet. Road is "CR-480": https://www.waze.com/editor/?zoom=4&lat ... s=19400448 south of Harvey, MI.

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

Posted: Wed May 29, 2013 8:15 pm
by AlanOfTheBerg
dctdye wrote:I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:

https://www.waze.com/editor/?zoom=6&lat ... nts=956781
You need to have spaces on both sides of the slash characters, per the naming guidelines.

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

Posted: Wed May 29, 2013 8:29 pm
by AlanOfTheBerg
dctdye wrote:Figured it was something simple like that. That's hopefully fixed now. Thanks :D
I noted others in the area, too. You'll probably be going around fixing a bunch now?

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

Posted: Tue Jul 23, 2013 6:44 pm
by AlanOfTheBerg
Why not just use the global standard of E for east?

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

Posted: Mon Nov 04, 2013 11:04 pm
by AlanOfTheBerg
qwaletee wrote:It would be interesting to know the distribution of signs using Br for Bridge versus using Br for Branch, so that we could know which to assign causing the fewest issues.
As noted elsewhere, when in doubt, spell in out.

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

Posted: Fri Dec 13, 2013 6:30 pm
by AlanOfTheBerg
qwaletee wrote:Update on 9W. Text to speech says West. Ouch. I can't see manually updating every segment to use 9'w' instead of 9w. Also, I believe the quotes do show up, so 9'w' would be a problem. Maybe 'US-9w'?
If it is capitalized, it shouldn't do this. I know that I have "99W" and "99E" here in Oregon and they are always pronounced as double-you and eee respectively. However, these are state routes, so perhaps Waze doesn't have the same rule for the US routes.

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

Posted: Mon Dec 16, 2013 6:09 pm
by AlanOfTheBerg
qwaletee wrote:I have observed that this could be happening when my phone is bogged down with other tasks. Perhaps the thread that expands abbreviations has a low priority, and if it doesn't run in time, Waze just reads it as-is.
I don't see how this is possible. TTS audio is created at the server and the mp3 file is downloaded to the app.