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.
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. 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.
This leap toward Java Help smacks of the uninformed managerial masses going
with "the next great thing" without knowing what "the next great thing"
actually is or does.
Crotchety WinHelp Afficionado
Pro-Logic & Adjustable Choke
Outsource Documentation and Online Help
justin-paul -dot- geo -at- yahoo -dot- com <mailto:justin-paul -dot- geo -at- yahoo -dot- com>
sarchasm The gulf between the author of sarcastic wit and the person who
doesn't get it.
> Could somebody on this forum talk about the strong and weak points of
> JavaHelp and WebHelp?