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.
RE: earlier discussions of "user" (was: Grammar - The Gotcha Microsoft Gives)
Subject:RE: earlier discussions of "user" (was: Grammar - The Gotcha Microsoft Gives) From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:Ruth Sessions <ruthsessions03051 -at- yahoo -dot- com>, Milan DavidoviÄ <milan -dot- lists -at- gmail -dot- com>, William Sherman <bsherman77 -at- embarqmail -dot- com> Date:Fri, 9 Sep 2011 16:00:08 -0400
> -----Original Message-----
> From: Ruth Sessions
>[...]
>
> My comment earlier this afternoon on Kevin's concern was strictly aimed
> at situations like the one Kevin described, where a product has
> multiple types of users.
[...]
>
> Also, I confess to having written a lot of installation, administrator,
> and programmer guides, where I address the administrator or developer
> as "you," but need to able to talk about all the other users of the
> product (or the end users of the development process) in the third
> person.ÂOverviews of multi-user systems also need to discuss how the
> product serves multiple types of users.
That's exactly my situation.
Also, if you recall, I had User in my list. But I also had
Crypto Officer and Crypto User, as well.
For original North American customers, we already (back in the nineties)
had to deal with some customers who referred to a role as Owner, while
another group referred to the identical role as User.
Different milieu, different terms.
Then, we found some eager customers in Germany who demanded that
that role be split into two roles - Crypto Officer with full
capability to admin, configure, and alter contents of their
portion of one of our products, and Crypto User with reduced
admin scope and capability to use objects _found_ in their space,
but not alter them.
We didn't dictate to our customers. They dictated to us.
In addition, I had plenty of occasion to tell this-or-that
administrator that s/he had to do this-or-that preparation
or selection before configuring groups of.... gasp... users
of various flavo[u]rs.
-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 and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-