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.
Actually, unless the image is critical to the description that goes with it,
we don't use any referential or introductory text. Given the frequency with
which we single-source, we're never sure if we're always going to use a
given screenshot with the text. However, we always use "following" instead
of "above" or "below" and generally we'll say "diagram" or "screen shot"
wherever appropriate.
Darren Barefoot
Meridian Project Systems
Manager of Documentation
604-904-0822 ext. 112
dbarefoot -at- mpsbc -dot- com
www.mps.com
-----Original Message-----
From: Karen Field [mailto:kfield -at- STELLCOM -dot- com]
Sent: Thursday, December 16, 1999 3:09 PM
To: TECHWR-L
Subject: Introducing graphics
Greetings, gang.
How do you introduce graphics in your manuals? For example, in procedures,
do you write, "[Do this], and then click Save, as shown in the following
image"? Do you use the "image" or "graphic" or "illustration"? (I deal with
screenshots of software programs and Web apps.)
