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: JavaHelp or WebHelp From:"David M. Brown" <dmbrown -at- brown-inc -dot- com> To:Techwr-L post <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 06 Jul 2000 23:45:49 -0700
Justin Cascio wrote:
> JavaHelp is a royal pain in the butt. Cleaning up the output
> from RoboHELP, for instance, is a full-time job, because JavaHelp
> does not handle all standard HTML well, and many of the extras
> that RH sticks into it make JH look terrible-- extra space around
> tables from extra paragraph tags, for instance.
Let me get this straight: When you tell RoboHelp you want to create JavaHelp, it writes code that JavaHelp can't handle--and this is a *JavaHelp* problem?!
Before a vendor claims their tool is compatible with a particular format, shouldn't the tool write code that conforms to the published standard for that format?
Don't get me wrong, JavaHelp has its shortcomings--but that's a completely different issue from the one raised by Mr. Cascio.
> Web Help is nice and neat, HTML standards are fairly easy, and
> there's no extra software to install to make it run-- any browser
> will do.
JavaHelp is intended primarily for use with Java applications, in which case there's no extra software to install, either.
David M. Brown - Brown Inc.
dmbrown -at- brown-inc -dot- com