RE: Introducing graphics

Subject: RE: Introducing graphics
From: Darren Barefoot <dbarefoot -at- mpsbc -dot- com>
To: "'Karen Field'" <kfield -at- STELLCOM -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 16 Dec 1999 15:26:19 -0800


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

-----Original Message-----
From: Karen Field [mailto:kfield -at- STELLCOM -dot- com]
Sent: Thursday, December 16, 1999 3:09 PM
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.)

Any thoughts? TIA

Previous by Author: RE: Involving Users in Doc. Design?
Next by Author: RE: Screen captures without marquee
Previous by Thread: RE: Introducing graphics
Next by Thread: RE: Introducing graphics

What this post helpful? Share it with friends and colleagues:

Sponsored Ads