TOC Levels and Page Numbering

[Techno]

Having finally resolved the lack of images thanks to the forum, I'm struggling (or perhaps just too tired) to resolve two other issues.

1) I'd like to limit my TOC to just the first four levels. Where is this done?

2) How does one ensure page numbers are produced?

Any pointers would be most appreciated.

[NorthEast]

Having finally resolved the lack of images thanks to the forum, I'm struggling (or perhaps just too tired) to resolve two other issues.

1) I'd like to limit my TOC to just the first four levels. Where is this done?

2) How does one ensure page numbers are produced?

Any pointers would be most appreciated.

Both of these should be covered pretty well in Flare's help...

1) The mc-heading-level property controls what styles are displayed at which level in your print TOC; so in your case you need to set this property to 0 for any styles where it's above 4 (e.g. h5, h6).
http://webhelp.madcapsoftware.com/flare ... Levels.htm

2) If you're using page layouts, insert the page number variable (System) in your header/footer. Alternatively, and probably less likely, if you're using master pages then insert the variable on the master page.

[Techno]

Many thanks indeed, Dave.

I guess much of my problem is as the old addage goes; "The UK and USA are two countries separted by a common language!"

To a relative novice like me, "The mc-heading-level property is used to indicate a TOC level for a style." is hardly intuitive. Why not label that field "TOC Level"?

Nevertheless, the results I'm getting so far are quite impressing my American masters, and I'm looking forward to improving them.

Thanks again.

[LTinker68]

To a relative novice like me, "The mc-heading-level property is used to indicate a TOC level for a style." is hardly intuitive. Why not label that field "TOC Level"?

Because that's an attribute in the stylesheet and style attributes can't have spaces in them. The mc is for MadCap. And they went with heading-level because your heading level doesn't necessarily correspond to a topic's final heading levels as displayed in the TOC Editor or even to the heading styles (h1, h2, h3), so they were trying to be generic yet descriptive.

An example of the heading level not matching the topic's final heading levels is if you have the "Use TOC depth for heading levels" option (I think that's the label) enabled in the target. If that's enabled, your topic's h1 tag could be changed to an h2 tag in the output, depending on the topic's depth in the TOC file.

And yes, that is a bit difficult to get your head around initially.

[Techno]

Many thanks again. That's my Word TOC looking much better.

Now - what do Madcap call what Word for Windows's Paragraph Style Formatting calls, "Keep with Next"?

I have an <H4>, a <Keystroke> followed by either a screen shot or paragraph of text which I want to keep together on the same print page.

[LTinker68]

Set page-break-after to avoid in the stylesheet. You probably don't want that with every paragraph, though, so you'll want to create a class of paragraph with that property set to avoid, then apply that class to the appropriate paragraph. There are also widow and orphan controls, although I'm not sure how well they're supported, especially to different outputs. Word, in particular, doesn't support all CSS attributes (e.g., DIVs, images for bullets, etc.).

[Techno]

Thank you again Lisa. That's another lesson learned and problem resolved. Just trying to tackle page numbering, but after 4-5 hours I need a break.

George.

[helen]

If you have the luxury, I would strongly advise you to skip Word output and go straight to PDF. Word does some horrible things to CSS as well as ignore whole chunks of it. PDF output looks great, Word output on the other hand looks "okay" but needs a lot of tweaking to make it look even remotely decent. I won't turn this into another Word rant but do give it some consideration if you are able to.

[Techno]

One of my problem, Helen, is that my output needs to be accessible to blind people with screen readers. Also, the software for which I author the Help files, also uses Word for Windows, and in particular Word's Styles, in order to convert the text to properly formatted braille. Consequently it's very much a case of practicing what we preach!

While I agree that PDFs are in many ways a better option, they can be a swine to work with if you are blind.