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.
I almost always bold GUI elements because it makes the text easier to
follow. It can often shorten the text because there usually isn't a need to
identify the type of element, as in "click <bold>OK", rather than "click the
OK button".
-Svi Ben-Elya-
----- Original Message -----
From: "David Chinell" <dchinell -at- msn -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Friday, July 11, 2003 5:35 PM
Subject: Typographical treatment of GUI components
>
> Gang:
>
> Does anyone have any information to support (or not) bolding
> GUI component names in printed reference manuals or Help
> systems?
>
> Our shop follows the MS Manual of Style with a few
> exceptions. One exception being that we don't give GUI
> components (commands on menus and buttons, window and dialog
> box titles, etc.) any special typographic treatment. In
> other words, no bolding. We do replicate the spelling and
> casing of these components.
>
> Years ago, we decided that the extra work required didn't
> create a proportional value. We also felt that the resulting
> text looked blotchy and was less readable.
>
> 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.
>
> Bear
>
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.
