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.
> -----Original Message-----
> From: Brierley, Sean [SMTP:Brierley -at- Quodata -dot- Com]
> Sent: Friday, October 01, 1999 10:45 AM
> To: TECHWR-L
> Subject: Thoughs on reproducing what's on screen
>
>
> The development team wants, included in the book, the first page of each
> of
> the 35 reports, so the customer can browse the book and look at the
> reports
> to see what information each includes.
>
> Instead, I prefer to add a short, bulletted, admittedly
> unexciting text list of key information each report provides. Am I
> unreasonable in this?
[Lizak Kristin]
Sean, just wanted to let you know that this is not unheard of. Our
users wanted an example of each of the reports in the book - so I created an
Appendix that not only has the first page of each of report, but also
samples of maps that they can generate. In addition, I have a reports
chapter that has a sub-section detailing each report. Within in of these
section, there is a screen capture of what the report looks like in the
program for each (it differs than the printed product). We figure that if a
few users would find this helpful, there's a good chance a lot more will
also. I don't think you can give people too much information. If they are
not interested, I can assume that they will just ignore the Appendix.
