Re: The Bible in Tech Comm
Haven't you ever done a gap analysis of a technical document? Does
doing one negate the fact that it is still a technical document?
Most of the documents we create have gaps in them somewhere.
Usually, they're due to compromises we were forced to make for
time and/or budget. That doesn't negate the fact that they're still
technical documents, but I wouldn't present them as "models for
ideal technical communication."
Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l
Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.
RE: The Bible in Tech Comm: From: John Posada
Previous by Author:
Re: is "technologies" a word?
Next by Author: Re: Writing Samples and Confidential/Internal Use Publications
Previous by Thread: RE: The Bible in Tech Comm
Next by Thread: Re: The Bible in Tech Comm
Search our Technical Writing Archives & Magazine