This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Double Side and FOP with 1.53
- From: Jens Stavnstrup <js at ddre dot dk>
- To: Togan Muftuoglu <toganm at users dot sourceforge dot net>
- Cc: Docbook-apps <docbook-apps at lists dot oasis-open dot org>
- Date: Tue, 13 Aug 2002 10:36:22 +0200 (CEST)
- Subject: Re: DOCBOOK-APPS: Double Side and FOP with 1.53
Togan,
Below is a stylesheet, that solves your problem. I don't know, why I
havn't though of this before, since it is a much cleaner solution, and you
do not have to copy and override Norms templates.
I suspect, this technique can also be used as a different solution to
Nicolas idea on fixing pagenumbering of components as described in:
http://list.oasis-open.org/archives/docbook-apps/200208/msg00081.html
and also to take Bob comment into account, see:
http://list.oasis-open.org/archives/docboo-apps/200208/msg00093.html
Regards
Jens
-------------- fo-post-for-fop.xsl ---------------------------
<?xml version="1.0"?>
<!--
This stylesheet is created for post-processing of FO result-trees intended for
delivery to FOP 0.20.4. This should temporary solve problems caused by wrong
or unimplemented features in FOP.
When using Saxon, this stylesheet can be automatically processed by adding the
attribute saxon:next-in-chain to the xsl:output element of your own
stylesheet.
E.g.
<xsl:output method="xml" indent="no"
saxon:next-in-chain="fo-post-for-fop.xsl"/>
N.B. Remember to attach the namespace declaration
xmlns:saxon="http://icl.com/saxon" to your stylesheet element
Copyright (c) 2002, Jens Stavnstrup/DDRE <js@ddre.dk>
-->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version='1.0'
exclude-result-prefixes="#default">
<!-- Copy everything -->
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<!-- ....................................................................
Problem: In DocBook XSL 1.53.0 Norm uses the basic conformance level
property initial-page-number to force components to break on
odd-pages instead of the previously used extended conformance
level property force-page-count.
Solution: Use the extended property force-page-count
.................................................................... -->
<xsl:template match="fo:page-sequence[@initial-page-number='auto-odd']">
<xsl:copy>
<xsl:apply-templates select="@*[name() != 'initial-page-number']"/>
<xsl:attribute name="force-page-count">end-on-even</xsl:attribute>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<!-- Put your own templates here -->
</xsl:stylesheet>
--------------------------------------------------------------
On Mon, 12 Aug 2002, Togan Muftuoglu wrote:
> Hi,
>
> I have tried with Saxon, Xalan using a custom style sheet using with
> parameters on the command line but with Fop 20.4 along with XSL
> stylesheets 1.53.0 I can not get a double sided print outpout.
>
> Is this something with the Stylesheets or with Fop ?
>
> --
>
> Togan Muftuoglu
>
Regards,
Jens
------------------------------------------------------------------------
Jens Stavnstrup Phone :
Danish Defence Research Establishment Voice : + 45 - 39 15 17 97
Ryvangs Alle 1 - P.O. Box 2715 Fax : + 45 - 39 29 15 33
DK - 2100 Copenhagen O. E-Mail (Internet) :
Denmark js@ddre.dk
------------------------------------------------------------------------