Hello again. First, thank you again. My colleague and I just did a test run with the new approach and it worked beautifully.
Second, we were just discussing the same issue you raise, particularly because my books are single-sourced and hers are not. I use a variables.fmfile while she does not need to. The book title that I use on the right header pages does not change from vendor platform to vendor platform -- it's always *Product-name Installation and Setup Guide*. The book titles that she uses on the right header pages do change from connector to connector -- *Company-name Connector for 3rd-party-company-name Administrator's Guide*. If I understand your suggestion correctly, we would create a single user variable named "book title" with a definition such as "book-title". We would then open whatever book we were working on and edit the book definition variable for that book. If you edit a variable from the master template so that the values are different in different books, importing variables from the template in the future will "reset" the value to "book title". How do you handle that type of template update? Carol On 5/9/07, Jones, Donna <[EMAIL PROTECTED]> wrote: > > > We will now create unique 'book title' user variables for each unique > > book in TemplateVariables.fm and import all "common" variables from > > this file. > > > Hi Carol, > > You should only need one variable for book title and just change the value > of that variable for different books. If you create separate variables for > each book, you'll have to keep substituting one variable for another > wherever they are used. That defeats the purpose of using a variable. Maybe > I'm misunderstanding what you're doing. > > 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
