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.
Re: New Chapter On Right/Leave Left Page Blank -Reply
Subject:Re: New Chapter On Right/Leave Left Page Blank -Reply From:"Parks, Beverly" <ParksB -at- EMH1 -dot- HQISEC -dot- ARMY -dot- MIL> Date:Wed, 26 May 1999 14:43:52 -0700
I agree. But that's the only valid justification I've heard so far.
Distribution of documentation in binders also seems to be a fading method of
publishing, though I'm sure there are some industries that still use it
heavily, such as heavy machinery or something. Heck, hard copy documentation
- period - is a fading method of publishing!
Bev Parks
> -----Original Message-----
> From: Nora Merhar [SMTP:nmerhar -at- CHARLESINDUSTRIES -dot- COM]
> Actually, I can think of a very good reason to force each chapter to end
> on an even
> page. If you want to use a modular documentation scheme, in which you can
> pull
> individual chapters and add them to a book, it's certainly easier if each
> chapter
> is its own self-contained unit.
>
> It also works better if you have to change a chapter and provide change
> pages to a
> customer. If the change causes a repagination, at least you would only
> have to
> replace the rest of that chapter, instead of that chapter and all the
> following
> chapters.
>
>