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.
Then get whoever is putting the pressure on to pay for you trip to
talk to the author face-to-face, alongside the piece of kit...
> On 12 November 2013 at 23:42 TechWhirl Community Forums
> <no-reply -dot- 38b4n -at- zapiermail -dot- com> wrote:
>
>
> A message from TechWhirl Community Forums
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> I'm editing a short article intended for dissemination to our
> customer base. The document was written by an engineer in a
> non-English speaking country. This document is a mess. I've been in
> the telecom industry for 20 years, but I have no idea what this guy
> is trying to say. I've sent it back, I've asked another engineer to
> review it, but I keep getting the same gibberish back. There's no
> one to escalate this to, and I am being pressured to distribute this
> because customers are asking for it. But it is, honest to Pete,
> completely incomprehensible even to other engineers.
>
> Has anyone else dealt with this? I should say that I speak and read
> several languages, have been a technical writer and editor for
> twenty years, and routinely encounter and deal with folks whose
> primary language is other than English. I have every possible
> sympathy for someone who is trying to write a technical paper in
> another language. But this is simple unacceptable. Suggestions?
>
> Thanks.
>
> Munchkyn
>
>
>
>
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
> Learn more: http://bit.ly/ZeOZeQ
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> --
> Reply to this email directly or follow the link below to check it
> out:
>http://community.techwhirl.com/discussion/1065/authors-who-cannot-write
>
>
> Please reply to all for this message to be delivered to the Forums
> and Email Group.
>
> ---------------------------------------------------------------------------
> Visit this link to stop these emails: http://zpr.io/6d4n
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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 ant -at- ant-davey -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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
