TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>Parks, Beverly wrote:
>> I use "press". That's what you do with buttons, you press them. That is
>> even the visual effect you get when you perform the action.
Kim Keegan wrote:
<<
>So how do you differentiate keyboard input vs. buttons on the screen?
>That is, do you also say "Press the Enter key"? Or are you one of the
>more violent types that uses "Hit" or "Strike"? (Just kidding...) ;-)
<<
I say "Smash that Enter key!" In the application I document (yes,
there's just one), none of the labels on the GUI buttons match any keys
on the keyboard (except Delete), so I just say "Press Update", "Press
Close", "Press Enter", "Press Tab". I can't think of a single instance
at the moment where the user has to press the delete key as opposed to
the delete button. At least not a documentable (is that word?) instance.
They can delete highlighted text with the delete key, but that's a
Windows task.
I use "select" for when they have to select an item from a table (grid)
or a tab from a tabbed dialog. For menu items and option buttons, I use
"choose". I use "type" when they have to enter text from the keyboard.
And I use "click" for checkboxes.
>>
>To me, reading the command "Click" tells my brain to "use my mouse to
>move the pointer to the appropriate place on the screen - a button for
>instance -- and click the left mouse button once." The term "click", in
>the software documentation world, automatically implies using a mouse
>(or non-keyboard input device?).
<<
Very true. In the front of the manual I define the mouse actions "single
click" (or just "click") and "double click". And (oh, no!) I just
noticed I use "click on" in some instances. For inputting dates, there
is a calendar that pops up and I tell the user to "click on any date in
the month to select a day".
>
>>My US$.02 worth.<<
It was quite a bargain. ;-)
With this, I'm outta here till Monday.
>
>Bev Parks
>parksb -at- emh1 -dot- hqisec -dot- army -dot- mil
>The Friendly Faces of TECHWR-L -
>http://www.bayside.net/users/cbsites/techwr-l/
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html