That seems to fit the rules for abbreviationsLonewolf147 wrote:I just got a report that CH-ID in Wisconsin pronounces as County Highway Idaho, instead of County Highway Eye Dee.
Permalink
I'm asking how the county comes up with the names so we can code a workaround.Lonewolf147 wrote:I'm not sure I understand what you're asking. The CH names are what the county names them.PesachZ wrote:How are WI CH names generated?
I can change this road to put the ID in single quotes if need be as a workaround, but I thought we could have things specified if it came after a hyphen. So that -ID would be Eye Dee and just ID would still be Idaho.
Would you be able to easily cross reference the ch designations against the abbreviation list in the wiki and see if there are any other conflicts please?Lonewolf147 wrote:CH names are always letters here. But how they decided what letters to use is up to each county and can be from a number of reasons.
Note, we do not use CTH- for our naming standard. We use CH-.Wikipedia wrote:Wisconsin uses letters as route designations for its county roads. Routes may be labeled with a single letter (CTH-H), double letter (CTH-LL or CTH-AB) or triple letter (CTH-BBB). Roads are usually named sequentially, though there is leeway to have the letter designation stand for the initials of a road, geographical feature, political division (such as CTH KR along the Kenosha/Racine county line) or in honor of a person.
Route designations may or may not be repeated within a single county, mostly depending on the size and population of the county. Designations also may or may not continue over a county line. Usually the letter designation remains the same when the route is a former Wisconsin state highway that has been decommissioned and turned over to county control. There is no east/west or north/south pattern restrictions on which letters can be used for a road, and they can be looped around counties and metropolitan areas.
Thanks I bring it to the Devs when you're doneLonewolf147 wrote:Easily? No. But I'll get it done today and post back.
Putting here is fine, but give a pl, the full instruction (turn left to ...) That you heard, why it sounded wrong, and how it should sound.ramblinwreck_81 wrote:I'm not sure if I just list words here that are misspoken in the app or if I put them on a list somewhere. Please let me know the right protocol.
The waze app pronounces "Base" like "Bass" (as in the fish).
Example, "Dobbins Air Reserve Base" is currently pronounced "Dobbins Air Reserve Bass"
PL: https://www.waze.com/editor/?env=usa&lo ... st=4923144
It will have to be addressed by the TTS vendor, but will not likely happen very soonramblinwreck_81 wrote:Trying to solve a UR but I have heard the same instructions myself when driving to this road.
PL is above.
What it should sound like is "Base" (above) and what it does sound like is "Bass" (posted above).
The voice instructions recite the "to Dobbins Air Reserve" as above in the PL, only it says "Bass" vice "Base".
Thanks
Noramblinwreck_81 wrote:understand. is there anything else I need to do?
thanks.
Nothingjondrush wrote:What are we to conclude if the new test sounder still doesn't sound like what is being pronounced in the client?
Brg is not a recommended abbreviation, you should be using Br. Unless you can show the BGS actually says Brg.codgerd wrote:Brg is pronounced correctly as 'bridge' when in the course of normal instructions, but is pronounced on my client as B-R-G when it occurs in the little summary spoken prior to starting a route. e.g. "Let's get started! Let's take Burrard B-R-G". Then later, "turn left on Burrard Bridge".
Forgive me, I did not realize you were speaking for Canada. In lieu of doing a full uninstall and install, you can clear your TTS cache. That usually is enough to do the trick. Navigate to cc@ttsKayos_On_The_Road wrote:I also experienced this and reported it to the beta team, but unfortunately they were unable to replicate the issue. It seemed to only happen with the "Lets take..." and "Continue straight..." strings and would occur with both B R G and H W Y abbreviations. Doing a complete uninstall and a fresh install seemed to fix the problem for me, but I wanted to do the uninstall to clean up some other issues as well.PesachZ wrote:Brg is not a recommended abbreviation, you should be using Br. Unless you can show the BGS actually says Brg.codgerd wrote:Brg is pronounced correctly as 'bridge' when in the course of normal instructions, but is pronounced on my client as B-R-G when it occurs in the little summary spoken prior to starting a route. e.g. "Let's get started! Let's take Burrard B-R-G". Then later, "turn left on Burrard Bridge".
Sent from Android using Tapatalk
With respect to the Brg abbreviation, we use the Canada Post addressing guidelines for abbreviations and some are not common between Canada and the US. The Brg abbreviation is in the localization file and is supported in Canada. Another somewhat unexpected abbreviation is Pky for Parkway, where most signage and typical abbreviation is Pkwy. Both are in the localization file.
Kayos
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien