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.
Likewise, the developer
> needs to leave the grammar to you and review for content only. Clear?
> Vince Putman | Avoid polishing the fire truck
. . .
Why this insistance that someone could ever read for "content only" ?
What about if you left a coffee stain on a draft that made part of it
illegible? You want to cow your readers so that they don't mention this
difficulty to you, but press on regardless and try to decipher the
document without being able to really understand the parts that you
unintentionally obscured? Unless they're experts on coffee,
I take your point that pages and pages of precise, well-meaning, and
totally screwy grammar and punctuation edits would drive me crazy and
be a waste of everyone's time, but the trouble is, I've never seen this!
In ten years of tech writing I've had a few complaints about
reviewers, but they haven't had to do with illiterates trying to teach me
English. Maybe it's because I try to make my drafts fairly clean to
begin with; maybe not.
Anyway, if you really have to deal with that kind of endless edits, you
have my sympathy, but I doubt you're going to change the way a lot of
us work, or modify the desire of readers (ESL or not) to make something
Corte Madera, California
atc -at- corte-madera -dot- geoquest -dot- slb -dot- com