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: there is vs. there's From:"Zen C" <zenizenc -at- gmail -dot- com> To:"techwr-l List" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 16 Apr 2008 16:59:53 -0400
Do you recommend following a formal style when writing a SOP for a company
or informal (meaning using the spoken style of English)?
The reason I am asking is, I am checking a SOP that is written using the
"speaking style" of English and not sure if I should provide my feedback
saying "use writing style." There is not set standards the company follows,
this is the first SOP the company has documented.
On Wed, Apr 16, 2008 at 4:45 PM, Fred Ridder <docudoc -at- hotmail -dot- com> wrote:
> As always, it depends on what style guide you follow. Many (maybe
> most) style guides say to avoid contractions in formal writing. Period.
>
> The only possible benefits of contracting this phrase are to make your
> style less formal (which is perhaps not good), and to save exactly one
> character. On the downside, it possibly compromises readability a little
> bit (particularly for ESL readers, who often have problems with English
> contractions), and almost certainly causes issues in translation to some
> languages. So what's the point in doing it?
>
> -FR
>
> > Date: Wed, 16 Apr 2008 16:33:40 -0400
> > From: zenizenc -at- gmail -dot- com
> > To: techwr-l -at- lists -dot- techwr-l -dot- com
> > Subject: there is vs. there's
> >
> > Hi,
> >
> > Is there a rule about using "there is/there's" in Technical Writing? or
> is
> > it a standard followed based on preference.
> >
> > Zen
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > 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 docudoc -at- hotmail -dot- com -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/docudoc%40hotmail.com
> >
> >
> > 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.
> >
>
>
> ------------------------------
> Use video conversation to talk face-to-face with Windows Live Messenger. Get
> started!<http://www.windowslive.com/messenger/connect_your_way.html?ocid=TXT_TAGLM_WL_Refresh_messenger_video_042008>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-