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.
Unless I am mistaken, the lady's answer is "no"--no matter what she
means by "track history."
As a compiled help file, there are only limited abilities of a .chm.
Any sort of active "tracking" would need to be at the application
level--although some sort of history-of-use capture would be useful
indeed for seeing what parts of a product were most often causing help
system access.
If anyone knows of a method of doing this within the helpfile
methodology, I shall be very interested in learning of it.
David
On Fri, 29 Oct 2004 15:00:46 -0400, TechComm Dood
<techcommdood -at- gmail -dot- com> wrote:
>
> What do you mean by "track history"?
ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
---
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.
