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: style guidelines From:Stan Brown <stbrown -at- NACS -dot- NET> Date:Sat, 2 Mar 1996 20:55:54 -0500
Responding to a question from Ruth Glaser <ruthg -at- goretek -dot- com>, quoth
Ian Macdonald <imacd -at- PC -dot- JARING -dot- MY>:
Subject: Re: style guidelines
>>Does anyone have an opinion/rule of thumb regarding a maximum number of
>>paragraph tags/fonts to use in a document?
>Using fonts: in general no more than two in a document. All headings should
>use the same font with size and style attributes to show levels, all body
>text elements (body text, lists, etc.) should use the same font. Special
>fonts can be used in special situations, for example, courier to format
>actual data entry, or code examples.
Sound advice, but I'd like to suggest an even stricter standard. A
heading should vary no more than one element from the next less
significant heading level (or from text). For instance, if the text is
11-point Times, the lowest-level heading might be 11-point Times
italic, or 11-point Times bold; but it should not be 12-point Times
bold or italic. Vary size or emphasis, but not both.
You can also position headings in various ways to handle different
levels without creating a Christmas-tree effect.
This advice is adapted from Robert Bringhurst's _The Elements of
Typographic Style_, a terrific book in my opinion. He discussed this
topic at length, and gives two different extensive examples on pages
64 and 65 of his book.
Regards,
Stan Brown, Oak Road Systems Cleveland, Ohio USA +1 216 371-0043
email: stbrown -at- nacs -dot- net Web: http://www.nacs.net/~stbrown