Re: Poll: How do you differentiate commands, etc. in text?
That's because there's no unequivocal "best practice". Many options
work equally well; there may be "statistically significant"
differences, but I haven't yet seen any evidence that there are
_practically significant_ (i.e., meaningful) differences.
I use words combined with quotation marks where necessary. For example:
Open the Menu menu and click the Button button. Then enter your name in
the "Name" field.
I'm skeptical about boldface because with enough commands, the printed
page starts to look like your pen was blobbing ink, and the help topic
looks like the monitor is misbehaving. You'll often see typographers
refer to this as "the ransom note syndrome" because the text looks
pasted together. The bold stands out enough that it attracts too much
attention, and that's rarely a good thing. Italics has been a
traditional solution in print because it stands out less, but does
differ enough from its surroundings that it achieves the goal of
On 6/28/06, Dick Margulis <margulisd -at- comcast -dot- net> wrote:
Less is more. The simpler you can make the styling, the clearer it will^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
be to the reader and the less likely you and your coworkers will screw
up in implementing the style.
I use--and recommend--caps and lowercase to name things. Period. Press
Enter. Type your name in the Name field. The Customer Account window
opens. Click the New Address button. Etc. (Those are not meant to
constitute a sequence of steps; they're unrelated examples.)
I've suggested before, and apparently convinced a few people that it
makes sense, using caps and lowercase when referring in documentation to
longer UI labels, even if sentence case is used for the labels
themselves. For example, if a Print dialog has a field labeled "Number
of copies," I would refer to it in documentation as the Number of Copies
Using caps this way and avoiding font changes, bolding, italics, etc.,
meets Edward Tufte's criterion of "least perceptible difference" and
serves your purpose well, I think.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com
To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.
Poll: How do you differentiate commands, etc. in text?: From: Diana Ost
Poll: How do you differentiate commands, etc. in text?: From: Geoff Hart
Previous by Author:
Re: Converting embedded Word Images
Next by Author: Re: Word and crashing
Previous by Thread: Poll: How do you differentiate commands, etc. in text?
Next by Thread: Re: Poll: How do you differentiate commands, etc. in text?
Search our Technical Writing Archives & Magazine