docbook-apps

Hello,
my last request had some substantial mistakes. The problem still exists
and a solution is not yet in sight. I´m afraid that I still need your
help.

We use Oxygen and DocBook to write and maintain our user manuals.
Since these manuals describe various software applications, we often
insert "buttons".
Until recently, these buttons were inserted as screen shots, taken from
the original application.

In the course of time, we realized that the effort maintaining the amount
of screens shots was to high, so we decided to add a new style to our XSL
style sheet to imitate the original buttons. Basically what we did is to
create a format for an inline "box" with a solid border.:

<xsl:template match="d:button">
<fo:inline background-color="#D3D3D3" color="#4B0082" font-family="Courier
New" font-weight="bold" text-align="start" border-style="solid"
border-width="thin" padding="1pt" >
<xsl:apply-templates/>
</fo:inline>
</xsl:template>

The expected result was a solid box to indicate that its content was a
"button":

---------
| Button |
---------

It worked out fine for the HTML output, as well as the editor View.

However, transforming to PDF results in

---------
| Button
---------

The right border is missing, and we can´t figure out why.
The strange thing is, it works when we replace the fo:inline by a
fo:block. Nevertheless, this is not a solution, since the button is
supposed to be an in-line element:


---------
Click on | Button | to ....
---------

The FO transformer is Saxon 6.5.5. The entire documentation, including the
transformation is done with Oxygen XML editor.



Thanks for your help,

Daniel Keyes




=======================================================
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
=======================================================

Hi Daniel

Sorry if this is a stupid question, but could the problem come from your
PDF viewer?

Sometimes I find that Adobe Acrobat does not display all thin borders
around a shaded area at 100% magnification. But they are there; you can
see them if you increase the magnification or if you print the page.

If this is the case making the border a little thicker may help. Try
border-width="1pt".

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 09:41, daniel.keyes@finaris.de wrote:

> Hello,
> my last request had some substantial mistakes. The problem still exists
> and a solution is not yet in sight. I´m afraid that I still need your help.
>
> We use Oxygen and DocBook to write and maintain our user manuals.
> Since these manuals describe various software applications, we often
> insert "buttons".
> Until recently, these buttons were inserted as screen shots, taken from
> the original application.
>
> In the course of time, we realized that the effort maintaining the
> amount of screens shots was to high, so we decided to add a new style to
> our XSL style sheet to imitate the original buttons. Basically what we
> did is to create a format for an inline "box" with a solid border.:
>
> <xsl:template match="d:button">
> <fo:inline background-color="#D3D3D3" color="#4B0082"
> font-family="Courier New" font-weight="bold" text-align="start"
> border-style="solid" border-width="thin" padding="1pt" >
> <xsl:apply-templates/>
> </fo:inline>
> </xsl:template>
>
> The expected result was a solid box to indicate that its content was a
> "button":
>
> ---------
> | Button |
> ---------
>
> It worked out fine for the HTML output, as well as the editor View.
>
> However, transforming to PDF results in
>
> ---------
> | Button
> ---------
>
> The right border is missing, and we can´t figure out why.
> The strange thing is, it works when we replace the fo:inline by a
> fo:block. Nevertheless, this is not a solution, since the button is
> supposed to be an in-line element:
>
>
> ---------
> Click on | Button | to ....
> ---------
>
> The FO transformer is Saxon 6.5.5. The entire documentation, including
> the transformation is done with Oxygen XML editor.
>
>
>
> Thanks for your help,
>
> Daniel Keyes
>
>
>
>
> =======================================================
> 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
> =======================================================

Hi Simon,

your question isn´t stupid at all. Adobe Acrobat has some problems
displaying thin borders or details. It really depends on the
magnification.

I tried your advice. The border is thicker, but the right border is still
missing. I checked it with Adobe Acrobat ( zooming in and out), as well as
simply printing a page.


Greetings

Daniel



From: "Dew, Simon" <Simon.Dew@sbdinc.com>
To: "docbook-apps@lists.oasis-open.org"
<docbook-apps@lists.oasis-open.org>,
Date: 12.10.2012 11:35
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 Daniel

Sorry if this is a stupid question, but could the problem come from your
PDF viewer?

Sometimes I find that Adobe Acrobat does not display all thin borders
around a shaded area at 100% magnification. But they are there; you can
see them if you increase the magnification or if you print the page.

