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.
Some workflows just don't. Something probably has to
give, such as:
1) The expectations.
2) The software.
3) The timeframe.
That is, given enough resources, you can manually work
around the design of the tools you are using, but it
will be inefficient and take time. Or, you can switch
to tools that do what you want. Or, you can change
your expectations, and redefine what you really want
to better meet what your tool can do.
Cheers,
Sean
--- Gene Kim-Eng <techpubs -at- genek -dot- com> wrote:
>
> From Bill's original message, it doesn't sound as if
> he
> has the flexibility to select a different help
> authoring tool;
> his client wants him to author help in RoboHelp.
>
