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:Re: Single Sourcing From:ellen ewald <eellen -at- IPCELL -dot- COM> Date:Wed, 9 Jun 1999 10:35:07 -0500
when i click on this link it returns:
The requested web address does not exist on our server.
From: Mary Deaton <m_deaton -at- KWARE -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Wednesday, June 09, 1999 10:19 AM
Subject: Re: Single Sourcing
>Joanne Hackos is giving a session on single-sourcing using a database at
>Help Technology Conference in August. She has given this presentation in
>several places to rave reviews. People interested in single-sourcing
>solutions might want to check it out at http://www.winwriters.com/htc99.com.
>President, KNOWware, LLC
>* Smart User Assistance and Training http://www.kware.com
>* Microsoft MVP for HTML Help
>* Program Associate, Winwriters 200 Online Conference
>* Speaker, HElp Technology Conference,
>* and all-around great gal!
>From: Xiang Li [mailto:xli -at- FEDERALAPD -dot- COM]
>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.
>From ??? -at- ??? Sun Jan 00 00:00:00 0000==