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.
The discussion is "Top 20 Readability and Translatability Issues"
I also recommend the Global English style guide
Kathleen
On Sat, Oct 12, 2013 at 8:31 AM, Barb Philbrick <barb -at- caslonsvcs -dot- com> wrote:
> Thank you! That sounds like the type information weâre looking for.****
>
> ** **
>
> Barb****
>
> ** **
>
> *From:* Kathleen MacDowell [mailto:kathleen -dot- eamd -at- gmail -dot- com]
> *Sent:* Friday, October 11, 2013 9:57 PM
> *To:* barb -at- caslonsvcs -dot- com
>
> *Cc:* techwr-l -at- lists -dot- techwr-l -dot- com
> *Subject:* Re: Perform vs. do****
>
> ** **
>
> Barbara, I've recently seen references to a "plain" language for technical
> writing, but I can't remember where I saw it. I think it was on one of the
> LinkedIn groups, but not the Plain Language one.****
>
> I'll see if I can find the reference for you--it sounds like it might be
> more suitable for your needs. Although clarity is important, the Plain
> Language group seems a bit more directed toward law and academics (although
> I could be mistaken).****
>
> Kathleen****
>
> ** **
>
> On Fri, Oct 11, 2013 at 8:39 PM, Barb <caslon -at- windstream -dot- net> wrote:****
>
> If you are a true glutton for punishment, you can download the Reference
> Manual and see the examples in context.
>
>http://www.keithley.com/data?asset=57633
>
> The autozero example is on page 136.
>
> The User's Manual is the one that tends to use the ".... perform the
> following steps" format:
>http://www.keithley.com/data?asset=57632
>
>
> Barb****
>
>
> -----Original Message-----
> From: techwr-l-bounces+caslon=windstream -dot- net -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+caslon=windstream -dot- net -at- lists -dot- techwr-l -dot- com] On
> Behalf
> Of Barb
> Sent: Friday, October 11, 2013 9:00 PM
> To: 'Milan Davidovic'
> Cc: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Perform vs. do
>
> We've been trying to move to more ESL-friendly language, plus
> plainlanguage.gov recommends "do" over "perform" (but with no
> explanation).
> We've been trying to use "do" instead, but it sounds strange. Because it
> sounds strange, our department members have been sporadic about using it.
> This in turn has resulted in inconsistent usage, so we're trying to
> establish rules around when to and not to use "perform" and "do" (or,
> ideally, use one of them consistently).
>
> I've found that sometimes there's a grammatical reason when things sound
> strange (rules we've internalized but forgotten). In this case, I'm not
> finding one.
>
>
> Barb
>
> -----Original Message-----
> From: Milan Davidovic [mailto:milan -dot- lists -at- gmail -dot- com]
> Sent: Friday, October 11, 2013 4:00 PM
> To: Barbara Philbrick
> Cc: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: Perform vs. do
>
> On Fri, Oct 11, 2013 at 9:07 AM, Barbara Philbrick <caslon -at- windstream -dot- net>
> wrote:
> > Our writing group is trying to decide if we should start using "do"
> instead of "perform" for lead-in statements to procedures.
>
> How did this come up?
>
> --Milan Davidovic
>
> Sent from my Yost 10
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^****
>
> You are currently subscribed to TECHWR-L as caslon -at- windstream -dot- net -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
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as kathleen -dot- eamd -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****
>
>
>
>
> --
> Kathleen MacDowell
> kathleen -dot- eamd -at- gmail -dot- com****
>
--
Kathleen MacDowell
kathleen -dot- eamd -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
