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: When to bold From:"Humbird, LenX" <lenx -dot- humbird -at- intel -dot- com> To:"'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 23 Feb 2000 11:05:06 -0800
Perhaps this is an antique way to address the matter. I believe you should
reserve embolding for text which is most important. IMHO, bold text catches
the eye faster than italic, underline, spacing, changes in typeface, boxing,
shading, special characters, and even changes in type size. (There are
exceptions, of course; combinations of the above mentioned attributes; some
fonts have very heavy bold faces.) If the reader is skimming, chances are
you want that person to see the important information (such as loss of data,
hazard, etc.), and pass over the details (such as command syntax). So unless
the text is important, use some other style to set it apart.
> From: Susan Arbing[SMTP:Sarbing -at- ITCCanada -dot- com]
> I'm in the midst of a discussing about bolding menu commands in
> I am writing a manual for a software program. My QA person is suggesting
> that I bold the commands. For example, in the step "Click Save" save
> would be bolded.
I'm not inclined toward bolding. I think bolding is more useful
> intraining materials and tutorials where a user is being introduced to a
> product and needs a lot of emphasis and reinforcement.