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.
Subject:"check" the box (was RE: "Click on" or "click") From:SIANNON -at- VISUS -dot- JNJ -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 4 Apr 2002 7:26:27
Drew Adams mentions some alternatives to the verb "check"
> I've used "turn on" or "enable" (and "turn off" or "disable").
I agree with your concerns on ambiguity, but I want to toss in a potential
problem with using enable/disable. Say you have a GUI in which there is
"enforced permitted sequencing of steps" (FDA's way of saying you use GUI
elements to constrain user actions to a specific procedure). A text box or
other control on the screen may not be "enabled" for entry/use until some
other button is clicked, or some other action completed.
Example: "On entry of the sixth character of the order code, the action
buttons will become enabled, based upon the status of the product. Only
product that has completed quality testing will have the button 'Shipping
Checklist' enabled. Click 'Shipping Checklist'. The Shipping Checklist
dialog box will appear, displaying the list of shipping options available.
Note: options not supported by a specific facility will be disabled, and
appear grayed out. Check all options that apply, and click 'Save
Options'."
I appreciate this discussion...while it may fall under the heading of
"fussing over details", underneath it addresses some of the how's and why's
that need to be kept in mind when analyzing the audience of a doc. We
repeat the mantra "Know thy audience" a lot, but sometimes it's not always
easy to _get_ to know the audience (cf. previous posts by people never
allowed contact with their target audience). Sometimes there is too much
assumption of technical knowledge (e.g., "if your users don't know how to
<insert standard Windows interface convention here>, you've got bigger
problems"...never mind the fact that the blue-collar users being targeted
may not have completed high school and have never worked with computers
before in their lives...). Sometimes there's localized language conventions
(especially for folks dealing with their first international audience, and
different languages or dialects).
...just another two cents...
Shauna
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.