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.
Good morning and my apologies if this reply comes too late to be of much
use. I'm on the digest.
I just finished a lengthy Readme project and (still) suffering through
the same headaches you described in your post. What bugs me is that we
have a fairly strong process that we simply cannot enforce.
We're using AuthorIT to produce readme docs in HTML that's posted daily
to a network site and picked up automatically by the build process.
Development folks open issues to report changes or corrections needed
and I am responsible for managing that queue. Additionally, a Word
version is posted on another network share for non-Dev folks to
They are supposed to work directly in the Word file, using Track
Changes, but invariably end up making local copies of the file and
emailing it to me.
Here's what I ended up doing before I jumped from the roof of my
building. It ain't pretty, but it works.
>From day 1 of the effort, I took a snapshot of the AIT source published
to Word and stored that on my local drive. Each and every issue, email
or change request that comes my way...I make in two places - to the Word
file and in the original AIT source. Yes, it's double the work. However,
in the Word file, I also note the issue number, the email date and who
sent it, etc. with Track Changes.
This method has been invaluable to me because no sooner do I make a
change when another reviewer is asking me why something was deleted. I
can simply look up the initiator, direct the offended party their way
and let them duke it out until they're both happy.
Interestingly enough, it does not take much time to do this, which
surprised me. I really thought, "Wow. Double work, twice the time." But
as I write in AIT, I merely copy and paste the change into the Word
file, note the source information and save. I can publish a clean copy
in HTML or Word any time I need to from AIT because there is no
'garbage' there. It's all in my local word copy.
Like I said, it's not elegant. If anyone comes back with a cleaner
suggestion, please send it my way... :)
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-