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.
This sounds to me like a perfect case for a style guide. You can start
by organizing it into the categories you have already listed. If you
also put it in an online format, make it searchable and easy to access,
your "writer" may be more likely to refer to it, rather than repeating
the same mistakes.
I agree with Geoff, too. In my experience, most authors really don't
care to learn to write properly, or where to correctly place the comma
in a sentence. That's what editors are for (if the company employs one)
or worst case, they just let the document go out the door poorly
written. I've seen several instruction pamphlets for home equipment and
self-assembly projects that prove that point.
Hope that helps.
Claire Conant
Technical Editor
Digeo, Inc.
Kirkland, WA
Karen wrote: I would also like to summarize the
edits to give him a list of issues to work on for the
next report. (My boss does not want to see me
correcting the same mistakes and wants to see the
co-worker learn from this experience.)
I've created a form with the following subsections:
Punctuation
Numbers
Consistency
Grammar
Word Choice
Would anyone care to share their approach?
Also, any PC term to use to convey sloppy or careless
work? (The language barrier really wasn't an issue in
this work, but there were a lot of careless mistakes.)
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-