Re: Need Advise for Converting to HTML Help

[The Tech Writer <techwrtr -at- CRL -dot- COM>]

We're doing it right now. In fact, we're converting both hard copy and
winhelp documents to HTML Help, using RoboHTML. It's really rough going,
as we're working with a 1.0 software program. It is extremely slow, and
there's lots of bugs. You can join the listserv that Blue Sky (the maker
of RoboHELP and RoboHTML) created for discourse on the program, via their
web site, http://www.blue-sky.com.

Drawbacks? It's a pain to implement. Benefits? We'll have all of our
information in one format, which will allow us to spend more time on
improving the content, since we won't be copying content between the two
media.

The users must use Internet Explorer 4. It really sucks, because IE4
causes all sorts of problems on any machine it's installed on. My Network
Neighborhood doesn't work, my AS/400 connectivity software doesn't work,
and the list grows every day.

If you have additional questions, feel free to email me directly.

-David Castro
 techwrtr -at- crl -dot- com

On Mon, 2 Feb 1998, Robyn Faulkner wrote:

> The Engineering group at our company is requesting that we convert our
> existing Win Help Online Help (Windows 95 and NT platforms) to an HTML
> Help format. Has anyone done this before? If so, what has been your
> experience? What are the drawbacks? Benefits? Are there issues with any
> particular browser an end user maybe using?
>
> Words of wisdom would be greatly appreciated.
>
> Thanks.
>
> Robyn Faulkner
>
>
>
>