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:Re: Including Screen Captures From:Robert Plamondon <robert -at- PLAMONDON -dot- COM> Date:Fri, 24 May 1996 15:45:55 PDT
Most of the screen captures I've seen in documents are worse than
gratuitous. Screen captures are easy to make and give the impression
that the document contains illustrations.
While my documents almost always have around one illustration per
page, I rarely use screen captures, because the information they
present is so blindingly obvious that white space would be just
as useful to the reader.
When I *do* use screen captures, they tend to be surrounded by call-outs,
just like they taught me in Technical Illustration class. Screen
captures are too static to stand on their own (except when their
usage is so transparently obvious that the capture itself is superfluous).
-- Robert
--
Robert Plamondon, President/Managing Editor, High-Tech Technical Writing, Inc.
36475 Norton Creek Road * Blodgett * Oregon * 97326
robert -at- plamondon -dot- com * (541) 453-5841 * Fax: (541) 453-4139
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
