RE: Best Practices in Indicating Versions

Subject: RE: Best Practices in Indicating Versions
From: "Lorraine Kiewiet" <Lorraine -dot- Kiewiet -at- mullinconsulting -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Fri, 25 Jul 2003 11:41:46 -0700

We produce documents for both engineering and for end-users. We use
Revision Tables in the front of both documents, but I format the one for
end-users as Hidden Text. That was, we can track drafts, but then when
we go to print for the users, they don't see the unnecessary


There's not much to be said about the period except that most writers
don't reach it soon enough. - William Zinsser


sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required!

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: Acrobat to Framemaker 7 - is it possible?
Next by Author: RE: Typographical treatment of GUI components
Previous by Thread: Re: Best Practices in Indicating Versions
Next by Thread: Are any of you using SCORM?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads