Re: [xsl] 2 column page layouts in FO

Subject: Re: [xsl] 2 column page layouts in FO
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Sep 2005 19:39:42 -0400
Hi Dan,

At 2005-09-15 11:59 -0700, Dan Vint wrote:
I'm trying to create an index for my publication and set it on a 2 column page, where the rest of the pub is one column. What I'm finding is the first page of this section is setting as a single page wide column and follow on pages are setting as 2 column correctly. I don't set any spans and when I check to bounding boxes in Antenna House it shows blocks spanning the whole page on the first page and the second page shows two columns.

So I know my text output and its blocks are correct because they format properly on subsequent pages, so it seems like it should be in the page layout information where this is being changed, but I can't see the problem. Also, if I force a page break before my heading of Index, all the text formats correctly.

Here are my page layouts:

<fo:simple-page-master master-name="index-2col"
        page-height="{$pageHeight}" page-width="{$pageWidth}"
        margin-right=".75in" >

          <fo:region-body margin-top=".5in" margin-bottom=".35in"/>
  <fo:region-before extent=".5in" display-align="before" />
  <fo:region-after extent=".5in" display-align="after"/>

        <fo:region-body column-count="2" column-gap=".5in"

I note above that you have *two* <region-body> constructs ... is that a copy/paste problem in the email or do you actually (incorrectly) have two in there?

Antenna House may not be reporting an error because it is satisfied there *is* a <region-body>, it just isn't counting them.

I could imagine having two might cause some internal problems.

I hope this helps.

. . . . . . . Ken

World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05
Legal business disclaimers:

Current Thread