<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17098" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Doug,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>I've done this type of thing for several clients, though on
a slightly smaller scale. I've used a couple of tools that make the process much
more doable.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Here's what I've done:</FONT></SPAN></DIV>
<OL dir=ltr>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Analyze documents for styles used using the Paragraph
Tools and Character Tools plugins from Silicon Prairie.<BR><BR>I did not look
at every single file, but would select a few from each book and look at what's
there. I would print some lists of styles, then check off or add to until I
had all the style names, including paragraph, character, table, cross
reference, variables, and conditions.<BR></FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Map all the styles in use to the new template
styles.<BR><BR>I use Rick Quatro's FrameScript (something like
FindChangeFormatsBatch). You just have a table in a Frame file and map the old
style to the new style and say whether to delete the old style. It lets you
map all of the styles I listed above.<BR><BR>These two steps are what take the
most time.<BR></FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Test the mapping/conversion by importing the new template
into a copy of the book, running the script, and looking at the
results.<BR></FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Adjust the mapping based on the test
results.<BR></FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Repeat steps 3 and 4 on a couple of
books.<BR></FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=187520921-26072011><FONT face=Verdana
color=#0000ff size=2>Run the script on the "live" books.<BR><BR>This part is
amazingly fast!</FONT></SPAN></DIV></LI></OL>
<DIV><SPAN class=187520921-26072011><FONT face=Verdana color=#0000ff
size=2>Voila! You may find some outliers here and there that you missed. If
they're in a bunch of files, you can create a new mapping file for just those
few styles and rerun the script. </FONT></SPAN></DIV><!-- Converted from text/plain format -->
<P align=left><FONT face=v><FONT size=2><FONT face=v><FONT
face=Verdana>~~~~~~~~~~~~~~~~~~~~~~~~~<BR>Linda G.
Gallagher<BR></FONT></FONT></FONT></FONT><FONT face=v><FONT size=2><FONT
face=v><FONT face=Verdana>STC Fellow</FONT></FONT></FONT></FONT><FONT
face=v><FONT size=2><FONT face=v><FONT face=Verdana><BR>TechCom Plus,
LLC<BR>lindag at techcomplus dot com<BR><A
href="http://www.techcomplus.com/">www.techcomplus.com</A> <BR>303-450-9076 or
800-500-3144<BR>Tutorials, "show me" demos, user guides, help, FrameMaker and
WebWorks ePublisher templates<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>RMIMA
Secretary<BR><A href="http://www.rmima.org/">www.RMIMA.org</A>
<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</FONT><BR></P></FONT></FONT></FONT>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> framers-bounces@lists.frameusers.com
[mailto:framers-bounces@lists.frameusers.com] <B>On Behalf Of
</B>edwardsdo<BR><B>Sent:</B> Tuesday, July 26, 2011 7:30 AM<BR><B>To:</B>
framers@lists.frameusers.com<BR><B>Subject:</B> Applying new templates to
existing documents<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>My employer has implemented a new corporate-level
style guide that impacts the look and feel of our customer-facing documentation.
Source files for these documents are created/maintained using unstructured
FrameMaker 8 running on Windows XP sp 3. 13 writers are updating the
majority of our current documents (group A) by applying templates that use
the existing paragraph/character/table format naming conventions and reflect the
new style requirements. A small group of the documents to be updated (group
B) uses the A4 page size and a set of paragraph/character/table formats that
have completely different naming conventions than those used group A. Group B
includes 50+ documents with a total of 650 source files and just over
10,000 pages. We're considering the options we have for converting the
group B documents to the new style guide requirements.<BR><FONT
face="Times New Roman" size=3> <BR></FONT><FONT face=Arial size=2>One
option is to convert the group B documents to the templates used
for the group A documents, including paragraph/character/table naming
conventions and the letter page size, so that we can move forward with a single,
consistent set of templates for all FM documents. However, this
option means that we must identify all paragraph/character/table names in
the group B documents, rename them with corresponding names from
the group A templates, and then apply the group A templates to
each FM file. Definitely a labor-intensive process unless it can be automated
significantly, possibly with FrameScript. </FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT face=Arial size=2></FONT></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT face=Arial size=2>The other option is to
modify the templates currently used for the group B documents to
obtain the needed look and feel, and then reapply those templates to
the group B documents. The conversion effort would be reduced
significantly, but we would still have two sets of FM templates to
maintain.</FONT><FONT face="Times New Roman" size=3> <BR><BR></FONT><FONT
face=Arial size=2>Is there a more efficient way to implement either of the
options I have described? Are there other options for reformatting
the group B documents?</FONT><FONT face="Times New Roman" size=3>
</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thanks.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Doug Edwards</DIV>
<DIV><BR><BR></DIV></FONT></FONT></DIV></BODY></HTML>