RoboHELP as a single sourcing tool

[Sharon Key <sharon -at- dra -dot- com>]

Background...We're a small company...we write library automation software
for medium to large, academic and public libraries.  Up until a year ago, we
provided our documentation in 15 three-ring binders.  These docs were
produced using MSWord.  Some of this stuff is very, very ugly.  We're
talking about screen shots that were typed by hand.  We want to convert
these docs into HTML and make them searchable by using Microsoft's index
server.

In addition, we have several new software products.  We're being told that
we need to furnish documentation for this new software in the following
formats:  context-sensitive Help files, printed documentation, PDF files,
and HTML.  We're not sure what our customers want; we assume they want
everything.  Let it suffice to say that we will produce everything.

We attended the STC conference last year where single sourcing was a hot
topic.  All the tools seemed very expensive.  Everyone I talked to off line
told me to wait...single sourcing was currently a pipe-dream for most
people.  Plus, it wasn't really ready for prime time.

My colleague has suggested that we use RoboHELP (WinHELP) to produce
everything.   Now, I used an old version of RoboHELP in a former life, but
I've been away from it for about three years.  On the other hand, he is
going great guns with it.  Loves it.  Talks about it like it's the best
thing since sliced bread.  I'm lost.

Here's the question...does RoboHELP seem to be a viable single-sourcing
option for us?  I've not been able to find anyone who uses RoboHELP to
produce all their documentation and I'm certainly not qualified to judge
this myself.  

I'd be grateful for any insight.  I can furnish more details if you need
them.

Sharon Key
Data Research Associates
St. Louis, MO  USA