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.
They're "choices". Since there's no earthly hope of getting them to
refer to parallel or equivalent things/items/whatevers, why not avoid the
issue?
> -----Original Message-----
> From: John Bell <jbell -at- PARAGREN -dot- COM>
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
> Date: Tuesday, 01 September, 1998 11:38 AM
> Subject: Menu terminology
>
>
> >I have a new writer who brought an interesting question to me.
> >What do you call the items on a menu?
> >My initial reaction was "Commands", because that's
> >what the Apple Style Guide and the Microsoft Manual
> >of Style calls them.
> >
> >Her reaction is that commands should be verbs, and
> >most of the items on our menus are not verbs but the
> >names of windows (List Field Builder, User Setup,
> >and so on). We even have a few options where you
> >turn on/off checkmarks on the menu (Show Tooltips,
> >Open Library on Start, and so on).
> >
> >Now I find myself doubting the universal label of
> >"Command". Should we differentiate between commands,
> >window names, and options? If so, what should we call
> >them?
> >
> >Thanks!
> >--- John Bell
> > jbell -at- paragren -dot- com
> >
> >From ??? -at- ??? Sun Jan 00 00:00:00 0000
> ==
> >
> >
> >
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> =
>
>
