andrewfatcat wrote:In my area, I am currently using "Exit xx: xxx Rd, xxx St", and it works pretty well. This uses less character than "Exit xx: xxx Rd / xxx St". I justify this because it is not necessary to be "or" in this case. It can also be "and". Therefore, using ", " should be literally correct.
Commas will always look out of place in this context. The slash is a better visual seperator, and besides, it's already the standard. You will never see a road sign with a comma on it.
I strongly oppose using double-colon for the highway directions because it really looks bad and not logical. If I am going to put the city after the highway, I will be using "Exit xxx: I-10 East (San Antonio)" or "Exit xxx: I-10 East - San Antonio" because they look much better than the double colon and more logical. And I doubt the need to add city name in some cases because it should be already enough for people to understand the directions if there is only the highway name. Putting too much information does not help much and just making the TTS more verbose.
I disagree. Parentheses are clunky, and the hyphen (which should technically be a dash, anyway) with spaces on either side eats up a LOT of real estate.
I think a lot of people are reacting to the idea of two colons in a phrase too quickly. I think we'd have some converts if you had a couple in your area to test. It works. Quite well.
About the entrance ramps in my area, I am currently using "To I-10 North" instead of "to I-10 North". "To" makes the whole thing looks better than using "to", and it is also more literally correct. If one looks closely to some of the highway signs, sometimes there is a "TO" on the top of the highway badge. Therefore, I think capitalize the "T" should not be a problem. The TTS works the same in both cases.
This is another case where there's no reason to mess with convention. "to" is a small formality designed to keep ramps from being selected by the Select All Streets tool. It is a very small word that still manages to take up more screen real estate than it should. Anything that makes it bigger would be counterproductive. Also, the "TO" on some highway signs means something different than it does on our ramps.
jondrush wrote:Also strongly opposed to double colon. Would like to eliminate all colons if we could get TTS to behave. Slashes are extra characters, but they present nicely on the phone display.
A certain element of preferring a colon to a slash or a slash to a dash or a dash to a colon is always going to be aesthetic. Some people are going to like it, some people aren't. Here are the facts:
A colon takes up less space, its proposed usage is logical according to its usage in English grammar, and it currently begets a pause in TTS speech.
A slash takes up more space, does not currently provide a pause in speech (even though this was asked for and promised three months ago), and in the place of the proposed colon it does not make grammatical sense.
A hyphen suffers from many of the same problems: it makes more sense than a slash grammatically (although, again, it should technically be a dash), but it doesn't provide a pause, and in fact that pause hasn't even been requested.
I'm okay with a vote for the approval/rejection process. I have taken your survey, banished.