Re: Structured FrameMaker Master Pages

Subject: Re: Structured FrameMaker Master Pages
From: Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 29 Aug 2013 02:49:33 -0700 (PDT)

Richard Combs is right -- variables are the way to go.  Since you're using structured Maker, you could set up your template master pages to pick up values from attributes in each document's root element.  When you use a shared file in a publication, you set the correct attr val, and Maker will pick it up in the master pages.

You could go a step further and write up a FrameMaker script to automate setting these attribute vals in all the files in a book.  You could do this in a number of ways.  For example, you could trap the Book Generate event, and post a dialog that asks for the values you want.  Or you could have a magic ref page on the first file in the book and use that to cache the attr values -- automatically apply those when you generate the book.

I suppose you could just as easily do this with non-struct variables...  Set up the variables in the first file in the book, and automatically import formats (variables only) from that file into all the other book components.  Since you're using struct I prefer using attributes, but it's really academic at this point.

In any event, you're not necessarily modifying the shared files, per se.  If you modify them at render time, just don't save the changes.  Shoot, make the files read-only.  Anyway, if you have a rendering process that corrects the variables or attributes for each publishing run, it doesn't matter if you accidentally save...  No harm done.

cud

> We have lots of books to write, maintain, and update. Many sections are
> redundant from one book to another, so we want to single source some of these.
> For example, the book layout may be something like:
>
> Cover
> TOC
> Safety
> Intro
> Description
> Operation
> Maintenance
> Fluid Specs
> Torque Specs
> Contact
> Back page
>
>
> Sections (files) like Safety, Description, Fluid Specs, Torque Specs, and
> Contact can be shared among operator, maintenance, and service manuals
> (books). Some can be shared from model to model.
>
> What we want to do is have the FrameMaker book (not the individual files)
> contain the master page, but so far, I can't find anything that supports this
> in Structured. This is so the header on each page can go something like:
>
> T-800 Terminator Operator Manual
> T-800 Terminator Service Manual
> T-1000 Terminator Maintenance Manual
>
> and so on, as determined by the book.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

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

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Previous by Author: RE: Weird HTML problem
Next by Author: Re: spec writing - is simple ever wrong ?
Previous by Thread: Re: Pre-select multi-boot?
Next by Thread: RE: Structured FrameMaker Master Pages


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

Sponsored Ads


Sponsored Ads