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.
Re: cross section vs cross-sectional - what about cross sectionedandcross sectioning
Subject:Re: cross section vs cross-sectional - what about cross sectionedandcross sectioning From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 24 Dec 2009 10:55:13 -0800
My goal is that anything I write will be quickly and easily understood by the
people I'm writing it for. If I have the rare luxury of putting a dedicated
editor into the documentation chain (the last time was about six years ago),
that person is there because I concluded that he or she could tweak whatever I
write to improve its chances of accomplishing that goal. I'll most likely spend
a little less polishing time on what I write so I have more to devote to the
"technical" part of technical writing, and let that person bring my drafts up to
whatever standard is needed. I'm not writing things to make that person's job
easier.
I have written for academic readers who would have found even slight errors in
grammar distracting, and have instructed editors to be ruthless grammar tyrants.
I have written for highly specialized readers, and have provided editors with
lists of jargon that are incomprehensible to the average person-off-the-street
but which make sense to the intended audience and should be left alone. I have
yet to write for readers who best understand hip-hop or Boontling, but if that
goal ever presents itself, I'll see to it that the English language is mangled
into whatever shape it needs to be to best reach those readers.
Gene Kim-Eng
----- Original Message -----
From: "Robert Lauriston" <robert -at- lauriston -dot- com>
> My goal is that anything I write for publication will sail smoothly
> across the desk of any copy editor or proofreader who might at some
> point enter the editorial chain. Their standards are considerably
> tighter than the average technical publications reader.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-