Page 4 of 159

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Tue Sep 11, 2012 12:58 am
by AlanOfTheBerg
xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!
I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Sep 12, 2012 4:22 pm
by AlanOfTheBerg
GizmoGuy411 wrote:..."bee eye aye" ...
FYI, in my area of the country "eye" and "aye" are both pronounced the same. :lol:

Phonetic representation of that would be "eɪ" as in "say," but that makes me realize there is no real easy was to represent vowel-only sounds without resorting to "as in" or using the phonetic characters.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Fri Sep 21, 2012 4:24 pm
by AlanOfTheBerg
As is mentioned in this thread and elsewhere, we have no ability to influence TTS pronunciation. We have requested a phonetic field which would help in many cases, but would not likely be able to influence accents.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Oct 31, 2012 4:48 pm
by AlanOfTheBerg
I spell out "Branch" and "Bridge" because Br is a valid abbreviation for both. I've see Brg for bridge, but haven't looked at the list to see if Waze pronounces it properly. It probably does.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Wed Oct 31, 2012 10:29 pm
by AlanOfTheBerg
harling wrote:I can tell you definitively that Brg = "bridge".
Cool. I still think "Bridge" looks better. :)

Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Posted: Sun Nov 04, 2012 4:25 pm
by AlanOfTheBerg
Hospital shouldn't be abbreviated IMO.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Tue Nov 06, 2012 4:39 pm
by AlanOfTheBerg
GizmoGuy411 wrote:Boro → Borough
That's not an abbreviation, but simply how you would pronounce "boro" as a stand-alone word. :)

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Tue Jan 15, 2013 6:32 pm
by AlanOfTheBerg
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.

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Mon Jan 28, 2013 3:36 am
by AlanOfTheBerg
Since we parse this "Exit 70A-B" in our mind as two separate exits, you could simply name the ramp "Exit 70A and B" because that's what we think in our head anyway. Since there is no other wording on the first BGS, just leave all the other words off the ramp name, letting that verbiage be part of the subsequent actual Exit 70A and 70B.

(FYI: I also will often take the first ramp and leave it unnamed because no driver who should be driving should be confused when they here "Exit to the right at exit 70A...." or "70B" when the sign says "70A-B". It's just clearly obvious.)

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Posted: Thu Jan 31, 2013 12:20 am
by AlanOfTheBerg
txemt wrote:
jemay wrote:But putting a period implies there is more to the letter (representing a word).
Huh?
A period means either the end of a sentence or that it is an abbreviation. One could argue E. is an abbreviation for East, but it cannot be an abbreviation for "ee" and therefore the dot method, I feel, should not be used.