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: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby GizmoGuy411 » Thu May 10, 2012 5:33 am

xteejx wrote:Actually, enclosing N/E/S/W in brackets also makes it say the directions.


Types of brackets (quoted in part from Wikipedia):
( ) — round brackets, open brackets, brackets (UK), or parentheses (called parentheses by Microsoft)
[ ] — square brackets, closed brackets, or brackets (US), (called square brackets by Microsoft)
{ } — curly brackets, definite brackets, swirly brackets, curly braces, birdie brackets, Scottish brackets, squirrelly brackets, braces, gullwings, seagull, fancy brackets, or DeLorean Brackets, (called curly brackets by Microsoft; see Character Map - %windir%\system32\charmap.exe)

I hate to say it, but I guess we need to test N/E/S/W with all of them.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1370
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 538 times
Been thanked: 352 times

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

Postby floppyrod84 » Thu May 10, 2012 10:32 am

In that case the first one ()

Sent from my Telenor_OneTouch using Tapatalk
floppyrod84
 
Posts: 2583
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 44 times

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

Postby vectorspace » Sat May 12, 2012 3:20 pm

Another topic: Indian Reservations in the US...

I've not been a part of this discussion and have searched the 18 pages on TTS without finding anything. This is also probably a topic for textual road abbreviations on the client.

There are a lot of American Indian reservations in the US Southwest. I am starting to address some of the roads there now in New Mexico. I see that these are not well represented in the material on Waze likely because they have fewer drivers. Some areas are high traffic from tourism or casino traffic. These regions actually have a large amount of autonomy from the US Government and therefore different road naming conventions than states or interstates.

One convention is "Indian Service Route XXX." Many times these are named inconsistently in the current map with the usual abbreviation "Indian Svc Rte XXX" being used, but sometimes other variations being used for highway-like roads. Other lesser streets have names like "Indian Rd XXX." Other states may use other naming conventions.

It would seem that the primary textual values on the map are displayed on an often-cramped client display, a much shorter version could be used. This would impact the TTS as well. Obviously the smallest abbreviation might be "ISR-XXX." That's one I prefer because it seems brevity is the primary driver due to a small client display.

It would be nice if we considered the US Indian reservations in both the textual abbreviations and the TTS.

As a relative outsider (6 months new) and pragmatist, I am often struck by how the Waze software team seems distant from the dedicated AM/editor group both dynamically and by setting standards. Maybe that is part of what makes a world-wide social app work. Efforts here are commendable. Client/Server software seems like the place to solve a lot of these issues with ability to parse a wide range of naming conventions and abbreviations. If Waze is truly successful in having a community-based editing crowd, many less-dedicated and formalized editors will name things however they want and that crowd will overwhelm dedicated editors.
vectorspace
vectorspace
 
Posts: 1185
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 419 times

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

Postby Panda47 » Sun May 20, 2012 1:10 am

Hi. Can we get the following special character in it? I know you have it already surrounded by single quotes, but what about w/o the quotes? What about with a street name?

Character = ½
Example: 30th ½ St
Example: 31st ½ St

Thanks, and keep up the good work.
~David~ Motorola Atrix 4G (Android 2.3.6) - Waze 3.2.0.0
ImageImage
South Texas AM - aka the Rio Grande Valley
Panda47
 
Posts: 122
Joined: Tue May 01, 2012 7:59 am
Location: Mission, Texas, USA
Has thanked: 0 time
Been thanked: 0 time

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

Postby Webs101 » Mon Jun 18, 2012 11:55 am

Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Also, along with Saint, there is also Sainte for the feminine. Normally abbreviated St and Ste without periods.
ImageImage
Webs101
Waze Local Champs
Waze Local Champs
 
Posts: 451
Joined: Sun Feb 26, 2012 9:09 pm
Location: Montreal, Quebec
Has thanked: 13 times
Been thanked: 145 times

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

Postby AndyPoms » Mon Jun 18, 2012 12:03 pm

Webs101 wrote:Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Isn't that because it's French? (i.e. Nord, Sud, Est, Ouest = North, South, East, West)

Wouldn't it just be easier to use N, S, E, W as the cardinal (compass) directions in Waze? And then you can change the language in the app to either Engilsh (and get North, South, East, West) or French (and get Nord, Sud, Est, Ouest) - I think, I'm not about to change my Waze to French as I may never get it back to English.
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7077
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 127 times
Been thanked: 1286 times

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

Postby floppyrod84 » Mon Jun 18, 2012 12:07 pm

We seem to have lost cardinal directions here ie (N) (S) etc :-(

Sent from my GT-I9100P using Tapatalk 2
floppyrod84
 
Posts: 2583
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 44 times

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

Postby mapcat » Mon Jun 18, 2012 1:13 pm

AndyPoms wrote:
Webs101 wrote:Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Isn't that because it's French? (i.e. Nord, Sud, Est, Ouest = North, South, East, West)

Wouldn't it just be easier to use N, S, E, W as the cardinal (compass) directions in Waze? And then you can change the language in the app to either Engilsh (and get North, South, East, West) or French (and get Nord, Sud, Est, Ouest) - I think, I'm not about to change my Waze to French as I may never get it back to English.

No, he's saying that Waze pronounces roads like "Autoroute 20 Est" as "Autoroute Twenty Estate" instead of the preferred "Autoroute Vingt Est".

Unfortunately, the North America server (USA+Canada) only has English TTS at the moment, and until all the Anglo pronunciations are correct, I doubt they'll be able to work on the other languages.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

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

Postby NicoPapa29 » Thu Jul 12, 2012 3:30 pm

I live in South Africa and find WAZE a brilliant application.
Problem is that TTS is wrongly describing our HighWays.

All South Africa's National Highways and Roads are "Prefixed" with an "N"
The "N" stands for "NATIONAL"

In Johannesburg the major highways are:
N3
N1

TTS translates this to "North 3"
It should remain as "N3" because the N SHOULD NOT translate to "North" and no one refers to them
as "National 3" so that wouldnt make sense either.

TTS should remain as "N3"

How can this be achieved?
NicoPapa29
 
Posts: 1
Joined: Wed Jul 04, 2012 5:04 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby jasonh300 » Thu Jul 12, 2012 3:49 pm

Should be pretty simple to fix if the N and the 3 don't have a space between them. (do they?)

Send a request to support via nanorep on the support page.
Image
New Orleans, Louisiana, USA
South-Central Regional Coordinator
(LA/MS/AR...contact karlcr9911 for TX/OK related issues)
U.S. Champ, Global Champ
Waze FAQ ... Best Map Editing Practice
Ask me about Louisiana Editors Chat in Google Hangouts!
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 7557
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 399 times
Been thanked: 967 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: johnsninja58