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: Subject: RE: When to bold From:Henry Vandelinde <vandelinde -at- wordtek -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 23 Feb 2000 14:18:31 -0500
My opinion is
>bolding commands is always useful. A more experienced user does not have to
>read all text in order to find useful information. They can scan for the
>bolded items and get on track. A less experienced user knows a bolded item
>is a necessary command in the procedure. Anyhow, the driver for any
>documentation is not the writer or the developer. It is the end-user and
>what will facilitate their use of your documentation.
I agree. I always bold direct action commands and change the font ever so
slightly to break the reading rhythm and to emphasize the action.
Henry Vandelinde, Ph.D.
vandelinde -at- wordtek -dot- com