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.
>Yesterday in a meeting I was told: "There is NO editorial process.
You're it. You're writer, editor, (Document dept.) project manager. Make
it happen. Next."
>HELP! What are the traps? What should I do? What should I not do? Any
tips gladly accepted. Any books anyone can recommend.
I've always been in that situation.
Get someone else to read your texts once you have edited them.
One ploy is to ask a coder to read them to check that the content is
"functionally" correct (often they will point out other mistakes as well).
If you're really stuck - try reading your texts backwards - an old
copyediting trick (so I'm told). You often find those silly typos you missed
reading it the usual way (although it can hurt the head after a few pages).
Don't panic - there are many web resources such as dictionaries, grammar
guides, and style guides. There are even document management guides. Try a
web search.
Try joining copyediting and DTP newsgroups and email lists.
_______________________________________________
The views expressed in this communication
are my own and do not represent the views
of my employer or any other third party.
_______________________________________________
Michael Toogood, Technical Author, miket -at- datent -dot- com
DAT Enterprises Limited, Microsoft MCSP Partner
Phone: +44(0)870 606 5550 Fax: +44(0)1580 830044
_______________ www.datent.com ________________
