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.
Another option could be to use TemplateMapper to switch from template to template... You can set up a project file, and then it becomes a single button press. If your templates are really that different it might be the right way to go. It's specialized (not completely open like FrameScript), but that can be good for some situations. And it is extensible -- you can invoke external plugins to run special processes (like break tables apart, change anchored frames, etc.)
DISCLAIMER: This is a product plug... I make it. cud
Thanks for this Richard, the FrameScript option looks promising. At the
moment I have very little information about what the client will
provide, they may not even use FrameMaker for all I know!
But at least now I am more prepared, so thanks again.
Laura
-----Original Message-----
From: Combs, Richard [mailto:richard -dot- combs -at- Polycom -dot- com]
Sent: 23 October 2009 17:31
To: Laura Fergusson; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Framemaker Conditionalising Templates
Laura Fergusson wrote:
> Up to now I have had around 10 different variants of a standard
product,
> for which I have used conditional text and variables. All variants
have
> their own book, but have used the same template, with the front and
back
> matter customised for each.
>
>
>
> Now a new client means another variant - but they have their own
> templates which I am to use.
>
>
>
> I want to keep the same structure if possible, ie a book for the new
> client, with all relevant files contained in that book, and within
those
> files, text conditionalised where necessary.
>
>
>
> However can I do this if I am using a different template? I do not
want
> to have to make a separate copy of the files and apply a new template
-
> but is that the only way to do this?
It depends on the nature and extent of the differences. If the two
templates use the same pgf, char, xref, etc., names, but merely define
them differently, then you can simply convert at production time: make a
copy of the book and its files, apply the new client's template (i.e.,
import formats from it), produce the PDF, help, or whatever, and discard
the file copies. Repeat when necessary.
If the client is requiring the use of a template that's completely
different -- e.g., different custom master pages, different pgf and char
catalogs, different autonumber sequences, their own set of user
variables, ... -- then you're looking at far more work. Far, far more.
In the latter case, I'd raise a red flag with the boss, run to get
FrameScript (if not already available), and try to automate this as much
as possible. Rick Quatro (frameexpert.com) has some scripts available
that can help immensely (FindChangeFormatsBatch comes to mind, which
does about what the name suggests), or he can create a custom solution.
Good luck with it!
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-