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: Style Guidelines for pull-down menus From:"Olive, Eric" <EOlive -at- GLHEC -dot- ORG> Date:Fri, 6 Aug 1999 09:36:47 -0500
Mary,
As Sean Brierley suggested yesterday in response to a similar question, why
not keep it simple?
Choose Search>Search Menu Option.
As for standards, the previous responses to your post are on the mark; there
is not standard. Some prefer choose, others select. MS uses click. I prefer
choose because it clearly distinguishes pull-down/drop-down menus from items
one selects in a list box and buttons one clicks in a dialog box.
Eric O.
> -----Original Message-----
> From: Norman, Mary [SMTP:Mary -dot- Norman -at- WESTGROUP -dot- COM]
> Sent: Friday, August 06, 1999 9:18 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Style Guidelines for pull-down menus
>
> We are trying to get some clarity about how to document a
> pull-down menu correctly.
>
> Our doc team is currently using the following construction
> when documenting a procedure within a program:
>
> Select Search, Search Menu Option.
> So the basic construction is: Select x, y.
>
> However, another contractor suggested this: From the menu,
> choose x, y.
>
> Here's are our concerns:
>
> 1. Which one of these methods is the "standard"? If neither, can you
> offer some suggestions?
> 2. Should we use "choose" over "select" in our procedures?
>
> Thanks!
>
>
> Mary Norman
> Technical Writer
> Documentation Group/Rochester
> x6418
>
>
>