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.
--- Bill Swallow <wswallow -at- nycap -dot- rr -dot- com> wrote:
> The problem is, as several have already pointed out, that
> RoboHelp is not a single-sourcing tool (no matter how much
> they tell you otherwise). It just doesn't work that way. Any
> time you spend time tweaking output to make it fit your
> needs, you're abandoning single-sourcing, as you'll have to
> perform the same or more manual cleanup every single time
> you churn out the output. There is a better way; get a
> single-sourcing toolset.
This is why, back in the mists of time in 1992, when I first started
to investigate this problem, I went with Doc2Help over RoboHelp. With
Word (and I had a 600+ page manual formatted over 9 separate linked
chapter files), it worked very well for single-sourcing. All of the
tweaking for help, I did in different color text, hidden fields,
footnotes, and bookmarks. Then creating the help was a one click
process. Furthermore, since Doc2Help was just a set of WordBasic
macros, it was extensible.
Is Doc2Help still around? Is it still a good tool for single-sourcing
from Word?
WebWorks can be made to do that with Frame beautifully! However, it
requires WebWorks Professional and a LOT of painful tweaking to get
there.
