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:Reinhard Jaehnig <jaehnig_reinhard_rej-d -at- BETASYSTEMS -dot- COM> Date:Tue, 19 Jan 1999 17:42:23 UT
I don't quite understand why you think that the
function of screen shots in host documentation
is different from the function of screen shots
in Mac documentation -- maybe you want to elaborate
on that and start a new thread....
You wrote:
> Programming wants the lines to wrap and align
> as they do on the user's terminal.
Makes sense. A screen shot should look like the
screen. And to make the WHOLE thing look like
a screen, you put a (rounded) frame around it.
This is standard procedure for host documentation.
Courier might not be the best choice of font because
it does not look like the font on the screen -- but
you must definitely use a fixed pitch font.
I don't see how the 4:3 ratio of the screen is a
problem: One screen shot uses about two fifth of
your printable page and leaves you about three
fifth for instructions.
Reinhard
PS: Is it possible that you're a little bit
frustrated and feel like a time traveler having
gone back to the stone age of computing.
