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.
I always create a style called "BodyKN" -- standard body text with the "keep
with next" attribute set -- and use it 1) for all paragraphs that end in a
colon, and 2) for all very short paragraphs that begin a section. That way,
all my procedure intros stay with the first step and I never end up with a
heading and two lines of text at the bottom of a page.
I also create "keep together" and "keep with next" toolbar buttons and use
them to clean up stragglies during a production edit. Yes, they work with
tables too. <g> Click... click... and the text reflows.
The beauty of these methods, unlike a hard page break, is that they allow
the document to reflow without causing any problems like blank pages or
nearly blank pages.
HTH!
-Sue Gallagher
Kevin McLauchlan writes:
> Ok, my dark secret is that I actually have used a sprinkling
> of blank paragraphs to move an awkward bit to a new page.
> Sometimes I'm in a hurry, and can't take the time to re-think
> the entire document, just to get a table to start on the next
> page, rather than split at the second of four rows (or whatever).
> I know I can apply a page-break,...
> I try to avoid having to do either, but as documents evolve,
> something is always breaking or being made to look ugly, where
> it looked fine previously.
> What are the "proper" or... failing that... most popular ways
> to mitigate what can happen when inserted (or removed) text
> causes existing items to break awkwardly or to go places you'd
> prefer they didn't? Another occasion is that you've written
> a doc with one-or-more instances of a descriptive or instructive
> paragraph on a facing page opposite an illustration... then stuff
> gets bumped and the illustration is now a page-turn away from the
> referring text.
<snip>
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-