You could always look at TemplateMapper, but I think it's not geared entirely
to your problem. Still, if you come up with a normalized template, then you
*could* make a map that incorporates everything your legacy has accumulated and
then map it to your template. And it handles all those catal
ve to struggle quite so much with the
HTML mapping table! ;-) Also working on ways to get co-users to use
character styles (more) correctly.
Jim, Thanks for pointer to reference materials.
Thanks to all!
Karen
>Date: Fri, 19 Jun 2009 09:47:11 -0500
>From: "Jeff Schweiner"
>Sub
its structured emphasis.
Jim
-Original Message-
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Karen Robbins
Sent: Friday, June 19, 2009 12:20 PM
To: framers@lists.frameusers.com
Subject: Re: Merge Multiple Doc Styles?
Rick and Art
Rick and Art,
Thanks for your insights. Both sensible approaches and at least
somewhat less painful than rebuilding the entire thing from scratch
:-).
--Karen
>==Rick's Reply==
>
>Hi Karen,
>
>Here is how I would approach the problem. Find the component the book that
>is the most solid as far
Karen,
Rick makes a good point that a complete template should include more
than just paragraph tags and mentioned Character and Table formats. I
went thru this about 1.5 years ago and found inconsistencies in the
following areas:
- Conditional Text tags
- Variable and Running Header/Footer defi
Hi Karen,
Here is how I would approach the problem. Find the component the book that
is the most solid as far as styles. Make a copy of this and call it your
"template." Delete all of the paragraph format formats in this document that
still need work, leaving only the solid formats.
For each of
I think any method you choose depends on having one known-good file
that you can use as a template for the others. It may be a true
template or one of the chapters, but it should exist so you can clone
it to the others and enforce consistency. Depending on the version of
FM that you're running (you