If this is the case making the border a little thicker may help. Try
border-width="1pt".

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 09:41, daniel.keyes@finaris.de wrote:

> Hello,
> my last request had some substantial mistakes. The problem still exists
> and a solution is not yet in sight. I´m afraid that I still need your
help.
>
> We use Oxygen and DocBook to write and maintain our user manuals.
> Since these manuals describe various software applications, we often
> insert "buttons".
> Until recently, these buttons were inserted as screen shots, taken from
> the original application.
>
> In the course of time, we realized that the effort maintaining the
> amount of screens shots was to high, so we decided to add a new style to
> our XSL style sheet to imitate the original buttons. Basically what we
> did is to create a format for an inline "box" with a solid border.:
>
> <xsl:template match="d:button">
> <fo:inline background-color="#D3D3D3" color="#4B0082"
> font-family="Courier New" font-weight="bold" text-align="start"
> border-style="solid" border-width="thin" padding="1pt" >
> <xsl:apply-templates/>
> </fo:inline>
> </xsl:template>
>
> The expected result was a solid box to indicate that its content was a
> "button":
>
> ---------
> | Button |
> ---------
>
> It worked out fine for the HTML output, as well as the editor View.
>
> However, transforming to PDF results in
>
> ---------
> | Button
> ---------
>
> The right border is missing, and we can´t figure out why.
> The strange thing is, it works when we replace the fo:inline by a
> fo:block. Nevertheless, this is not a solution, since the button is
> supposed to be an in-line element:
>
>
> ---------
> Click on | Button | to ....
> ---------
>
> The FO transformer is Saxon 6.5.5. The entire documentation, including
> the transformation is done with Oxygen XML editor.
>
>
>
> Thanks for your help,
>
> Daniel Keyes
>
>
>
>
> =======================================================
> 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
> =======================================================

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




=======================================================
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
=======================================================

Hi Daniel

