I'm just working through the spreadsheet - it was on there, so I put it in my test rig...AlanOfTheBerg wrote:Hospital shouldn't be abbreviated IMO.
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
1) "Capt." (with the period) is pronounced "Capt-ain" (with a pause - I had to listen to it a few times)AndyPoms wrote:1) "Capt" as in "Capt Andrew Rd" is pronounced "Capped" (close, but you get the idea)
1a) Changed to "Capt." for next tile update - will test "Cap" next
2) "Hosp" is pronounced "Hos-puh" (used "Hosp Rd" - i.e. "Turn Right onto Hospital Road")
2a) Changing position for further tests (Now using "Test Hosp" - i.e. "Turn Right into City Hospital")
2) Hosp still pronounced "Hos-puh" for positional test. I do agree with Alan that Hospital probably shouldn't be abbreviated...
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
I'm not showing duplicate TTS files on my phone... I only have one file for each direction...
I've found a couple of files with the same name except the -# suffix on the end, but they are VERY different files, for different streets/TTS directions...
I am looking in \Waze\tts\database\local_nuance_8_mp3_Samantha_Female for these files...
I've found a couple of files with the same name except the -# suffix on the end, but they are VERY different files, for different streets/TTS directions...
I am looking in \Waze\tts\database\local_nuance_8_mp3_Samantha_Female for these files...
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
I found the one I was looking for (using the TTS.db file to turn Words into file names), sorted the audio files by name, found the one I was looking for, played it, then went up and down the list looking for the 2nd one - couldn't find it...GizmoGuy411 wrote:Typically they are one file number different from each other. One will contain just the names of the segment and the other will have the names prefaced with the word "at" like the files in my message about boro, par, and ph saying borough, parade, and phone in one file but borough, par and p h in the other
Sent from my Galaxy Nexus using Tapatalk 2
The files I have for testing Captain:
1350890107-241200-1.tts = "at Capt Andrew Road" (Capt)
1352209891-134545-2.tts = "at Captain Andrew Road" (Capt.)
The files that share filename (except the last digit):
1352212687-976610-2.tts = "at Wilson Street"
1352212687-976610-3.tts = "at Grenhart Road"
More last digit changes & the files around them...
1343979810-878014-6.tts = "at Sherman Ave"
1343979854-936669-7.tts = "at Airport Road"
1343979854-936699-8.tts = "at I-91 S / SR-15 S"
1343979854-936699-9.tts = "at I-91 S / New Haven / North Why City"
1343979854-936730-10.tts = "at I-91 S"
Still no duplicate files...
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Remember there was a period of time when auto-capitalization just started where the word "to" was not exempt & it was automatically changed to "To", so there may be more ramps out there like this...jasonh300 wrote:It's most likely because the word "To" on the ramp is capitalized, which doesn't conform to the standard.
I'm going to send a PM to the editor in question and make sure this is just a typo and not widespread.
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Pkwy confirmed by several people as Parkway.
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Only tested "Pkwy" (first letter capitalized, rest lowercase) in response to another thread...
On a side note "Waze" isn't pronounced correctly - not even close.
On a side note "Waze" isn't pronounced correctly - not even close.
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Xing is a standard MUTCD abbreviation, so I don't see why it shouldn't be used. http://mutcd.fhwa.dot.gov/htm/2003/part1/part1a.htmCBenson wrote:So I just came across the first UR that I have seen that objects to the spelling of an abbreviation. The UR states: "xing is not how you spell crossing!'" The TTS here does speak "xing" as "crossing." So this objection is purely a display objection. Should we not use the abbreviation "xing" if users (or at least one user) objects to the spelling but the TTS is correct?
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
I thought we only found "Br" = "Branch" in the USPS abbreviations, not in the MUTCD. I know in CT (there's a link to the state listing in the TTS spreadsheet) that "Br" is officially "Bridge" (and it's used extensively in the northeast US that way too).sketch wrote:"Br" is apparently the abbreviation for "Branch" according to both the USPS and MUTCD. This is what Waze's TTS abbreviations are apparently based on.AlanOfTheBerg wrote:As noted elsewhere, when in doubt, spell in out.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.
If a local authority disagrees with the USPS and the MUTCD, well, what can we do.
https://www.waze.com/wiki/images/f/ff/W ... 00k_6c.png
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien