Thanks for the responses to my quarry. For my purpose I will choose to use the 
user variables, and appreciate knowing the other options for future projects. I 
was hoping if I only had one line with the assigned paratag that it would 
populate throughout the book.



I apologize for the multiple posts. I could not figure out why my emails were 
not posting to the list and then saw that I had not received any posts since 
the end of August.



Thanks for the responses,



Anne



Anne H. Duffield





Anne Duffield  ?Senior Technical Writer 



916.286.3105 ?office

aduffield at stratascale.com <mailto:rsuchan at stratascale.com> 

www.stratascale.com 
<http://www.stratascale.com/microsite/Dedicated-Hosting.html> 



Please consider the environment before printing this email. 
`?.??.???`?.?.???`?...? ><((((?>`?.??.???`?.?.???`?...?><((((?>







From: Fred Ridder [mailto:[email protected]] 
Sent: Sunday, October 02, 2011 7:45 AM
To: Anne Duffield; framers at lists.frameusers.com
Subject: RE: Pulling cover information for Running H/F



The Running H/F variables were not designed for this purpose. They are actually 
much more powerful than this simple taks, because they are deisgned to pick up 
information that changes from file to file within a book or from page to page 
within a file. What you are trying to accomplish is a much simpler 
goal--inserting the same static content in the header or footer of every page. 
There are two fairly direct ways to accomplish this: user variables and 
cross-references.

If your chapter files will always be used as components of the same book, you 
can use cross-references in the header or footer to pick up the conent of any 
paragraph in any other file in the book, such as the VersionDoc and VersionSoft 
paragraphs in your cover page file. This approach has a few disadvantages. If 
you will be using any of your chapter files in more than one book, the approach 
doesn't work very well because the x-refs are always linked to a target file 
with a specific name and path location relative to the chapter file. This 
approach also creates a flock of x-refs that need to update in each file every 
time you open the file, which means slower opening. And when you create a PDF 
of your book, you'll wind up with hyperlinks from the headers/footers to the 
cover page, which are unnecessary and potentially disconcerting for users. 

The most direct and easily maintainable approach is to use a user variable for 
the desired strings and to use those variables wherever the string needs to 
appear--including the cover page itself. In other words, you'd type the 
document version and software version strings in the Variables dialog rather 
than in the body page of the cover page file. Then you'd use 
File>Import>Formats to import the variable definitions from the title page into 
all of the chapter files (a single-step operation if you do it from the book 
file). Using this approach and making the step of importing variables a 
standard part of your procedure for preparing a book for publication makes it 
quite easy and fairly foolproof to share some chapter files (e.g., overviews, 
glossaries, bibliographies or reference lists) among multiple books. 

-Fred Ridder



________________________________

Subject: Pulling cover information for Running H/F
Date: Thu, 29 Sep 2011 15:58:00 -0700
From: [email protected]
To: framers at lists.frameusers.com

Is it possible to have a Running H/F pulled from the cover document and appear 
in the footer throughout the entire book?



I would like the document version and software version on my cover to appear in 
the footer throughout my guide.



I created paratags for each and am using 



Running H/F 11 <$paratext[VersionDoc]> 

Running H/F 12 <$paratext[VersionSoft]>



Unless I have the information in each file it will not populate in the footer.



Thanks,



Anne





Anne H. Duffield





Anne Duffield  ?Senior Technical Writer 



916.286.3105 ?office

aduffield at stratascale.com <mailto:rsuchan at stratascale.com> 

www.stratascale.com 
<http://www.stratascale.com/microsite/Dedicated-Hosting.html> 



Please consider the environment before printing this email. 
`?.??.???`?.?.???`?...? ><((((?>`?.??.???`?.?.???`?...?><((((?>






______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________ You are currently subscribed to 
framers as DocuDoc at hotmail.com. Send list messages to framers at 
lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe 
at lists.frameusers.com or visit 
http://lists.frameusers.com/mailman/options/framers/docudoc%40hotmail.com Send 
administrative questions to listadmin at frameusers.com. Visit 
http://www.frameusers.com/ for more resources and info.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20111003/17287357/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 8750 bytes
Desc: image001.png
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20111003/17287357/attachment.png>

Reply via email to