A couple of suggestions. Have you looked at the .fo file to see if the
borders are defined correctly? (I don't know Oxygen XML, but presumably
there's an option to keep the .fo file when you transform to PDF.)

Secondly, I just looked at your customisation more closely.

> <xsl:template match="d:button">

Shouldn't that be d:guibutton? As it is, this template won't match
anything, in which case the formatting that you're seeing must be coming
from somewhere else. Is there another template in your custom layer
which matches guibuttons?

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 10:47, daniel.keyes@finaris.de wrote:

> Hi Simon,
>
> your question isn´t stupid at all. Adobe Acrobat has some problems
> displaying thin borders or details. It really depends on the magnification.
>
> I tried your advice. The border is thicker, but the right border is
> still missing. I checked it with Adobe Acrobat ( zooming in and out), as
> well as simply printing a page.
>
>
> Greetings
>
> Daniel

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






From: "Dew, Simon" <Simon.Dew@sbdinc.com>
To: "docbook-apps@lists.oasis-open.org"
<docbook-apps@lists.oasis-open.org>,
Date: 12.10.2012 12:43
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 Daniel

A couple of suggestions. Have you looked at the .fo file to see if the
borders are defined correctly? (I don't know Oxygen XML, but presumably
there's an option to keep the .fo file when you transform to PDF.)

Secondly, I just looked at your customisation more closely.

> <xsl:template match="d:button">

Shouldn't that be d:guibutton? As it is, this template won't match
anything, in which case the formatting that you're seeing must be coming
from somewhere else. Is there another template in your custom layer
which matches guibuttons?

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 10:47, daniel.keyes@finaris.de wrote:

> Hi Simon,
>
> your question isn´t stupid at all. Adobe Acrobat has some problems
> displaying thin borders or details. It really depends on the
magnification.
>
> I tried your advice. The border is thicker, but the right border is
> still missing. I checked it with Adobe Acrobat ( zooming in and out), as
> well as simply printing a page.
>
>
> Greetings
>
> Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




=======================================================
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
=======================================================

Hi Daniel

I think you should check that the borders of your buttons are all
present and correct in the the .fo file.

I tried editing an .fo file by hand to include an inline with the same
attributes specified by your custom template. I used Apache FOP to
create a .pdf file from my .fo file. In the .pdf file, the borders were
all visible: a bit faint in Adobe Acrobat, but definitely there.

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 12/10/2012 13:37, daniel.keyes@finaris.de 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

On 10/12/2012 01:37 PM, daniel.keyes@finaris.de 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

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:



<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="docbook.xsl"/>

<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 <davep@dpawson.co.uk>
To: docbook-apps@lists.oasis-open.org,
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, daniel.keyes@finaris.de 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: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




=======================================================
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
=======================================================

Hi,
this is my xsl:
<xsl:template match="d:guibutton">
<fo:inline border-left="1pt solid gray"></fo:inline>
border-top="1pt solid gray"
border-bottom="2pt solid black"
border-right="2pt solid black"
vertical-align="middle">
<xsl:apply-imports></xsl:apply-imports>

</xsl:template>

This ist the xml:

<informalexample>
<para>Klicken Sie auf
<guibutton>
<accel>S</accel>peichern
</guibutton>
um die Änderungen zu übernehmen
</para>
<informalexample>

This will result in this (image)
[cid:image001.png@01CDABB2.DB8E8010]

And in this (fo):
<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">Klicken Sie auf
<fo:inline border-left="1pt solid gray" border-top="1pt solid gray" border-bottom="2pt solid black" border-right="2pt solid black" vertical-align="middle">
<fo:inline text-decoration="underline">S</fo:inline>peichern
</fo:inline>
<fo:block>
um die Änderungen zu übernehmen

We're using db5, rng, docbook-xsl-ns-1.76.1 with xsltproc and Apache-fop 1.0.

Maybe this can help you.

Regards
Dominic

Von: daniel.keyes@finaris.de [mailto:daniel.keyes@finaris.de]
Gesendet: Dienstag, 16. Oktober 2012 14:22
An: docbook-apps@lists.oasis-open.org
Betreff: 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:



<xsl:stylesheet></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="docbook.xsl"></xsl:import>

<xsl:template match="d:button">
<fo:inline background-color="#D3D3D3" border-style="solid" border-width="thin">
<xsl:apply-templates></xsl:apply-templates>
</fo:inline>
</xsl:template>





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 < /><mailto:davep@dpawson.co.uk>>
To: docbook-apps@lists.oasis-open.org<mailto:docbook-apps@lists.oasis-open.org>,
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, daniel.keyes@finaris.de<mailto:daniel.keyes@finaris.de> 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<http: www.dpawson.co.uk/="">

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org<mailto:docbook-apps-unsubscribe@lists.oasis-open.org>
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org<mailto:docbook-apps-help@lists.oasis-open.org>




=======================================================
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
=======================================================

</mailto:docbook-apps-help@lists.oasis-open.org></mailto:docbook-apps-unsubscribe@lists.oasis-open.org></http:></mailto:daniel.keyes@finaris.de></mailto:docbook-apps@lists.oasis-open.org></mailto:davep@dpawson.co.uk></fo:block></fo:block></informalexample></informalexample>

Hi Daniel

> - How did you (@Simon) manage to successfully transform our style to PDF?

I used Apache FOP 1.0. (http://xmlgraphics.apache.org/fop) to convert an
xsl-fo file containing an inline with your specified attributes.

Have you tried a different xsl-fo processor?
--
Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

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
bobs@sagehill.net


From: daniel.keyes@finaris.de
Sent: Tuesday, October 16, 2012 5:22 AM
To: docbook-apps@lists.oasis-open.org
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:



<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="docbook.xsl"/>

<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 <davep@dpawson.co.uk>
To: docbook-apps@lists.oasis-open.org,
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, daniel.keyes@finaris.de 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: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




=======================================================
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
=======================================================

Hi,
thanks for your help Bob!
At first, we first tried to run a transformation with fop 1.0. This didn´t
work, so we used fop1.1rc1.

fop1.1.rc1 is still a release candidate, but it works just fine for our
transformation. Each element / style is at its place and our PDFs finally
show the right border of our buttons.

We really don´t what it was, but it looks like the FOP of our Oxygen
version (13) couldn´t handle our style.

If anyone has the same problem: You can download the latest FOP version on
apache.org/dyn/closer.cgi/xmlgraphics/fop


Thanks for your help!


Greetings,
Daniel




From: "Bob Stayton" <bobs@sagehill.net>
To: <docbook-apps@lists.oasis-open.org>, <daniel.keyes@finaris.de>,
Date: 16.10.2012 20:18
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.



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
bobs@sagehill.net

From: daniel.keyes@finaris.de
Sent: Tuesday, October 16, 2012 5:22 AM
To: docbook-apps@lists.oasis-open.org
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:



<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="docbook.xsl"/>

<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 <davep@dpawson.co.uk>
To: docbook-apps@lists.oasis-open.org,
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, daniel.keyes@finaris.de 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: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




=======================================================
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
=======================================================


=======================================================
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
=======================================================

Hi Daniel,

Sorry for not jumping into this thread sooner, we are getting close to
the Oxygen 14.1 release so lots of work and testing to do :)

Indeed both Oxygen 13 and 14 come with Apache FOP 1.0 which seems to
have the bug you mentioned.
And indeed running the transformation with FOP 1.1 RC1 fixes this
problem (but it might break something else though being just a release
candidate).

In the Oxygen Preferences "XML/XSLT-FO-XQuery/FO Processors" page there
is a checkbox called "Enabled output to the built-in FOP" which shows
the entire output received from Apache FOP.

For example, running the Docbook XSLS 1.77.1 over my sample Docbook XML
file which contains a <note> produces some XSL-FO image references which
are not in URL format like:

> <fo:external-graphic width="auto" height="auto"
> content-width="36pt"
> src="url(D:\projects\eXml\frameworks/docbook/xsl/images/note.png)"
> />

This works with FOP 1.0 but the Apache FOP 1.1 RC1 seems to report
errors (and not load the note image anymore) like:

> SEVERE: Invalid property value encountered in src="url(D:\projects\eXml\frameworks/docbook/xsl/images/note.png)": org.apache.fop.fo.expr.PropertyException: Invalid URI specified (See position 1056:39)
> org.apache.fop.fo.expr.PropertyException: Invalid URI specified
> at org.apache.fop.fo.properties.URIProperty$Maker.make(URIProperty.java:142)
> at org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:413)
> at org.apache.fop.fo.PropertyList.addAttributesToList(PropertyList.java:321)
> at org.apache.fop.fo.FObj.processNode(FObj.java:122)
> at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:280)
> at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175)
> at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
> at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
> at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:300)
> at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:130)
> at org.apache.fop.cli.Main.startFOP(Main.java:177)
> at org.apache.fop.cli.Main.main(Main.java:208)

