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

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

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby kentsmith9 » Sat Nov 17, 2012 7:57 pm

AndyPoms wrote:Remember there was a period of time when auto-capitalization just started where the word "to" was not exempt & it was automatically changed to "To", so there may be more ramps out there like this...

That was during July or Aug this summer. I have a bunch around me that came from my edits during that time.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Sat Feb 02, 2013 5:02 am

I assume we need to update the Wiki with this new recommendation.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Sun Feb 03, 2013 9:13 pm

sketch wrote:
Timbones wrote:
orbitc wrote:Would you put Avenue S as Ave 'S' or just leave it as Avenue 'S'?

Not sure. Is it "Avenue Ess" or "Avenue South"? Which is the noun? Does it really need to be abbreviated at all? Maybe it's time to get rid of them altogether. Devices have much higher resolutions these days, and there's plenty of space on the screen for full road names... [/rant]

I don't think so. Resolutions are getting higher but not all screens are getting bigger. I think you'll have a tough time justifying spelling out "Boulevard" or "Throughway" in any case.

I absolutely agree. I still have an iPhone and my screen is the same as it was 3 years ago. With a huge market share of smartphones I believe we still need to keep the text condensed as much as possible in the directional text areas.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Tue May 14, 2013 3:39 pm

This conversation has been launched in two separate threads. This one and viewtopic.php?f=8&t=47255&start=10#p440213
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Tue Feb 04, 2014 5:20 pm

Doing some Wiki cleanup. I noticed on the OP the link to Abbreviations and acronyms was changed in the Wiki for country specific naming some time ago. I fixed the OP to note that and then added a link directly to the US version of the page for faster linking and less confusion for people in this US forum.

In reviewing this page on Abbreviations and acronyms the first section seems out of place in the flow. I propose that we move it after the standard abbreviations section. However since the standard section is so long, I will include a note in that section pointing people to the "non-standard" section if they don't see what they are looking for.

I also added an opening to help clarify the purpose of the page. We can add more if we think it is necessary.

GizmoGuy, I recommend when you update the Wiki with new info from this thread (as I assume you have been doing), maybe put a comment in the Wiki page in the Other Reading section saying the data on the Wiki page is current from forum feedback as of X date.

Final note. The Wiki does not like using "&" in page titles. The page above previously used an "&", so I renamed (moved) the page to use "and" instead. There is a redirect page for any other links to the old "&" format so there are no problems getting to the page with either spelling. Over time I will search them out and replace them for general cleanup, but we will leave the redirect just in case there are external links outside the Wiki. I cover it in the Wiki forum here.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby kentsmith9 » Wed Feb 05, 2014 1:01 am

It looks like one of our Australian editors was making some changes for the Australian pages and then came in making changes here as well.

sketch wrote:
bgodette wrote:
qwaletee wrote:That page needs serious copyediting.
Go right ahead, and be sure to submit it to a new page or sandbox so others can review your work.

It's not copyediting that page needs, it's a full rewrite, and maybe just a removal of that first section. Those are not the rules, at least in the US, and they don't belong on a country-nonspecific page. (They are, indeed, also pretty difficult to understand.)

I would agree and I am fine if qwaletee wants to take a first crack at it.

I created a separate page linked to the original just for easy locating if we all forget about it. Whoever holds up their hand first should be given initial control over the page and then ask for input from this forum. I have temporarily assigned it to qwaletee, but if someone else steps up or wants it just change the name at the top of the page linked above.

Once we all agree or get enough consensus we can just cut and paste the new content over the old. No need to track our session edits before the final. The history will hold the original page changes for reference.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

Re: Forest Service and Bureau of Indian Affairs

Postby kentsmith9 » Tue Feb 25, 2014 4:58 am

dbraughlr wrote:There are prefixes like "I-" and "US-" don't get special pronunciation.
For all these that you propose, I would be fine with just the letters being pronounced.

Otherwise, what the harm is there in shortening them?
  • IRR-xxx → "Reservation Road".
  • ITR-xxx → "Tribal Road".

Are you proposing two possible options for "IRR-123" to be pronounced either
1. "Eye Are Are One Two Three"
or
2. "Reservation Road One Two Three"

Was there a desire not to have it say the whole thing, or were you just offering ideas to shorten it?
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

Re: Forest Service and Bureau of Indian Affairs

Postby kentsmith9 » Tue Feb 25, 2014 9:35 pm

bgodette wrote:
kentsmith9 wrote:
dbraughlr wrote:There are prefixes like "I-" and "US-" don't get special pronunciation.
For all these that you propose, I would be fine with just the letters being pronounced.

Otherwise, what the harm is there in shortening them?
  • IRR-xxx → "Reservation Road".
  • ITR-xxx → "Tribal Road".

Are you proposing two possible options for "IRR-123" to be pronounced either
1. "Eye Are Are One Two Three"
or
2. "Reservation Road One Two Three"

Was there a desire not to have it say the whole thing, or were you just offering ideas to shorten it?
Perhaps the reasoning is much like with County Roads. The generic is just County Road even tho they may be signed or locally known as <Countyname> County Road ###.

Yes that does make sense. So I would support number 2 based on that logic for consistency.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 3127
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 525 times
Been thanked: 594 times

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

Postby khaytsus » Sun Nov 11, 2012 11:57 pm

Anyone know the proper abbreviation for Sideroad? I thought it was Srd and had been using this, but that is pronounced "S R D". Not seeing it in the spreadsheet either.
USA Country Manager
Central Kentucky Area Manager
ATT LG G2 (AOKP 4.3)
Nexus 7 (Rooted, Stock 4.4 Kit Kat)
Samsung Galaxy Note (i717 AT&T; AOKP 4.3.1 Jellybean)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 769
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 33 times
Been thanked: 54 times

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

Postby khaytsus » Tue Nov 13, 2012 12:22 am

jasonh300 wrote:
khaytsus wrote:Anyone know the proper abbreviation for Sideroad? I thought it was Srd and had been using this, but that is pronounced "S R D". Not seeing it in the spreadsheet either.


Is this really a street type? Post an example.

In my case, it's usually when a street has a side road which leads to businesses, or the road has been replaced with a wider road and the original road left paralleling the new road.

http://goo.gl/maps/K9k52 (ignore the name, Google and Bing both have it as the same name of the main road, but other sources have it as "Srd".

http://goo.gl/maps/2KZQh (this case they have the name right).

http://en.wikipedia.org/wiki/Side_road
USA Country Manager
Central Kentucky Area Manager
ATT LG G2 (AOKP 4.3)
Nexus 7 (Rooted, Stock 4.4 Kit Kat)
Samsung Galaxy Note (i717 AT&T; AOKP 4.3.1 Jellybean)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 769
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 33 times
Been thanked: 54 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: ply8808, vectorspace