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: Your typographical conventions From:"Chinell, David F \(GE Indust, Security\)" <David -dot- Chinell -at- GE -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 8 Mar 2007 17:33:33 -0500
Nancy:
I follow the Sun style guide for typographical treatment of GUI components. No special typographical treatment. (Sun and the CMS support your use of italics for references to the titles of other works.)
My preferred font set might be:
Sans serif for headings and display text (headers, footers, tabular material, captions, callouts)
Serif for body text
Monopitch for user entries and system messages
Italics for emphasis and titles of works.
You didn't mention URLs and web pages and the like. Sun sets them in monopitch, which makes the same kind of sense as it does for user entries and system messages -- it shows the spacing and punctuation very clearly. But I'm still not comfy with this. Neither do I like italicizing URLs -- suggested by the MS MoS -- as this seems to obscure them.
When there's a chance of confusing English-like GUI labels with supportive text, either changing the labels to I-caps or setting the label in double quotes is fine with me, provided it's consistent across a product library.
This discussion comes up from time to time, and I feel I'm in a minority about GUI components. As a bold experiment, why not try doing without while you're drafting stuff up. You can always add special typography later. If you do, please use specific character styles for GUI elements, rather than just bolding labels.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-