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: page breaks From:Richard Lippincott <rlippinc -at- BEV -dot- ETN -dot- COM> Date:Wed, 11 Jan 1995 12:34:53 EST
Sherry Hall asked:
>When do you force page breaks in a technical (printed) manual?
When it makes the page layout look better. When it seems like the right thing
to do. When your gut tells you that you've reached the end of the page, but
the software doesn't agree.
There's no hard and fast rule, but I can't help remember what I learned from
an old-timer when I was starting out as a tech writer. We were working on
military manuals, each controlled by Mil-Specs. One day, he made a change
in a page, and I wasn't sure how it was justified under the specifications.
"I-Spec." he said.
"Huh?"
"I 'spect it'll look better if I do it that way." he explained.
I still use the I-Spec to this day.
Rick Lippincott
Eaton Semiconductor
Beverly, MA
rlippinc -at- bev -dot- etn -dot- com
