Autonumbering problem for webhelp vs pdf

This forum is for all Flare issues related to styles, stylesheets and XML.
Post Reply
peterbrown05
Propeller Head
Posts: 52
Joined: Fri Jun 18, 2010 9:08 am

Autonumbering problem for webhelp vs pdf

Post by peterbrown05 »

Hi
I am documenting a requirements document using flare. It is vitally important that my numbering stays in sync between all outputs and stays related to the original customer requirements document (in word format).

I have successfully produced the pdf output. (UN-selected option "Use TOC depth for heading levels") and checked that all numbers stay in line with the original word document.
I then wanted to enable the same numbers in the WebHelp output; but, to my surprise they come out differently.

Looking at the first 2 topics; I expected them to look like the pdf:

Code: Select all

PDF Numbers:
<---- topic1.htm starts here
1. First chaper
1.1 first heading
1.1.1 sub heading
1.1.1.1 blah
1.1.1.2 blah
1.1.2 sub heading2
1.1.2.1 blah
<----- topic2.htm starts here
1.1.3 next sub heading
1.1.3.1 blah
etc... but to my surprise

it comes out like this:

Code: Select all

...(as above) then:
<----- topic2.htm starts here
1.1.4 next sub heading
1.1.4.1 blah
so there is a doble increment on the third autonumber field. I've checked and recehcked and I dont have any additional <h3> tags at all.

My numbering style is set up to be the same for print and non-print output thus:

Code: Select all

	h1
	{
		mc-auto-number-format: 'CH: Chapter {chapnum}{ =0}: ';
		mc-heading-level: 1;
	}

	h2
	{
		mc-auto-number-format: 'CH:{chapnum}.{n+}{ =0} ';
		mc-heading-level: 2;
	}

	h3
	{
		mc-auto-number-format: 'CH:{chapnum}.{n}.{n+}{ =0} ';
		mc-heading-level: 3;
	}

	h4
	{
		mc-auto-number-format: 'CH:{chapnum}.{n}.{n}.{n+}{ =0} ';
		mc-heading-level: 4;
	}

Any thoughts as to why this is happening would be greatly received. I thought this would have "just worked". Im tearing my hair out over this!

cheers
peteB
peterbrown05
Propeller Head
Posts: 52
Joined: Fri Jun 18, 2010 9:08 am

Re: Autonumbering problem for webhelp vs pdf

Post by peterbrown05 »

ok; this has been a painful journey but I have finally identified the cause of the problem. Posting here incase it helps someone else in my position;

turns out that my Master Page was causing the numbering to get incremented in the funny fashion;

Master Page was something like this:

Code: Select all

    <body>
        <MadCap:breadcrumbsProxy />
        <MadCap:bodyProxy />
        <MadCap:miniTocProxy class="" style="mc-toc-depth: 1;" />
    </body>
but turns out that the miniTocProxy was causing the numbering of subsequent pages to go awry ; perhaps because the H2 title for the subsequent pages was inherited into the class of the master page miniToc and it was as if the h2 appeared twice. thus ; the number incremented twice.

so; changing the Master page to become:

Code: Select all

    <body>
        <MadCap:breadcrumbsProxy />
        <MadCap:bodyProxy />
    </body>
(ie I removed the miniToc; and this "fixed" the problem. Obviously I have lost my miniToc; and perhaps this is a known bug????

anywayl my miniToc isnt essential so my immediate problem is solved.
LTinker68
Master Propellus Maximus
Posts: 7247
Joined: Thu Feb 16, 2006 9:38 pm

Re: Autonumbering problem for webhelp vs pdf

Post by LTinker68 »

I think others have used the miniTOCProxy in the masterpage without it causing problems with other auto-numbering. And the only reason it should cause problems with the auto-numbering is if you used an auto-numbering scheme on the miniTOC proxy that conflicted with the heading auto-numbering. I haven't seen that happen myself, but I always put an "ID" in my numbering schemes to differentiate them. For instance, my heading auto-number formats (all levels of the heading) begin with "GH" -- the G meaning it's a global counter and the H being the "ID" for that sequence. If I had an auto-number format on my miniTOC, then it would have a different ID. Likewise, the format for figures begins with "GF" and tables begin with "GT".

So I'd put the miniTOCProxy back into the masterpage (perhaps get rid of the empty class attribute) but check all the auto-numbering formats to make sure none are in conflict.
Image

Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
Post Reply