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.
> Hi,
>
> if you just exchange "will be" by "is" or "are" it has no direct influence
> on passiv or active voice.
>
> I am here. I will be here. - active
> The letter will be sent. The letter is sent. - passive.
>
> You will have to restructure the sentence.
> To avoid passive voice has advantage in many sentences, especially in user
> manuals and in specifications.
> Passive voice often hides what or who is doing the action. This may cause
> problems.
>
> Otherwise, passive voice can have an advantage if you want to topicalice
> something.
>
> Compare:
>
> 1. The system fills the Address field using the address information from
> the main customer. (active)
> 2. The address field will be filled with the address information from the
> main customer. (passive)
>
> 2. is shorter and you can read at first about the topic.
> In 1. you have to read a part which usually is not essential. But it can
> be. If both the user and the system can fill the field, 1. will hide this
> information.
>
> I would look into the style guide to find how to write it.
> If there is no style guide I would recommend to write one. It helps all to
> find answers when to avoid passive and how to write it.
>
> In my experience passive is dangerous for the programmers, if they
> mismatch the actor with the receiver.
>
> Best regards
> Bernd
>
>
>
> Usha Manoj <usha -dot- manoj07 -at- gmail -dot- com> schrieb am 11:50 Montag, 7.August
> 2017:
>
>
> Dear All,
> With regards to active and passive, I have a query and may be you can throw
> some light on it.
> I have usually encountered this problem when I drafted RFP or RFI.
> Technical writing emphasizes on using active voice. However, in case of
> proposals, where you talk about performing a particular action in case you
> win the deal, the text is usually in future tense, for example, Company X
> will be responsible to meet the SLA targets. How best can we avoid using
> "will be" in the sentence. I have tried replacing it with "is" or "are"
> depending on the context, but doesn't work in all cases. Please advise.
> Regards
> Usha
>
> On 05-Aug-2017 8:04 PM, "Karin Matchett" <wordcraft -at- karinmatchett -dot- com>
> wrote:
>
> > I agree. In addition to needing a form of "to be," it needs an
> explicit
> > subject.
> > The question of active vs. passive doesn't even apply to this sentence
> > because it's a command, which only has an implied subject of "you." My
> > sense of why the question of passive voice is coming up is that there
> > are different ways to phrase this sentence that are differently
> > direct/indirect/confusing/obtuse/imprecise. These have a similar feel
> > to active/passive, but they're not the same thing -- there's no
> > overlap.
> > Karin
> >
> > On 8/4/2017 7:23 PM, Robert Lauriston wrote:
> >
> > Since the subject specifically refers to active vs. passive, I'll
> > repeat what I said in that long thread, only correctly (it has been a
> > long and busy day):
> >
> > A phrase in passive voice has to have a form of the verb "be" and a
> > past participle. There's more to it, but without those, it's not
> > passive voice.
> >
> > Garner's "Modern American Usage" has good explanations for things like
> > that.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Visit TechWhirl for the latest on content technology, content strategy
> and
> > conte
> > nt development | [1]http://techwhirl.com
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > References
> >
> > 1. http://techwhirl.com/
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Visit TechWhirl for the latest on content technology, content strategy
> and
> > content development | http://techwhirl.com
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You are currently subscribed to TECHWR-L as usha -dot- manoj07 -at- gmail -dot- com -dot-
> >
> > To unsubscribe send a blank email to
> > techwr-l-leave -at- lists -dot- techwr-l -dot- com
> >
> >
> > Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
> > http://www.techwhirl.com/email-discussion-groups/ for more resources and
> > info.
> >
> > Looking for articles on Technical Communications? Head over to our
> online
> > magazine at http://techwhirl.com
> >
> > Looking for the archived Techwr-l email discussions? Search our public
> > email archives @ http://techwr-l.com/archives
>
> >
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as hutschi -at- yahoo -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
