RE: Single-sourcing DIDN'T work for me just now

["Downing, David" <DavidDowning -at- Users -dot- com>]

Okay, I see your point.  I was trying to do it by taking one of the final products and adapt its text for another final product, when in fact the way to go about it is to start with one master documents which will be used for all final products.

-----Original Message-----
From: David Neeley [mailto:dbneeley -at- oddpost -dot- com] 
Sent: Thursday, September 18, 2003 3:19 PM
To: Downing, David; TECHWR-L
Subject: Re: Single-sourcing DIDN'T work for me just now


 David, 
  
I don't know how to ask this gently, but has it occurred to you that the problem was not with single-sourcing methodology at all, but that you came at it from the wrong premise? 
  
Once the content is divided into all the various pieces required of an online help system, it is indeed too late to easily reincorporate it into a manual. However, perhaps that's just the point--if you *knew* you'd have to produce online help *and* a manual--shouldn't you have created the proper source doc from the start and then output it in both ways? 
  

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.