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:[Fwd: Re: What's it called?] From:Jeff Wiggin <wiggin -at- RPI -dot- EDU> Date:Wed, 5 May 1999 16:43:13 -0400
Apologies -- this was supposed to have gone to the list, and not just
John.
-------- Original Message --------
Subject: Re: What's it called?
Date: Wed, 05 May 1999 14:48:56 -0400
From: Jeff Wiggin <wiggin -at- rpi -dot- edu>
To: John Posada <jposada01 -at- YAHOO -dot- COM>
References: <199905051821 -dot- OAA40994 -at- mail1 -dot- its -dot- rpi -dot- edu>
John Posada wrote:
>
> My question...what do you call an .exe file that is
> not the main executable.
John -
Considering that your users are rank computer novices and non-native
speakers of English, I would strive to be as basic as possible:
"You will find a file named mdac_tpe.exe"
Do they need to know that an .exe file is a *program* file to complete
the task successfully? Or will identical terminology potentially only
cause confusion and interfere with their efforts to install the main
program/application? I can envision novices installing "mdac_tpe.exe"
and thinking they have installed the main application. Then they'd
really be confused!
And, MS Style Guide notwithstanding, "mdac_tpe.exe" -is- a file, so you
are not being inaccurate. This case is about your users.
