Unless you implement a manual or scripted solution as Mark suggests, you probably can't -- I noted in the first post that the out-of-the-box solution only works when the heads are on the same page.
Just in passing, from a reader's point of view, it probably doesn't give me any useful information to know what the next subtopic (Heading2) is, especially if it's several pages away. Knowing the topic that's on the page though, could be helpful, especially if you're skimming for info. Art On 1/10/07, Gillian Flato <gflato at nanometrics.com> wrote: > But my Head2 is not necessarily on the same page. I could have a Head1 > and an introduction that is long and makes the text flow onto the next > page so the Head 2 starts on the next page. So how do I compensate for > that? > > > Thank you, > > > Gillian > -----Original Message----- > From: Steve Rickaby [mailto:srickaby at wordmongers.demon.co.uk] > Sent: Wednesday, January 10, 2007 2:47 AM > To: Art Campbell; Gillian Flato > Cc: framers > Subject: Re: Running Headers > > At 16:59 -0500 9/1/07, Art Campbell wrote: > > >If all your heads are on the same page as the header, though, you can > >tell it to pick up the last Head2 on the page by modifying the > >variable string in the Master Page header to <$paratext[+,Head2]> > >instead of <$paratext[Head2]>. > > Yup: this '+' notation also allows you to create 'dictionary' style > spanned headers, like 'Aardvark-Avocet', 'Bantam-Broiler', kind of > stuff. I've used it when typesetting directories. > > -- > Steve > -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358
