Re: Focus & proc'd?
Neither word should ever appear in documentation unless the audience is
entirely composed of programmers, and even then, I'm not sure "proc'd" would
be obvious. ...
Think of what you're trying to say from the user standpoint, and if no one
word works to communicate that concept, then don't try too hard to find a
single-word solution. Describe what the user sees and what it means to them
Sound advice, and I agree with your prejudice in favor of plain language. But you can carry the principle too far. In the case of "focus", this is a concept that basic to GUI usage, and not one you can avoid. If you try, you have to do a *lot* of paraphasing. Not a formula for clear writing!
Sometimes jargon is unavoidable, because there's no practical way to talk without it. If you have to use a word your reader might not know, then you provide a definition. If you're writing a tutorial, you put the definition inline before the first usage. If you're writing a reference book, you provide a glossary.
ROBOHELP FOR FRAMEMAKER TRIAL NOW AVAILABLE!
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web. The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
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.
Search our Technical Writing Archives & Magazine