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: What's it called? From:jarnopol <jarnopol -at- INTERACCESS -dot- COM> Date:Wed, 5 May 1999 15:38:36 -0500
===== Original Message From John Posada <jposada01 -at- YAHOO -dot- COM> =====
<snip>
The audience is probably
>novice, not PC-literate, and may never have installed
>an application before. English is not their first
>language for any of them.
<snip>
Yea, MS says to call it an "application file". And that works fine IF your
audience is PC--literate. But Jon's audience is not. And to top it off,
English is not their first language.
I'd call it "an entry in the directory" or something like that. I don't
think application file or program file is going to mean anything to the
audience unless you lay a lot of ground work first. And if this procedure is
a one-time setup, or something that's infrequently executed, I think you can
get by with being vague.
Unless you want to tip your hat to MrGates, and then, by all means, be
MS-compliant.
Cheers!!
