Subject: RE: When to bold

Subject: Subject: RE: When to bold
From: Alice Kirk <AKirk -at- URSI -dot- com>
To: "'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 23 Feb 2000 10:53:09 -0600


From: "Murrell, Thomas" <TMurrell -at- alldata -dot- net>
Date: Tue, 22 Feb 2000 15:27:40 -0500
X-Message-Number: 50

> From: Susan Arbing[SMTP:Sarbing -at- ITCCanada -dot- com]
>
> I'm in the midst of a discussing about bolding menu commands in
> procedures.
>
> 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.

In reading responses to this, it seems the primary focus has been lost on
Techwriter vs. developer and who is going to 'call the shots' on
documentation.
The primary focus is what will help the user of the document. 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.
Alice Kirk
QA Manager
United Recovery Systems, Inc.
akirk -at- ursi -dot- com




Previous by Author: : tracking software
Next by Author: HTML Information Types in WWP
Previous by Thread: Updating copyright information?
Next by Thread: Re: Subject: RE: When to bold


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads