I did some testing and found that the problem seems to be the
FOP that ships with Oxygen 14. Here is what I did.
I copied your customization and configured an Oxygen 14
transformation to apply the customized stylesheet *and* run the built-in FOP
processor. For the Transformation Output tab, I said to Prompt for
filename so I could keep track of the output. That PDF file duplicated the
result you were seeing with the missing right border.
Then I changed the transformation to just produce the FO
output. When I examined the FO output file, it looked ok. When
I subsequently processed that saved FO file with the FOP 1.0 I had
installed separately on my system, the output showed the right
border.
Then I changed the Oxygen configuration using Options >
Preferences > XML > XSLT-FO-XQuery > FO Processors. Under Apache
FOP, I selected "Use other Apache FOP", and browsed to the fop.bat file that I
had installed separately on my system. I saved that configuration, and
when I ran the transformation, the output showed the right border.
So I concluded that the version of FOP 1.0 that ships with
Oxygen 14 seems to be the source of this problem. Oddly, I compared the
fop.jar in Oxygen 14 to the fop.jar in my installation, and they are
identical. So I cannot explain why this happens. But if you download
FOP 1.0, install it, and point Oxygen 14 to use it, then you should get the
right border.
And let Oxygen Support know about this (you can forward this
information if you like).
Bob Stayton
Sagehill Enterprises
From:
Sent: Tuesday, October 16, 2012 5:22 AM
To:
Subject: Re: [docbook-apps] PDF transformation: Why is the right
border of my inline "box" missing when I transform to PDF. It works for HTML and
Oxygen XML Editor.
Hi,
we tried to come up with a solution, but it didn´t work.
After all, we considered that it would be best to
reset the entire schema and stylesheet back to "factory settings". Starting from
scratch seemed to be a good idea to find the error (we created a backup). All
that remained was Oxygens supplied version of Docbook 5.0.
We added our button style to the styelsheet:
<?xml version="1.0"
encoding="UTF-8"?>
<xsl:stylesheet
xml:lang="de"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:d = "http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:exsl="http://exslt.org/common"
exclude-result-prefixes="d"
version="1.0">
<xsl:import
href=""/>
<xsl:template
match="d:button">
<fo:inline background-color="#D3D3D3"
border-style="solid" border-width="thin" >
<xsl:apply-templates/>
</fo:inline>
</xsl:template>
</xsl:stylesheet>
as
well as a matching counterpart to the schema docbookxi.rng. Everything else
remained the same.
However, the borders
were still missing when transforming to PDF
After all, the bottom line is that:
- Except of the border, our custom style is working just fine.
There is a link between stylesheet and schema
- Its not Adobe Reader (Zoom etc.)
- Its not our stylesheet or schema
So what´s the problem?
- Is it
possible that Oxygen and its FO processor cannot handle our custom style? I know
you told me that it´s propably not Saxxon, but is possible?
- How did you (@Simon) manage to successfully transform our
style to PDF?
- Is is possible that Oxygen
supplied an old or at least buggy version of DocBook 5.0?
- How is it possible that our styles works if we use
fo:block instead? We have several "boxes" in our manuals and their all rendered
correctly.
Thanks for your
help.
Greetings,
Daniel Keyes
From:
DaveP
<>
To: ,
Date:
12.10.2012 16:04
Subject:
Re: [docbook-apps] PDF transformation:
Why is the right border of my inline "box" missing when I transform to PDF. It
works for HTML and Oxygen XML Editor.
On 10/12/2012 01:37 PM,
wrote:
> Hi Simon,
>
> we have implemented some custom styles
in our style sheet and schema, so
> d:button shuld/ does
match.
>
> As mentioned before, it is a custom style. It works for
HTML and our
> Oxygen XML Editor, but not for PDF.
>
> Is it
possible that our FO processor, i.e. Saxxon, does not
work?
>
>
> Daniel
No Daniel, very unlikely. Saxon
is probably the most conformant
and well tested
processor.
regards
--
Dave Pawson
XSLT XSL-FO
FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To
unsubscribe, e-mail:
For
additional commands, e-mail:
=======================================================
Disclaimer
The
information contained in this e - mail and any attachments
( together the
"message") is intended for the addressee only and may
contain confidential
and/or privileged information. If you have received
the message by mistake
please delete it and notify the sender and do
not copy or distribute it or
disclose its contents to anyone.
FINARIS Financial Software Partner
GmbH
Sömmerringstr. 23, 60322 Frankfurt/Main, Germany
Registered at
Frankfurt/Main, HRB 52873
Managing Directors:
Dipl. Inf. Hermann
Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner
Märkl
=======================================================
