Hi,
The solution to the first-page problem is to define a new
page-sequence-master that has only 'odd' and 'even' pages, assign it a new
name, and use that name in the param named 'master-reference' when you call
the 'page.sequence' template:
<xsl:call-template name="page.sequence">
<xsl:with-param name="master-reference">sectionbody</xsl:with-param>
etc.
The 'page.sequence' template accepts other params too ('content' was used
initially), and you can see those params in the template as it is defined in
fo/component.xsl.
Information about creating new page masters is described here:
http://www.sagehill.net/docbookxsl/PageDesign.html
I'm not sure what's going on with the second problem, as I did not see that
issue. Is your customization setting indents for body text? Can you
describe that problem in more detail?
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Tobias Anstett [k15t.com]" <[email protected]>
To: "Bob Stayton" <[email protected]>
Cc: "docbook-apps" <[email protected]>
Sent: Wednesday, May 06, 2009 4:26 AM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems
Hi Bob,
I changed the code like you proposed. Now I am facing problems with
the PDF output. Every time a new page-sequence is started it is
interpreted as "first" page which has a totally different layout than
the "odd" and "even" pages. Furthermore all pages after the second
page-sequence have a wrong indent by means of admoniations, examples
and text rendering in the nirvana.
Any solutions?
Cheers,
Tobias
On Wed, May 6, 2009 at 12:37 AM, Bob Stayton <[email protected]> wrote:
Hi,
Yes, that is one workaround that should work in FOP.
Two things need to happen. The template that matches article will generate
a page-sequence, so the section content and any elements that come after
sections (glossary, appendix) must be excluded from that page-sequence
because you cannot nest page-sequences. Then you need to put each top
level
section and any elements after sections in in their own page-sequences.
In the template with match="article" in fo components.xsl, change:
<xsl:apply-templates/>
near the end of the template to
<xsl:apply-templates
select="*[not(self::section)][not(preceding-sibling::section)]"/>
That removes sections and any elements after sections from the article
page-sequence.
Then after the closing tag of the article page-sequence, add this:
...
</fo:page-sequence>
<xsl:for-each select="*[self::section or preceding-sibling::section]">
<xsl:call-template name="page.sequence">
<xsl:with-param name="content">
<xsl:apply-templates select="."/>
</xsl:with-param>
</xsl:call-template>
</xsl:for-each>
</xsl:template>
This processes all the sections and elements that follow sections, each in
their own page-sequence.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message ----- From: "Tobias Anstett [k15t.com]"
<[email protected]>
To: "Bob Stayton" <[email protected]>; "docbook-apps"
<[email protected]>
Sent: Tuesday, May 05, 2009 2:28 PM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap
Problems
...
so one possible solution would be to close the existing
fo:page-sequence and start a new one before every major section (1. 2.
3. ...). How could I do something like this? I must use
fo:page-sequence and not break-after page, but you know best.
Cheers,
Tobias
On Tue, May 5, 2009 at 6:23 PM, Tobias Anstett [k15t.com]
<[email protected]> wrote:
Hi Bob,
I analyzed the problem by splitting the whole generation chain like
you suggested.
The problem occurs when the Apache FO processor does the
transformation to PDF. After contacting the Apache FO mailinglist I
know what my problem is, but not how to solve it.
Adrian Cumiskey from the Apache FO mailinglist pointed out to check if
I use "many" page sequences in the resulting FO document, because FOP
processes documents by page sequence. Thus if I can section the
document contents into lots of small page sequence segments this can
help a lot with memory consumption.
So I checked the generated FO documents (size from 300kb to 20mb) and
noticed that there is really one single page sequence that wrapps all
the content.
=> Thus my question is => is there a way to change this behaviour and
how would it influence the look of my document?
I am exporting in article style using a own page sequence master in
the customization layer.
Cheers,
Tobias
On Fri, May 1, 2009 at 7:40 PM, Bob Stayton <[email protected]> wrote:
Hi,
Are you using FOP to apply the XSL stylesheet as well as converting the
XSL-FO to PDF? If so, you might try splitting those functions by first
generating an FO file with Saxon or such, and then processing the FO
file
with FOP. That would at least tell you which step was having the
problem.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message ----- From: "Tobias Anstett [k15t.com]"
<[email protected]>
To: "docbook-apps" <[email protected]>
Sent: Friday, May 01, 2009 10:02 AM
Subject: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems
Hi,
we are using the DocBook stylesheets in combination with Apache FOP
inside a web app. I already assigned more than 1024m to -Xms and -Xmx
but some (large) DocBook to PDF conversions still cause Java Heap
Exceptions. Is there a way to reduce the consumed memory ?
Cheers,
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
