Why not just use Frame? (Was RE: Robohelp vs. Doc-to-Help)

[Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM>]

Why don't you just author WinHelp directly in Frame?

You can convert Frame directly to WinHelp-compatible RTF using the
MIF2RTF tool from Omni Systems (meaning no clean-up in Word -- in fact
you don't even need Word for this), then create/compile your Help
project file in HCW (available for free from Microsoft). You can do
macros, jumps, keywords, etc.
http://www.omsys.com/

I've used Robohelp and Forehelp. If you didn't already have Frame, I'd
say they'd be fine. However, if you already have Frame, why buy and
learn unnecessary tools.

A.
--
Alexia Prendergast
Tech Pubs Manager
Seagate Software (Durham  NC  USA)
mailto:alexiap -at- seagatesoftware -dot- com

> -----Original Message-----
> From: Kim Wallace [SMTP:kwallac -at- ECT -dot- ENRON -dot- COM]
> Sent: Wednesday, February 25, 1998 5:04 PM
> To:   TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject:      Robohelp vs. Doc-to-Help
>
> Techwhirlers:
>
> The shop I'm working in is evaluating whether we should use
> Doc-to-Help
> (the currently used software) or move to Robohelp. I'd appreciate
> hearing
> your thoughts on these packages. Which did you find easier to use (and
> why)? How much time did it take you to learn it? How long to final
> product?
> Can you take a project written in one and use it in the other app?
> Tips and
> bug alerts also warmly appreciated. Thanks!
>
> BTW we are authoring all documentation in FrameMaker, so a conversion
> to
> Word will be required.
>
> ~~
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
> TECHWR-L)
> Search archives at:
> http://listserv.okstate.edu/archives/techwr-l.html,
>