Re: We need a specialized doc set- advice?

Subject: Re: We need a specialized doc set- advice?
From: Rick Sapir <rick_sapir -at- GILBARCO -dot- COM>
Date: Tue, 20 Feb 1996 08:15:12 -0800

This is a Mime message, which your current mail reader
may not understand. Parts of the message will appear as
text. To process the remainder, you will need to use a Mime
compatible mail reader. Contact your vendor for details.

Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part

You could use FrameMaker's conditional text to create a single
document with conditions A-I. Then simply "turn on" the conditions
that you want when you create a PDF file.

Rick Sapir Gilbarco, Inc.
Technical Communicator Greensboro, NC
Rick_Sapir -at- gilbarco -dot- com
DISCLAIMER: Speaking for no one but myself.

"Ideas withheld or repressed are automatically imbued - Jeff Heiskell
with a false sense of mystery and intrigue." The JudyBats

>Subject: We need a specialized doc set- advice?
>From: jblair -at- creo -dot- bc -dot- ca at ~GATEWAY
>Date: 2/19/96 3:53 PM


> Now, the company is starting to go modular; i.e., everything will be
> sold separately as well as in bundles. We need to come up with
> formatting, organizing, and binding options for the manuals based on
> the future 'modularity' of our products.

> Unfortunately, this is not as simple as writing smaller manuals for
> each product and issuing and bundling them at the time of sale.
> Because of the interdependence of the products, there needs to be
> information on how the products will be used with other products. For
> example, B could be sold with A-E, but it could also be sold by
> itself, and the user might want to use it with *any* of our other
> products, or with other companies' products.

> We've been thinking about PDF as a way of quickly customizing docs,
> but this hasn't developed beyond the speculative stage.
Content-Type: text/plain; charset=US-ASCII; name="RFC822 message headers"
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part

Received: from by with SMTP
(IMA Internet Exchange 1.04b) id 1293cae0; Mon, 19 Feb 96 19:14:54 -0800
Received: from by with SMTP id AA04408
(InterLock SMTP Gateway 3.0 for <RICK_SAPIR -at- gilbarco -dot- com>);
Mon, 19 Feb 1996 19:15:17 -0500
Received: from by id aa23581;
19 Feb 96 17:54 CST
release 1.8b) with spool id 37046 for TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU;
Mon, 19 Feb 1996 17:54:56 -0600
Received: from by (8.7.2/SMI-4.1) id PAA00047; Mon, 19
Feb 1996 15:54:16 -0800 (PST)
Received: from ccMail by (SMTPLINK V2.11 PreRelease 4) id
AA824774069; Mon, 19 Feb 96 15:53:40 PST
Message-Id: <9601198247 -dot- AA824774069 -at- mail -dot- creo -dot- bc -dot- ca>
Date: Mon, 19 Feb 1996 15:53:40 PST
Reply-To: jblair -at- creo -dot- bc -dot- ca
Sender: "Technical Writers List; for all Technical Communication issues" <TECHWR-
L -at- listserv -dot- okstate -dot- edu>
From: jblair -at- creo -dot- bc -dot- ca
Subject: We need a specialized doc set- advice?
To: Multiple recipients of list TECHWR-L <TECHWR-L -at- listserv -dot- okstate -dot- edu>

Previous by Author: Re: Needs/Task Analysis Training
Next by Author: Re: Electronic File Transfer
Previous by Thread: Re: We need a specialized doc set- advice?
Next by Thread: mail delivery error

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

Sponsored Ads

Sponsored Ads