Also the latest FOP build seems to be failing in loading a lot of system
fonts:

> WARNING: Unable to load font file: file:/C:/Windows/FONTS/batang.ttc. Reason: java.lang.NullPointerException

Regards,
Radu

Radu Coravu
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 10/17/2012 1:59 PM, daniel.keyes@finaris.de wrote:
> Hi,
> thanks for your help Bob!
> At first, we first tried to run a transformation with fop 1.0. This
> didn´t work, so we used fop1.1rc1.
>
> fop1.1.rc1 is still a release candidate, but it works just fine for our
> transformation. Each element / style is at its place and our PDFs
> finally show the right border of our buttons.
>
> We really don´t what it was, but it looks like the FOP of our Oxygen
> version (13) couldn´t handle our style.
>
> If anyone has the same problem: You can download the latest FOP version
> on apache.org/dyn/closer.cgi/xmlgraphics/fop
> <http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop>
>
>
> Thanks for your help!
>
>
> Greetings,
> Daniel
>
>
>
>
> From: "Bob Stayton" <bobs@sagehill.net>
> To: <docbook-apps@lists.oasis-open.org>, <daniel.keyes@finaris.de>,
> Date: 16.10.2012 20:18
> 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.
> ------------------------------------------------------------------------
>
>
>
> 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_
> __bobs@sagehill.net_ <mailto:bobs@sagehill.net>
>
> *From:* _daniel.keyes@finaris.de_ <mailto:daniel.keyes@finaris.de>
> *Sent:* Tuesday, October 16, 2012 5:22 AM
> *To:* _docbook-apps@lists.oasis-open.org_
> <mailto:docbook-apps@lists.oasis-open.org>
> *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:
>
>
>
> <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="docbook.xsl"/>
>
> <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 <davep@dpawson.co.uk>
> To: docbook-apps@lists.oasis-open.org,
> 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, daniel.keyes@finaris.de 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_ <http://www.dpawson.co.uk/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>
>
>
>
> =======================================================
> 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
> =======================================================
>
>
> =======================================================
> 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
> =======================================================