Hi, Donna. Thank you, again, for your timely and useful input. You have confirmed what my colleague and I were discussing over a lunchtime walk.
As a result of your earlier single-sourcing guidance, I had created a variables_*vendor-name*.fm file for each of the vendor-specific books. Each of these files contains three user variables -- partnumber, platform, and trademark -- which are used in the TitlePage.fm file. However, as a result of recent template changes, we have now created a TemplateVariables.fm file that contains all the common variables used in our documentation, such as product and component names with an without trademarks. We will now create unique 'book title' user variables for each unique book in TemplateVariables.fm and import all "common" variables from this file. Thanks again! Carol On 5/9/07, Jones, Donna <[EMAIL PROTECTED]> wrote: > > Hi Carol, > > Instead of using the header/footer variable and a marker for the manual > title, create a new variable called something like "book title." Put > that variable on your master pages where the header/footer variable > currently is. Then you'll simply need to import page layouts and > variables from the corrected file to the rest. You can then delete your > <$marker1> markers because you won't need them any more. The next time > you need to change the book title, you simply change the variable in one > file and import it into the rest. > > We create an "import from" file for each of our books. That file > contains all of the specific variables for the particular book it goes > with. In our case, we change the manual title, part number, product > line, and a few other things in the "import from" file and import that > information into all files in the book. > > Hope that helps! > Donna > > - CONFIDENTIAL- > This email and any files transmitted with it are confidential, and may > also be legally privileged. If you are not the intended recipient, you may > not review, use, copy, or distribute this message. If you receive this email > in error, please notify the sender immediately by reply email and then > delete this email. > ______________________________________________ Author Help files and create printed documentation with Doc-To-Help. New release adds Team Authoring Support, enhanced Web-based help technology and PDF output. Learn more at www.doctohelp.com/tcp. DOCUMENTATION & TRAINING WEST 07: THE USER EXPERIENCE April 18-21, 2007 ~ Vancouver BC ~ Marriott Pinnacle ~ free city tour 40+ sessions * free workshops * free iPod offer * www.doctrain.com _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
