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.
Have you tried the The Windows Interface Guidelines for Software Design?
Microsoft Press. ISBN 1-55615-679-0.
Home of RoboNEWS(tm), the award-winning unofficial RoboHELP Newsletter
anthrobytes -at- anthrobytes -dot- com
Check out www.winhelp.net!
From: Tom Hinds <THinds -at- TIMESLIPS -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Thursday, 23 July, 1998 9:09 PM
Subject: Field Labels
>Does anyone know of a good reference that states rules (standards) of GUI
>I am interested in rules that specifically deal with the labeling of
>My team is midway through a project. We are writing a manual and help files
>for a group of applications.
>In some of the dialog boxes there are fields that are not labeled.
>For example, one dialog box contains a set of columns. Some columns contain
>a heading; some do not.
>To make it easier on the writer (and eventually the user of the product) I
>insist that all fields are labeled.
>I would like to show the developers a rule or two supporting my demands.
>This would be much easier (and also better for work politics, although
>less effective) than applying a sleeper hold or figure-four leg-lock until
>the head of the development team submits to the field naming scheme I
>If you can, please forward any such rules that you find.
>Thanks in advance for any help you can provide.