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

Image This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderator: adriansinger

Re: Roman numerals

Postby dbraughlr » Wed Jun 04, 2014 7:32 pm

GizmoGuy411 wrote:I agree with sketch in that I am really not very concerned about Roman Numerals and that the letters themselves are more important at least for North America using the English voices.

We all agree.

GizmoGuy411 wrote:What I am MORE concerned with is why these variations exist in the first place and if they are indicators of some bad RegEx that needs to be addressed at the Waze end, as other parts of the world may need Roman Numerals.


Scrapping Roman numerals is a good way to avoid the bugs and problems they cause.

GizmoGuy411 wrote:Actually I don't think there are many more instances than those I listed as potential conflicts with Roman Numerals. This was limited to valid Roman Numerals, not simply every possible combination of letters used in Roman Numerals. I'll edit that in the prior post.


The highest number you gave in the prior post was MM. In order for that range of Roman numerals to work, all 2000 combinations from "I.", "II.", to "MCMXCIX.", "MM." would have to be defined as abbreviations.
That seems unrealistic. That's why I suggested an upper limit like 30.
dbraughlr
 
Posts: 559
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 162 times
Been thanked: 97 times

Re: search by numeral

Postby dbraughlr » Thu Jun 05, 2014 2:20 am

I expect a search to succeed even with a synonym, e.g., "first" = "1st" "eighty four" = "84".
I'm not particular about how it looks.
dbraughlr
 
Posts: 559
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 162 times
Been thanked: 97 times

Re: Roman numerals

Postby dbraughlr » Thu Jun 05, 2014 5:16 pm

I favor eliminating all Roman numerals as abbreviations. The disadvantages far outweigh any advantages. Pronunciation of "XIV" can be addressed when the pronunciation of "Louis" is addressed.
dbraughlr
 
Posts: 559
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 162 times
Been thanked: 97 times

Re: Roman numerals

Postby dbraughlr » Fri Jun 06, 2014 5:32 am

sketch wrote:Unless "Louis" is pronounced neither the English nor the French way, it cannot be "fixed". In some places one will be right, and in others the other, but no universal fix is possible.

Another proposal in another thread addressed this; I'm pretty sure you were there.
dbraughlr
 
Posts: 559
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 162 times
Been thanked: 97 times

Re: state abbreviations

Postby dbraughlr » Mon Aug 04, 2014 5:34 pm

sketch wrote:BGSes usually use the old-fashioned abbreviations, and I think it'd be nice to include those, with periods only, as TTS abbreviations – for example Ala. for Alabama, La. for Louisiana, Calif. for California, Penna. and/or Pa. for Pennsylvania, and so forth.

Having the period is good. I couldn't say what is usual, though. I've not seen Conn that I recall. So I think CT is the usual. NY, DC, NJ, and NC, are prevalent.
dbraughlr
 
Posts: 559
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 162 times
Been thanked: 97 times

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

Postby dctdye » Wed May 29, 2013 8:14 pm

I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:

https://www.waze.com/editor/?zoom=6&lat ... nts=956781
Area Manager- Tuscaloosa/Northport, AL

Image
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby dctdye » Wed May 29, 2013 8:24 pm

AlanOfTheBerg wrote:
dctdye wrote:I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:

https://www.waze.com/editor/?zoom=6&lat ... nts=956781

You need to have spaces on both sides of the slash characters, per the naming guidelines.

Figured it was something simple like that. That's hopefully fixed now. Thanks :D
Area Manager- Tuscaloosa/Northport, AL

Image
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby dctdye » Wed May 29, 2013 8:33 pm

AlanOfTheBerg wrote:
dctdye wrote:Figured it was something simple like that. That's hopefully fixed now. Thanks :D

I noted others in the area, too. You'll probably be going around fixing a bunch now?

Later today or tomorrow. Ah, the editing never ends. Also, hopefully they are all level 3 or below segments.
Area Manager- Tuscaloosa/Northport, AL

Image
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby dknight212 » Wed Sep 12, 2012 9:15 am

lovely
dknight212
Waze Global Champs
Waze Global Champs
 
Posts: 4964
Joined: Sun Apr 24, 2011 9:21 am
Location: London, UK
Has thanked: 471 times
Been thanked: 635 times

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

Postby dknight212 » Mon Nov 19, 2012 12:30 pm

Not very clever!
dknight212
Waze Global Champs
Waze Global Champs
 
Posts: 4964
Joined: Sun Apr 24, 2011 9:21 am
Location: London, UK
Has thanked: 471 times
Been thanked: 635 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users