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: Typographical treatment of GUI components From:Michael West <mbwest -at- bigpond -dot- net -dot- au> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 14 Jul 2003 09:40:16 +1000
> This decision was lately challenged by one of our
> engineering managers. That's why I'm asking if anyone has
> any information on whether it's worthwhile or not. I'd like
> some support for our decision, or to have my eyes opened to
> the value of bolding these names.
See if this helps.
Just to see whether I still subscribe to the
convention of bolding GUI items in instructional
material, I opened a few random topics in the
Help file of my mail reader (OE 6).
There, the convention is used, and I find that
it does help. Given a set of well-written instructions,
I can (if I want) simply scan down the list of instructions
without actually reading, picking out the boldface
words. Voila! What it gives me is the bare-bones sequence
of mouse clicks or keystrokes that I need to execute.
A real time-saver, in my view. It would be much harder to
pick out the command names and menu names without
the boldface type.
--
Mike West
Melbourne, Australia
ANNOUNCING ROBOHELP STUDIO
Create professional Help systems that feature interactive tutorials and
demos with all new RoboHelp Studio. More at http://www.ehelp.com/techwr-l2
Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -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.