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.
Subject:WinHelp test plans From:Alexander Von_obert <avobert -at- TWH -dot- MSN -dot- SUB -dot- ORG> Date:Mon, 20 Nov 1995 22:42:00 +0100
Hello Ken,
* Antwort auf eine Nachricht von Ken Cox an All am 18.11.95
KC> From: kencox -at- user -dot- rose -dot- com (Ken Cox)
KC> I could use some feedback on how your organization tests its
KC> online Help (WinHelp) files.
First I produce a dummy help system. Every topic contains nothing more than
its ID. Using this file the programmers can test their help calls and I can
figure out which ID is accessed where.
During developement I add all IDs as search keywords. Some authoring tools
(e.g. the shareware program Visual Help) offer that possibility.
Another important topic is a clear, simple structure of your help system.
"Author lost in hyperspace" is much more serious than "User lost in
hyperspace".
Finally, you cannot help but test all links as thoroughly as possible -
especially when writing context-sensitive help.
Greetings from Germany,
Alexander
--
|Fidonet: Alexander Von_obert 2:2490/1719
|Internet: avobert -at- twh -dot- msn -dot- sub -dot- org
| Standard disclaimer: The views of this user are strictly his own.
| From TechWriter's Home, Nuernberg Germany
| phone 49+911+591530, FIDOnet 2:2490/1719
