Barbara Duprey wrote:
william drescher wrote:
Barbara Duprey wrote:
william drescher wrote:
Brian Barker wrote:
At 13:40 01/08/2009 -0400, William Drescher wrote:
I have a master document/subdocuments. I would like to have a heading that spans all subdocuments and footers that are unique to each subdocument. The master document has no text in it, it is just a container for each chapter. If I open the master document and create a header, it works fine. But, If I create a footer in a subdocument, it is not carried to the master document.

I'm no expert on master documents, but here's a thought. The master document appears to inherit styles from its subdocuments. And headers and footers are properties of their page styles, of course. So I think you need to create different page styles in your subdocuments and create the footers in those. These styles could simply be copies of each other, provided they have different names. You may then need to repeat your common header in each page style, but that's a small inconvenience.

I trust this helps.

Brian Barker

Thanks Brian, but that is really messy in a document with lots of subdocuments. I was hoping there is an easier, more straightforward way.

bill

Bill, you haven't mentioned what is unique about the footers in the subdocuments. If it could be accomplished through fields (predefined or custom), maybe your master document could contain the footer as well as the header. I'm no expert on fields, but I'll bet Brian or somebody could help with that.

The header is the title of the whole book. I want the footers to just be the chapter title.

That should be straightforward, just Insert > Fields > Other, Document tab, Chapter, Chapter name into the master document footer and I think you'll have what you need as long as you're using the standard styles (Heading 1 content is used as chapter name).

Wow !
Worked like a treat !
Thank you so much.

bill


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to