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: Fields vs. Boxes, Options, etc. From:Kathleen Kuvinka <kkuvinka -at- EPICOR -dot- COM> Date:Thu, 24 Jun 1999 13:48:22 -0700
I respectfully disagree. Just because Microsoft does it one way doesn't make
it the best way. We use "fields" in our User Guides because our experience
has shown that our users know what we're talking about. However, in our
programming and administrative guides, we use the Microsoft GUI names.
If you are not writing for a Windows audience, are those terms still
appropriate? I'm only asking because I'm not sure. For example, what are the
elements called in Motif?
> -----Original Message-----
>
> Some people and some companies are so virulently anti-Microsoft that
> they design and describe their interface with the explicit
> goal of doing
> everything *not* as Microsoft does. That attitude generally hurts the
> user community.
>
> There can be good reasons for violating the guidelines. But those
> reasons are rare, and generally serve specific purposes for specific
> audiences.
>
