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 xanderb » Mon Jul 03, 2017 7:33 pm

ttninja55 wrote:Coming out of Ft. Knox KY today, Jane pronounced Bullion Blvd "bully on Blvd." where would I submit this issue?

PM me the segment and turn direction that gave you that pronunciation please.
xanderb
Local Champ Mentor
Local Champ Mentor
 
Posts: 645
Joined: Sat Jul 10, 2010 6:12 pm
Location: Louisville, KY
Has thanked: 384 times
Been thanked: 311 times

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

Postby ttninja55 » Sun Jul 02, 2017 1:52 am

Coming out of Ft. Knox KY today, Jane pronounced Bullion Blvd "bully on Blvd." where would I submit this issue?
ttninja55
State Manager
State Manager
 
Posts: 42
Joined: Tue Mar 17, 2015 9:05 pm
Location: Kentucky
Has thanked: 31 times
Been thanked: 13 times

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

Postby thanks0bama » Sat Jul 01, 2017 4:35 pm

Lincolnia Road in Alexandria Virginia.
(https://www.waze.com/editor/?env=usa&lo ... 559&zoom=3)

Correct pronunciation: Link - own - E - uh
thanks0bama
 
Posts: 1
Joined: Thu May 04, 2017 9:49 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby subs5 » Mon Jun 26, 2017 1:07 pm

Mispronunciation of Sycolin.

Segment location: Leesburg, VA

correct pronunciation: Sick - oh - Lynn,
subs5
Country Manager
Country Manager
 
Posts: 946
Joined: Sun Aug 17, 2014 7:05 pm
Location: Virginia, USA
Has thanked: 272 times
Been thanked: 392 times

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

Postby TauCetian » Mon May 29, 2017 2:11 am

Road mispronunciation: Permalink

User reported, and I confirmed via BOTG, that Jane mispronounces the name of this road as "FINE-durn"; it should be "FIN-durn".
TauCetian
 
Posts: 86
Joined: Tue Jul 14, 2015 3:25 am
Location: Piscataway, NJ
Has thanked: 0 time
Been thanked: 3 times

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

Postby xanderb » Sat May 27, 2017 3:19 pm

DwarfLord wrote:Was there a decision that FS-xxx is not a supported road-category prefix after all? Or is it semi-supported, in the sense that it's considered OK to use, but not to voice?


FS-xxx was submitted a while ago and we are just waiting for it to be processed as a voiced replacement. You are okay to use it.
xanderb
Local Champ Mentor
Local Champ Mentor
 
Posts: 645
Joined: Sat Jul 10, 2010 6:12 pm
Location: Louisville, KY
Has thanked: 384 times
Been thanked: 311 times

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

Postby DwarfLord » Sat May 27, 2017 2:38 pm

Wayyyyy earlier in this thread there seemed to be resolution that the FS-xxx road-category prefix should pronounce as "Forest Service", similar to US-xxx, I-xxx, SR-xxx, CR-xxx, etc. The US even has a wiki article on Forest Service Roads (note, MVUM = Motor Vehicle Use Map published by the US Forest Service):

Current USA wiki article on Forest Service Roads wrote:
  • USFS roads on the MVUMs that are not named or with an alternative naming convention should be named "FS-XXXX" where XXXX is the USFS road name on the MVUM. For example, main FS-333 road might have stub roads FS-333A through FS-333E. (NOTE: THIS NAMING STANDARD IS CURRENTLY UNDER DISCUSSION/REVIEW 15 MAR 2015)
  • Fire Service Roads, roads designated for Forest Fire services, shall also use the "FS-XXX" designation

However, testing today with the Jane voice indicates FS-xxx is pronounced "eff ess".

Was there a decision that FS-xxx is not a supported road-category prefix after all? Or is it semi-supported, in the sense that it's considered OK to use, but not to voice?
DwarfLord
Wiki Master
Wiki Master
 
Posts: 2138
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 897 times
Been thanked: 1173 times

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

Postby fjsawicki » Mon May 08, 2017 1:36 pm

Additional URs reporting that Causeway Blvd is pronounced Causewell Boulevard with the Jane voice

Thanks
fjsawicki
State Manager
State Manager
 
Posts: 307
Joined: Thu Dec 31, 2015 5:28 am
Location: Tampa Bay
Has thanked: 167 times
Been thanked: 37 times

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

Postby sketch » Fri Apr 28, 2017 12:47 pm

AndyPoms wrote:Just got a UR that says "Opas" is not being changed to "Overpass". Tested in WME & I get "Oh-Pus" (like Mr. Holland's Opus).

"Opas" is on the list of working abbreviations from the first post in this (incredibly long) thread.

Read the very first line of the sheet. Those test results are from Samantha, not Jane.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6048
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1504 times
Been thanked: 2045 times

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

Postby AndyPoms » Fri Apr 28, 2017 1:16 am

Just got a UR that says "Opas" is not being changed to "Overpass". Tested in WME & I get "Oh-Pus" (like Mr. Holland's Opus).

"Opas" is on the list of working abbreviations from the first post in this (incredibly long) thread.
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7174
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1315 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users