RE: Old thread, hopefully new spin on "allow" v. "enable."

Subject: RE: Old thread, hopefully new spin on "allow" v. "enable."
From: MAGGIE SECARA <SECARAM -at- mainsaver -dot- com>
To: "'Ackerson, Allan'" <aackerson -at- logicon -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 8 Mar 2000 13:19:33 -0800

Lets works best for me. Avoids those messy infinitives and tends to result
in a cleaner sentence.

as in:
The Cost Wizard lets you add, edit, and delete customized pricing
structures.

Maggie Secara
secaram -at- mainsaver -dot- com



> -----Original Message-----
> From: Ackerson, Allan [SMTP:aackerson -at- logicon -dot- com]
> Sent: Tuesday, March 07, 2000 6:57 AM
> To: TECHWR-L
> Subject: RE: Old thread, hopefully new spin on "allow" v. "enable."
>
> What's wrong with "lets"?
>
> -----Original Message-----
> From: Ron Rhodes [mailto:RRhodes -at- fourthchannel -dot- com]
> Sent: Tuesday, March 07, 2000 7:43 AM
> To: TECHWR-L
> Subject: Old thread, hopefully new spin on "allow" v. "enable."
>
>
>
> Techwhirlers,
>
> I have used the word "allow" throughout my career as a tech-writers. And
> I
> really don't have a problem with it even now. But I am wondering if
> perhaps
> "enable" is better when documenting software applications.
>
> EXAMPLE:
> Not
The Cost Wizard <ALLOWS> you to add, edit, and delete customized pricing
structures.

> Instead
> The Cost Wizard <ENABLES> you to add, edit, and delete customized pricing
> structures.
>
> "Allows" just sounds too permissive, restrictive, and constraining.
> "Enables" sounds more energizing to me. But my Webster's and my Oxford
> rendered similar definitions for both words.
>




Previous by Author: Summary of Webhelp vs. HTML Help (long)
Next by Author: RE: illegal to discuss/set rates
Previous by Thread: Re: Old thread, hopefully new spin on "allow" v. "enable."
Next by Thread: Summary: Standards for Documenting XML?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads