Hi, Tara.
Oh, yes - I can confirm that it is generally not considered
necessary to put output files under source control, except in one
circumstance. (Which I was unfortunately caught up in.)
If your application does automated builds from the source
control system, the build script can't generate WebHelp - you have
to open RoboHelp and generate from there. In that case, I had to
generate my WebHelp output and check the whole thing in.
I got around the filename thing (because adding/deleting
topics was causing merry hell) by packing the whole output folder
in a .jar file - kind of the Java equivalent of a .zip file. The
build script could unpack the .jar and put the help folder where it
was supposed to go.
This happy solution took about three months to come up with -
the first one was for me to beg the forum for a command-line
compile for WebHelp (duh, it's proprietary, so there isn't one),
the second month was to convince the ClearCase dudes that there
wasn't a command-line compile for WebHelp, and the third was
persuading the ClearCase Powers That Be to let us check in the
output .jar. Oy!
HTH,
Elisa