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: within vs. in From:Gause_Brian -at- emc -dot- com To:<Janice -dot- Gelb -at- Sun -dot- COM>, <Tammy -dot- VanBoening -at- healthlanguage -dot- com> Date:Thu, 17 Jan 2008 17:05:19 -0500
I agree with Janice. You are the writer. You have final say on words.
Brian Gause
Technical Writer
EMC Captiva
EMC Corporation
10145 Pacific Heights Blvd.
San Diego, CA 92121
P: 858-320-1202
F: 858-320-1010
E: Gause_Brian -at- emc -dot- com
-----Original Message-----
From: techwr-l-bounces+gause_brian=emc -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+gause_brian=emc -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Janice Gelb
Sent: Thursday, January 17, 2008 12:55 PM
To: Tammy Van Boening
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: within vs. in
Tammy Van Boening wrote:
> All,
>
> I can find all kinds of references for the correct use of in to vs.
> into, but nothing for within vs. in. I use "in" and I have a SME who
> insists on "within." It's not worth getting my hackles all raised for
> this issue, but for my own edification, any thoughts, references, etc?
> To me, they mean the same thing and simpler writing is better, so I
> stick with "in." (Kinda' like on or upon.)
>
I agree with your reasoning but have no source material
to provide. However, I do recommend that you emphasize
in review cover letters or conversations with reviewers
that their review should concentrate on the technical
aspects of the documentation and that you have the final
say on wording unless they can indicate that there is a
technical problem with the text as it stands.
Best of luck,
Janice
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats
or
printed documentation. Features include support for Windows Vista & 2007
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 gause_brian -at- emc -dot- com -dot-
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-
