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: Blank Pages and Numbering From:DURL <durl -at- BUFFNET -dot- NET> Date:Fri, 1 May 1998 08:33:39 -0400
One local pubs manager solves the problem by formatting so that no
page *is* left blank. This often works...add a table, break a procedure so
that it continues onto the blank page...
"Well-written" is a tad tough to define, demonstrate, and prove,
and I'd just as soon avoid the problem of saying, "Write this so people
know it's the end!"
I've also used dingbats--those fonts in dingbat were apparently
named for the publishing convention of using little designs at the end of
articles. You'll see them in most magazines. I use end-of-procedure
markers (three checkmarks, or whatever) to denote end of text.
Mary
Mary Durlak Erie Documentation Inc.
East Aurora, New York (near Buffalo)
durl -at- buffnet -dot- net
On Thu, 30 Apr 1998, Beth Agnew wrote:
> I think if the content is well-written, users won't be likely to feel that
> something is missing. The last paragraph on the last page of a chapter or
> section should sum up or neatly finish what has been said. That's allowed,
> and desirable, even in a technical manual.
>
