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.
Subject:Single Sourcing From:Xiang Li <xli -at- FEDERALAPD -dot- COM> Date:Wed, 9 Jun 1999 09:17:21 -0400
Hi, Fellow Technical Writers:
I have brought this topic to this list twice before. I would like to
continue to talk about it because I recently have gone through the process
of single sourcing. I produced a software manual from the online help for
the same software using Robohelp. This process is not quick and Robohelp
did not generate some of the graphics from the source file. I also had to
set up the manual in the way a manual should look like. However, the final
result pleases me and people in the company because it looks much better
than the one produced by FrameMaker. I found this method is durable because
I do not have to use two different software progams to work on help and
manual. The problems I ran across are indexing, graphics will not convert,
formatting, and numbering. I fixed the previous three, however, numbering
is a consistent problem, I have to be very careful when I print. I also
sent email for the solution to this problem, nobody could fix it.
