How about CR-##?
Last February it worked. For some reason I had an "Add" notation for it. Guess I should retest it.
Now that the tile turn around time has shortened I need to test the rest of the list. Hopefully before mid January.
How about CR-##?
Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)
imajica12345 wrote:I live in Quebec and often we have streets with directions like east/west, but here it is spelled est/ouest. it pronounces the ouest as west which is fine, but it pronounces est as "Estate".
Something to eventually fix i assume
txemt wrote:I have confirmed, today, that "SH" for "State Highway" is NOT working.
AndyPoms wrote:Pkwy confirmed by several people as Parkway.
hmarian wrote:The same for me.
"Pkwy" is reading out "Parkway" on the client and is more consistent with road signage.
Could someone finish this test and add to the TTS Log FIle?
rcenteno_davis wrote:... Do we need to add a separate row?
In the Text-to-Speech (TTS) Abbreviations in Waze Clients
Test List for North America, GizmoGuy wrote wrote:
• Waze creates two TTS audio files for every routed road segment on the Android. One file speaks just the names contained in the segment name property. The other prefixes the segment name with the word "at". (On iOS devices, only the prefixed files have been found thus far.) It was not until late 2012 that a distinction in the TTS results between the two files was noticed. Testing of both files started on 2013-01-12, when a second result column was added. Therefore, until all items are re-tested, an entry in the Non "at" prefixed audio file column, will be either for the prefixed or the non-prefixed results if the "at" prefixed audio file column is empty.
Users browsing this forum: No registered users