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 AlanOfTheBerg » Wed May 29, 2013 8:29 pm

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?
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23612
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4797 times

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

Postby dctdye » Wed May 29, 2013 8:24 pm

AlanOfTheBerg wrote:
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.

Figured it was something simple like that. That's hopefully fixed now. Thanks :D
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 8:15 pm

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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23612
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4797 times

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

Postby dctdye » Wed May 29, 2013 8:14 pm

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
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 7:37 pm

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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23612
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4797 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 6:57 pm

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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23612
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4797 times

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

Postby jondrush » Wed May 29, 2013 6:40 pm

Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2648
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 194 times
Been thanked: 516 times

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

Postby AlanOfTheBerg » Mon May 27, 2013 8:33 pm

Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan.

https://twitter.com/sorcererdale/status ... 8604571648

It's the first I've heard of this.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23612
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4797 times

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

Postby PhantomSoul » Mon May 20, 2013 6:30 pm

Like I said, I think it's confusing, and a dedicated text control marked with a phonetic pronunciation label is the best way to go, assuming such input is needed.
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1681
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 304 times
Been thanked: 501 times

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

Postby berestovskyy » Mon May 20, 2013 6:28 pm

PhantomSoul wrote:But in the long run, unless Waze creates some kind of administrator certification program to teach people these backdoor hacks [...]

"Certification program" for "backdoor hacks"? Oh, come on! :lol: Every single system or game has settings. They are confusing sometimes, that is why UI developers hide them under the "Settings" ;)

Yes, I really think the feature we use for one of a 100 road segments really deserve "to bypass the UI development process" like you said. And it's not only about immediate returns, but also about cluttering WME interface.

Examples?
  1. "Toll roads". There are many countries with no toll roads at all. But the option is there, easily accessible.
  2. "Lock", now with a dropdown box. How often do we use this feature? New editors especially.
  3. On the other hand, every single segment has an address. But we have to click "Edit" next to "Unnamed segment" and then "Apply".
So no, I don't like the way "WME system appears to be headed" :(
berestovskyy
 
Posts: 839
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 713 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users