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:Re: Java Help or Something Else? From:"Wing, Michael J" <mjwing -at- INGR -dot- COM> Date:Fri, 5 Feb 1999 09:49:51 -0600
Why not deliver the help as a collection of straight HTML files. Tie them
together from a default page or use a framed page with navigation in one
frame and selected pages in the other. If you keep formatting to a minimum
and use default fonts/settings, then the files should be viewable on a
variety of browsers
Later, you can straight HTML pages as source files to create HTMLHelp,
RoboHTML help, or whatever without having to reformat the source.
> I understand their concerns. But, I am in a time crunch. And the more time
> we spend on these issues, the less I have to work on CONTENT! (Sound
> familiar to anyone?) The way I see it: there will probably have to be some
> compromises and "throw away work" because JavaHelp will not be ready in
> Does anyone have any suggestions? I work with a great dev team, and we
> well together. So, any suggestions that could help either side of this
> equation are much welcome. Please reply directly to me as I am on digest.
> Many thanks,