Jane is clearly a Heathen.voludu2 wrote:https://www.waze.com/editor/?env=usa&lo ... st=4816115
"Ithan" should be pronounced "Eye-thən". Jane says "Ee-thən"
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
"Exits 14-1:" says "Exits 14 to 1" - yes, I know this should say Exit, not Exits. Nearby Exit 14B-61 works correctly. It is possible that there are special rules for ^Exit \d+-d+: ... if so, I can make the fix, drop the s, and test, before proceeding.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
14-1 has been there since forever - at least two years. The nearby 14B-61 reads the dash as a short pause. I'd be fine with either that or "fourteen dash one."
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
That's surprising since it is such a great discrepancy. Have you heard it yourself on multiple tries?mrsmith66 wrote:United States, New Jersey, Mercer County, Hamilton Township
"Gropp Ave" is read as "Grant Ave". Gropp rhymes with crop.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Really? I thought we followed whatever street signs said. 11 vs 11th seems like NBD for real estate, and "eleven avenue" sounds awkward to me.
PesachZ wrote:This isn't really a TTS question both options "Eleventh" and "11th" will be spoken the same by TTS. However for uniformity, simplicity, and the smaller space on the screen it uses, we prefer the numerical digits when the sign is spelled out.G_W1Z wrote:Sorry if this has been discussed/posted before.
I have looked over the standard suffix abbreviations page and am left with a question: should numbered street names which appear on signs as letters be named with a number? Example: 11th Ave in Springettsbury PA (York). In WME (Permalink) it is given the digit name instead of the lettering.
Sent from Android using Tapatalk
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
https://www.waze.com/editor/?env=usa&lo ... 5,82859798
Secaucus is pronounced correctly when it is at the end of the segment name, (se-CAW-cuss, segment on the upper right), but mispronounced when there is text following (se-CAW-keez, segment on lower left connecting to eastbound local lanes).
Secaucus is pronounced correctly when it is at the end of the segment name, (se-CAW-cuss, segment on the upper right), but mispronounced when there is text following (se-CAW-keez, segment on lower left connecting to eastbound local lanes).
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
I believe that's destination TTS, which does not use the same code as seg name TTS.Poncewattle wrote:Just last week I was routed to a doctor that ended in PA (search result pulled from Google since there is no Waze place for it) and it said "You have arrived at Dr. Alfieri PA" but Jane pronounced it Pennsylvania.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Kartografer wrote:DrDisaster wrote:Chili is not pronounced like the food or chilly weather. It should be a long I like eye. Ch-eye-l-eyeYes, a word can only be pronounced one way. For example, I'm sure New Yorkers would like Waze to read Houston St as "hauston street," but since Houston is pronounced as "hyuston" in the rest of the US we can't change it without making the pronunciation incorrect to more people.xanderb wrote:In most cases where a word or road name is very commonly pronounced a certain way, it is impossible to replace for a single road. Those TTS replacements are done for the whole country.
German hauston?
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
After reading this thread for the first time, I really like the notion of a separate TTS field. Would solve alot of the issues with overlapping abbreviations.
Tennessee Editors, paritipate in our Wikipage
Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze tobanished wrote:I am uncertain if spelling or standard abbreviations is taught at Street Sign School.AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
Normally, Trail would be Trl, Terrace would be Ter
https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).
implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?
Tennessee Editors, paritipate in our Wikipage
Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien