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.
Deborah Snavely, thanks for the helpful Dreamweaver feedback. Please clear this up: are you saying you built the project in InterHelp in order to create the TOC and index? Then you simply replaced your HTML and CSS files (since they were mucked with by ForeHelp) before releasing the help with, I assume, your Web app? This suggests that none of the tags added by ForeHelp were needed for the TOC or index to work--could that be correct?
PS - You signed-off with "YMMV;" -- Your Mileage May Vary?
>>Has anyone used the PC versions of Adobe GoLive or Macromedia
>>Dreamweaver for help system creation/maintenance? To what extent were
>>you satisfied/disappointed with either tool?
>
>I've used Macromedia Dreamweaver 1.2 on Windows NT 4.0 to work on a *small*
>suite of browser (IE & Netscape) help files. I like its site view, and very
>much appreciate its raw HTML editing capability.
>
>Most recently I used ForeHelp to do a quick-and-dirty upgrade to the suite
>of files so that it looked the same across all files. Unfortunately,
>ForeHelp 2000 has no way to tell even its Interhelp function not to embed
>JavaScript references (I miss ForeHelp 1999's vanilla HTML 3.2 setting! I
>was expecting 2000 to have an HTML 4.0 setting among its options, doggone
>it.) Got my major editing done in ForeHelp, built the project, and lifted
>the HTML and CSS files only for the actual object files that went into the
>product. . . .
>
>YMMV,
>
>Deborah Snavely, Document Architect, Aurigin Systems, Inc.