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.
Re: When to use screen shots (was: screen dumps in books)
Subject:Re: When to use screen shots (was: screen dumps in books) From:"Huber, Mike" <mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM> Date:Tue, 19 Jan 1999 09:53:57 -0500
> From: Brierley, Sean [mailto:Brierley -at- QUODATA -dot- COM]
...
> So, how about it? When to use screen shots (including re-typing or
> capturing text-based screens) and when not to?
Use a screen shot when a screen shot would make the information more accessible to members of the target audience. Otherwise don't.
Given the range of target audiences, material to be communicated, and types of documents, any other general rule is yet another example of pointless rule making. Focus on the real question: would a screen shot here help the intended reader?
There is an old Norse rule on how much mead one should drink that sounds very similar, but I can't recall the exact phrasing.
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
