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: screen dumps in books From:John Posada <john -at- TDANDW -dot- COM> Date:Tue, 19 Jan 1999 09:28:52 -0500
Youy just hit the key regarding why have screen shots. "user sees on their
terminal under normal circumstances?"
What about abnormal circumstances? I'm sure you are aware that you don't always
get what you expect on a screen and the screen shot confirms to the user that
they are on the right path. Screens give the user assurance that they are doing
it right when they see on the screen the same image as in their documentation.
> into the book in such a way that lines wrap as shown on the screen.
> Besides, why need I reproduce on paper what the user sees on their
> terminal under normal circumstances? I am not sure that screen shots are
> of much value in helping get the message across. Why cannot I just
--
John Posada, Technical Writer
Bellcore, where Customer Satisfaction is our number one priority mailto:john -at- tdandw -dot- com mailto:jposada -at- notes -dot- cc -dot- bellcore -dot- com
My opinions are mine, and neither you nor my company can take credit for
them.
"Give a man a fish and he will eat for a day. Teach him how to fish,
and he will sit in a boat and smoke cigars all day."
"The only perfect document I ever created is still on my hard drive."
