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[2]: Blank spaces From:Joyce Flaherty <flahertj -at- SMTPGW -dot- LIEBERT -dot- COM> Date:Wed, 1 Mar 1995 10:16:55 EST
Your question has to do specifically with separating text from
graphics. It has to do generally with judicious and consistent
use of white space (input from output, process from rationale,
and so forth).
Whatever you decide, make it a standard. We use three lines at
the top, one between the graphic/table and its title, and three
at the bottom. This evolved from a very old UNIX standard, which
was equivalent to advance-down-0.5".
Sometimes a bad standard is better than no standard at all. If
you have the standard, you can implement same with macros and
tags. You can always update the standard if you find you really
didn't get it quite right. Then there is the "deviation from
standard" mechanism, but that's another can of worms.
Good morning! We CTRL [ENTER] (equal to one space) after the text, import
the graphic, and hard [ENTER] after the graphic. The effect is one space
before and two spaces or a paragraph space after.
On Tue, 28 Feb 1995, David Dubin wrote:
> How do most of you handle spacing between text and graphics, text and tables,
> and between text blocks within a document?
