RE: Object-Oriented Documentation

Subject: RE: Object-Oriented Documentation
From: eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 21 Jul 2003 12:13:29 -0400





The suggestion to use text insets is a good one.

One approach would be to create individual documents for each procedure or
concept, then use FrameScript to assemble the final documents based on
various criteria. Essentially database publishing without the database.

Not a trivial thing to set up, but no solution will be.

Eric L. Dunn



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

NEED TO PUBLISH FRAMEMAKER CONTENT ONLINE? "Mustang" is a NEW single
sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required! http://www.ehelp.com/techwr-l3

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-

---
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.



Follow-Ups:

Previous by Author: RE: Nielsen and PDFs
Next by Author: Re: The saga ended (or is it continuing? (was Re: A sticky contractor situation: no pay yet?)
Previous by Thread: RE: Object-Oriented Documentation
Next by Thread: RE: Object-Oriented Documentation


What this post helpful? Share it with friends and colleagues:


Sponsored Ads