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.
I generally don't introduce graphics, which for my books are screenshots of
software, in my books. Introducing the graphics doesn't gain me anything and
using words like following, above, and below might not make sense when a
page break happens or in an online document. Furthermore, neither do I use a
LOF. Simply, I write the step, insert any and all appropriate graphics and
then write the next step (or procedure, or description, etc.).
Best regards.
Sean
sean -at- quodata -dot- com
> -----Original Message-----
> From: Karen Field [SMTP:kfield -at- STELLCOM -dot- com]
> Sent: Thursday, December 16, 1999 6: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.)
>
> Any thoughts? TIA
