Running Headers for PDF?

[scooter262]

I am trying to use a Running Header in my PDF output, but I can't get it to work. I added a new variable set, based on the running header template, and then changed the Running H/F 1 definition to a paragraph style (p_EventSourceTitle), as follows:

<$paratext[p_EventSourceTitle]>

But the PDF contained that exact text, rather than replacing it with the value of the first EventSourceTitle paragraph on the page.

I tried using simpler paragraph styles (<$paratext[p]>) just to see if I could get any text replacement, but still I only got the variable itself, rather than any replacement value.

The Output Type of my target is PDF; the help says that Running Heads are supposed to work in PDF output, but maybe they only work in Frame or Word output?

[ewok]

hello,

I'm afraid I can't answer your question, but can only ask if anyone has actually managed to get running H/F working correctly in PDF output?
I've been trying to get this to work correctly for a couple of hours, and flare still variously spits out nothing, or <$paratext[whateverStyle]>. This using both the inbuilt running header variable styles, or my own style/variable.

The flare help suggests using running h/f in page layouts (our setup) and master page layouts will work, and that it will work in PDF output.
However, the comment in the Running HF.flvar file suggests it's only valid for Framemaker and Word.

The Heading variables aren't enough for our purposes.

Anyone have any thoughts?
thanks
ewok

[Andrew]

I use running headers in my page layouts. I didn't create a new set of variables; I just used the default ones and added the running header to my header frame in the page layout.

[ewok]

hello,

then it would seem that there is something more intrinsically wrong with our setup then. super.

thanks
ewok

[ewok]

hello,

Actually, don't think it is a setup issue, I think it's a way PDFs are generated/read variables.

Spat out content using running H/F to word - and the variable worked as expected (using both a standard H1 style, and a custom p_chapter style.
Same files spat out to PDF and nothing, just the usual <$paratext[blah]> in the header.
So, still not convinced that running H/F variables work in PDF.

Even created a new project, using a default Book Template and generic files. Added default running h/f variables.
guess what? works in word, not in PDF.

anyone?

thanks
ewok

BTW - this is in Flare 6.1

[LTinker68]

Yep, I can confirm it's not working for PDF output, and the Printed Output Guide indicates that it should. Submit a bug report at http://www.madcapsoftware.com/bugs/submit.aspx.

[wclass]

Are you aware that there are two kinds of heading variables? There are Running Headers - that work in Word, and there are "Heading variables", that are newer and appeared about the same time as PDF output. If you are seeing text like "$paratext" then you've got the Word ones.

Have a look in the help (don't have the direct link):
- Features > Variables > More About Variables

The first two topics in this book should highlight the differences:
- About Heading Variables
- About Running Head Variables

I can get running headers to work as follows:
- For Word, use master pages and running headers
- For PDF use Page Layouts and Heading Variables.

And yes, it is confusing, and yes, I think they should pick one and go with just that.

[Andrew]

Sorry about that -- I didn't realize that running headers for Word wasn't the same thing as the headers for page layouts.

[LTinker68]

I think the problem is that the Flare Print Guide says that both heading variables and running headers are supported by PDF, yet it's not working.

In addition to system variables and those you can create (from the "MyVariables" template), you can also add Running Head variables (using the "Running HF" template). A Running Head (or Running HF) variable is a special variable that you can insert into a header or footer in a page layout or a print master page. It lets you display certain text in the header or footer automatically, based on the style associated with the variable. For example, Running Head variables are useful if you want to include the title of each chapter in a document in a header or footer without having to type them into multiple pages. For more information see "Running Head Variables" on page 129.

Note: Running Head variables are supported only in Adobe FrameMaker, Microsoft Word, Adobe PDF, and Microsoft XPS output.

Insert Running Head variables You can insert these variables into headers or footers within page layout frames or print master pages. See "Inserting Running Head Variables into Frames" on page 270 or "Inserting Running Head Variables Into Master Pages" on page 311.

[Oda]

Hi,
I know this thread was posted several years ago, but I 've got the same issue. I'm trying to apply a running HF into a footer. The corresponding value is displayed in the frame but when I build the PDF, it displays <$paratext[h1.style]>.

Has this issue been solved ?

Thanks

[Lydia]

The Flare Help says about Running Head Variables: "This feature is supported in Adobe FrameMaker and Microsoft Word output."
So if this doesn't work in PDF, that is expected.
Any chance that you can use Heading variables instead?

[Oda]

Hi Lydia,

Thanks, I thought that maybe it had been corrected to be supported in all print outputs.
I can't use a heading variable because I want it to be applied to a specific class. As a workaround, I specified the text I wanted in the topic title field and tried to insert the system variable "Title" but, still, it does not work and displays "TitlePage" in the output, as though it displays the expected text in Madcap.
I made a request to the support.

[Lydia]

Hi, there is that other thread with the same question: http://forums.madcapsoftware.com/viewto ... 10&t=17083. Going to update there, since it is newer and won't confuse people with the old Help information.