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.
Andrew Plato <gilliankitty -at- yahoo -dot- com> wrote:
>I agree. There is absolutely no reason specialized software documentation
>should have basic Windows user-interface instructions. If user?s don?t know how
>to right-click, then send them a copy of that video professor. No technical
>writer at a software firm should be documenting at that low of a level.
As always, it depends ...
If you're documenting a new statewide system being rolled out to counties
that were on a terminal based system (and who sometimes avoided even using that
as much as possible) you might need a little right-clickie verbiage ... in that
case you just try to present it in the least annoying manner possible.
I'd *like* to say "can't they just read Windows Help?". I do say it, at my
desk, just not often in my docs ;).
---
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.
