Changed h1 tag properties when Medium=print is ignored

[Paul_N]

I want to have h1 headings that are a sans font in HTML5 - Top Navigation output, and serif in print/PDF. For example, in the StyleSheet editor for the h1 tag I've set:

Medium: Default= Verdana 1.5em (for HTML5 output)
Medium: print = Times New Roman 24pt

The different font appears in the automatically generated chapter pages of a PDF, but in the topic pages of the PDF the h1 tagged page title stays at the default setting, even though I've set h1 to be Times New Roman 24pt when medium = print.

It's not apparent to me why when I change stuff in the Stylesheet Editor for Medium=print it doesn't get applied when I generate a PDF for topic pages. Has anyone got any pointers as to what I should be setting to get a different font in the print output?

I'm a Flare newbie wit MadCap 12 with the latest updates.

[ChoccieMuffin]

In your PDF target, on the Advanced tab, do you have the Stylesheet Medium set to Print?

[Paul_N]

In your PDF target, on the Advanced tab, do you have the Stylesheet Medium set to Print?

Thanks for the reply. Yes I have.

On the General tab I have Output Type = PDF
On the Advanced tab I have Stylesheet Medium = Print

As an experiment I tried changing it to Stylesheet Medium = PDF, but once again any changes to the h1 style did appear in generated PDF pages like the ToC and chapter title pages, but not on the 'content' pages that also had a tag of h1.

I may index all of the MadCap PDF user guides and see if a search turns anything up. It's probably some little check box setting buried on an obscure dialog somewhere.

If I still don't get any joy I may contact their support to see if there's a know bug...

[ajturnersurrey]

Here is a link to the little I have gleaned from my problems with this in the past (albeit caused by using default for my pdf/print medium and having to set up a non-print medium for web help at a later date).

viewtopic.php?f=75&t=21900

[Nita Beck]

Your mention of "generated ToC" made me take notice. See my reply in this forum discussion: viewtopic.php?f=10&t=27556. It MIGHT have some bearing on your issue (and if it does not, my apology for taking you down the proverbial garden path).

[Paul_N]

The solution to my problem (thanks to MadCap support's help) was because my h1s in my topics were effectively h2's in the PDF. This is because the level is being set by where they are in the Target=PDF ToC for PDF output. So I just had to go into the stylesheet editor and edit the fonts characteristics for h2/medium=print, and the stuff tagged h1 for picked up the h2 for print characteristics.

The Target Editor's Advanced tab, under Generated TOC had Use TOC depth for heading levels checked to force this behaviour to happen.