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.
txemt wrote:I have confirmed, about 5 minutes ago, that Clle reads out as "call"
AlanOfTheBerg wrote:txemt wrote:I have confirmed, about 5 minutes ago, that Clle reads out as "call"
I thought we decided a while back to just spell out "Calle" as it's only a single character different.
Users browsing this forum: No registered users