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.

Re: BI- prefix for interstate business loops

Postby dbraughlr » Tue Mar 04, 2014 7:40 pm

davielde wrote:… where would "Business US-[#]" routes fall? In making things convenient from a TTS and shield-generating standpoint for interstate business routes only using "BI-", are we sacrificing consistency with US business routes, or should potential abbreviations be discussed with those in mind as well? "BUS-[#]" likely wouldn't work as we know how that is pronounced...

I think "BUS-" (business alternate or biz alt) is fine for business alternate route. But there is a conflict if TTS interprets Bus or bus the same as "BUS".
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: business loop/spur/alternative route

Postby dbraughlr » Mon Mar 17, 2014 7:47 am

Those who are interested in the discussion of "Business" in the highway name, please see this thread on the subject to address the first matter of updating the wiki to standardize naming without the abbreviation "Bus".
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: MT = ?

Postby dbraughlr » Tue Apr 15, 2014 6:48 am

What happened to MT = Montana ?
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: Roman numerals

Postby dbraughlr » Mon May 12, 2014 6:34 pm

Whether Louis XIV is read as lewis ex eye vee or lewis fourteenth, it won't be perfect.

I think we want C, D, I, L, M, V, and X pronounced as letters. It seems that Roman numerals are the exceptions and should require special notation if used at all.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: Penn

Postby dbraughlr » Fri May 23, 2014 11:48 pm

sketch wrote:"Penn" should say "penn", but do we want "Penn." to say "Pennsylvania"?

No. Before the postal abbreviation "PA" came into use, the abbreviations were "Penna." or "Pa.". "PA" has become so widespread that even most old-timers refer to the state using the modern "PA", as in "I've lived in PA for 80 years".
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: Penn.

Postby dbraughlr » Sat May 24, 2014 9:55 pm

Image
Image
Perhaps we can collect actual examples.
Last edited by dbraughlr on Sat May 24, 2014 11:03 pm, edited 1 time in total.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: Roman numerals

Postby dbraughlr » Wed Jun 04, 2014 7:37 am

GizmoGuy411 wrote:Therefore we may need to follow suite for the letters used for Roman Numerals too.

From what you listed, there are thousands of them. That's clutter.
What range do you really intend to cover?

GizmoGuy411 wrote:So maybe Roman Numerals could use a period after them instead of quotes to differentiate them.

That doesn't seem likely, at least not if you intend to cover a range beyond 1 to 30.

What's wrong with using Louis the 14th instead of Louis XIV.? If anything, our experience with N/E/S/W should tell us that it was a bad precedent that should not be expanded.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: search by numeral

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

sketch wrote:Street names should still match signs. If it says "Louis XIV" use "Louis XIV". No one is going to think to search for their aunt's house at 1234 Louis The 14th St", and it's going to look wrong on the client display.


So where the signs say "First St", "Second St", etc, and Waze has "1st St", "2nd St", etc, that is wrong, looks wrong in the client, and causes searches to fail? Is this written is our road naming standard somewhere?

It seems to me that the fuzzy search engines can treat "XIV" as a synonym for "14" and search correctly.

Of course, writing "the 14th" instead of "XIV" goes back to the matter of pronunciation and how to get "Louis" spoken as "Louie" which would be a good way to handle pronunciation of Roman numerals too.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

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: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 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: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users