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.
> I'm responsible for choosing a help-authoring tool for our first MS
> Windows product. After a two-month evaluation, I recommended RoboHelp
> because it fits best with our authoring/development environment.
> However, my department's direction is to _reduce_ the number of
> tools; currently, we have a word processor, a desktop publishing
> package, a graphics package, a screen shot package...and so on.
> [...] is it possible (or even practical) to produce an .rtf file in
> FrameMaker that the Windows help compiler will accept?
Dunno, but you may want to look at Bristol Technology's Bridge
product. Bristol sells a nifty hypertext help application (called,
appropriately enough, Hyperhelp) that takes Frame files OR MS-Windows
Help files and converts them to a proprietary format. They also have
Bridge, which apparently converts Hyperhelp files to MS-Windows help
files. You might want to e-mail infoquest -at- bristol -dot- com for details,
or ftp some info files and demos from bristol.com.
