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.
I think if you took a role-based approach to your documentation, then you
avoid the awkwardness of the terminology. The customer's computer is not a
client when it is performing the role of a server. You do not need to
document every role that a physical piece of equipment performs when you
document a specific set of operations. You need to document the _specific_
set of operations whether they are those of a client *or* a server.
There are times when your customer's computer can be a desktop workstation,
but you would not state, "Go to the workstation to administer the
workstation's server and enter login information to access Company X
server." You also do not need to account for how your customers use your
product, whether they dedicate clients and servers or combine clients and
servers on one machine. It is not your job to know what they will do.
Document the customer's server operations in one manual, the customer's
client operations in another manual, and whatever other sets of operations
you have in other manuals, but keep the roles (client and server) separated.
Lauren
> -----Original Message-----
> From: techwr-l-bounces+lauren=writeco -dot- net -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+lauren=writeco -dot- net -at- lists -dot- techwr-l -dot- com
> ] On Behalf Of McLauchlan, Kevin
> Sent: Thursday, November 15, 2007 9:20 AM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: terminology that swings both ways
>
> What do y'all do with widely used terms like "client" and
> "server" that
> can rightfully be used interchangeably (yet perfectly
> accurately either
> way) in the same sentence? How to minimize the ambiguity without
> maximizing wordiness and if/thens?
>
>
>
> For example, in a few places in my Help, I have to talk about
> configuration and interactions among our product, our customer's
> computer, and _their_ customers' computers. Our product is a server to
> the client... the customer's computer, and it might also be a
> server to
> the customer's customers' client computers... or our customer
> might use
> our product as a server but act as a server to their customer
> clients...
> or... there could be a situation where our customer's
> computer serves a
> certain type of operation to their customers, but hands off a
> subset of
> those operations that our product does best. So, it's not as simple as
> just putting categorical adjectives in front of the various possible
> occurrences of "client" or "server", since those might switch in the
> middle of a thought.
>
>
>
> Don't get me started on "host"....
>
>
>
> Sentences could become a little awkward.
>
>
>
> Is there a standard approach? A best practice?
>
>
>
> Thanks,
>
>
>
> Kevin
>
>
> The information contained in this electronic mail
> transmission may be privileged and confidential, and
> therefore, protected from disclosure. If you have received
> this communication in error, please notify us immediately by
> replying to this message and deleting it from your computer
> without copying or disclosing it.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create HTML or Microsoft Word content and convert to Help
> file formats or
> printed documentation. Features include support for Windows
> Vista & 2007
> Microsoft Office, team authoring, plus more.
>http://www.DocToHelp.com/TechwrlList
>
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
>
> ---
> You are currently subscribed to TECHWR-L as lauren -at- writeco -dot- net -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/lauren%40wr
> iteco.net
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-