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

[GizmoGuy411]

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.

[floppyrod84]

In that case the first one ()

Sent from my Telenor_OneTouch using Tapatalk

[vectorspace]

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.

[Panda47]

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.

[Webs101]

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.

[AndyPoms]

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.

[floppyrod84]

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

Sent from my GT-I9100P using Tapatalk 2

[mapcat]

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.

[NicoPapa29]

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?

[jasonh300]

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.