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:Caroline Briggs <carolinp -at- Exchange -dot- Microsoft -dot- com> To:"'Humbird, LenX'" <lenx -dot- humbird -at- intel -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 23 Feb 2000 16:08:56 -0800
What's the delivery mechanism? If you're delivering content online, either
on the web or in HTML Help, your options are limited. Underlining is
obviously out, and italics are really hard to read on screen. You need to be
much more specific in your question, I think.
From: Humbird, LenX [mailto:lenx -dot- humbird -at- intel -dot- com]
Sent: Wednesday, February 23, 2000 11:05 AM
Subject: RE: When to bold
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.
Sponsored by Weisner Associates Inc., Online Information Services
Training & consulting for RoboHELP, Dreamweaver, HTML, and HTML-Based Help.
More info at http://www.weisner.com/train/ or mailto:training -at- weisner -dot- com -dot-
Sponsored by Rose Hill, Your Business and Career Coach.
"Assume Success! Live Your Passion!" Get the gist at
www.coachrose.com then call 503.629.4804 for details!
You are currently subscribed to techwr-l as: carolinp -at- EXCHANGE -dot- MICROSOFT -dot- COM
To unsubscribe send a blank email to leave-techwr-l-10492E -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.