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: on vs in From:dski -at- CAMEONET -dot- CAMEO -dot- COM -dot- TW Date:Tue, 9 Jul 1996 13:28:56 GMT
Back when folks said and wrote what came naturally, commands and other
information were invariably described as being "in" this menu or that menu.
Then the sharpies moved in and decided that every trace of abstraction
should be removed from computer screens and descriptions of them. Everything
must look like, and be treated as, a familiar physical object.
"On the menu" started creeping into software manuals. It has gained much
ground, but its victory is far from complete. Even its perpetrators have
difficulty using it consistently. A 1991 MS-DOS manual has both "in the xxx
menu" and "on the xxx menu" (it also has "in the menu bar").
"The commands on the xxx menu" jars very badly on me. Long before Stewart
Walker posted his question, I asked friends how they felt about this usage.
They said it jars on them too.
For what it's worth, here are the results of four Alta Vista searches I just
World Wide Web Usenet
in-the-file-menu 143 hits 138 hits
on-the-file-menu 144 hits 78 hits
Dan Strychalski dski -at- cameonet -dot- cameo -dot- com -dot- tw
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-