[jira] [Commented] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720268#comment-17720268 ] Glenn Adams commented on FOP-3132: -- Thanks! > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[
https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718690#comment-17718690
]
Glenn Adams commented on FOP-3132:
--
I mean use {{-release 8}} when compiling with Java 11,
> Link against Java 8 API
> ---
>
> Key: FOP-3132
> URL: https://issues.apache.org/jira/browse/FOP-3132
> Project: FOP
> Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
>
> As a user I want to compile fop with java > 8 and run with java 8 without
> error
> We want to be Java 8 compatible, if we compile fop with java 11, you would
> currently get a error when runtime is java 8. We currently compile with java
> 8, but it would be good to be able to use java 11 without a risk of issues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[
https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718639#comment-17718639
]
Glenn Adams commented on FOP-3132:
--
I believe this could have been solved by using {{-release 8}} instead of
{{-source}} and {{-target}}. See
https://www.baeldung.com/java-compiler-release-option for examples.
> Link against Java 8 API
> ---
>
> Key: FOP-3132
> URL: https://issues.apache.org/jira/browse/FOP-3132
> Project: FOP
> Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
>
> As a user I want to compile fop with java > 8 and run with java 8 without
> error
> We want to be Java 8 compatible, if we compile fop with java 11, you would
> currently get a error when runtime is java 8. We currently compile with java
> 8, but it would be good to be able to use java 11 without a risk of issues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718612#comment-17718612 ] Glenn Adams commented on FOP-3132: -- You should be able to compile with Java 11 but specify the target as Java 8, yes? That way you produce byte code that is compatible with Java 8. Can you comment on the reason for the source changes in this commit? They don't seem related to the description of this issue. > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-299) Cells border hidden by cells background
[
https://issues.apache.org/jira/browse/FOP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-299.
---
Resolution: Duplicate
> Cells border hidden by cells background
> ---
>
> Key: FOP-299
> URL: https://issues.apache.org/jira/browse/FOP-299
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 0.20.3
> Environment: Operating System: Linux
> Platform: PC
>Reporter: funkytow
>Assignee: fop-dev
>
> FO Input
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
> page-height="210mm" margin-left="1cm" margin-right="1cm" margin-top="1cm"
> margin-bottom="1cm">
>
>
>
>
>
>
>
>
>
>
> Don't care
>
>
>
>
> Border bottom 1
>
>
>
>
> Border bottom 2
>
>
>
>
> Don't care
>
>
>
>
> Border top 1
>
>
>
>
> Border top 2
>
>
>
>
> Don't care
>
>
>
>
>
>
>
> {code}
> When this FO is traformed into PDF, you have a bug with borders:
> the bottom border of the cell "Border bottom 1" has disappeared,
> hidden by the background of the cell "Border bottom 2".
> But if you have a look at the top border of the cell "Border top 2", it did
> not
> disappear
> because of the background of the cell "Border top 1".
> In fact, background in cells make any adjacent border-bottom to disappear.
> I am afraid it is the same with border-left.
> Note:
> Add the 'background-color="lightgray"'
> attribute to the very last "Dont'care" cell.
> Then you see that the background hides a part of the border surrounding the
> table.
> Note2: add the attribute 'background-color="lightgray"'
> to the tag. You will see that the background does not hide the borders
> of the table,but is one pixel too large in the lower part.
> PPS/ BTW, why does xpdf/acroread displays borders not always with the same
> size, but
> the printed version is okay?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-299) Cells border hidden by cells background
[
https://issues.apache.org/jira/browse/FOP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-299:
Description:
FO Input
{code}
http://www.w3.org/1999/XSL/Format;>
Don't care
Border bottom 1
Border bottom 2
Don't care
Border top 1
Border top 2
Don't care
{code}
When this FO is traformed into PDF, you have a bug with borders:
the bottom border of the cell "Border bottom 1" has disappeared,
hidden by the background of the cell "Border bottom 2".
But if you have a look at the top border of the cell "Border top 2", it did not
disappear
because of the background of the cell "Border top 1".
In fact, background in cells make any adjacent border-bottom to disappear.
I am afraid it is the same with border-left.
Note:
Add the 'background-color="lightgray"'
attribute to the very last "Dont'care" cell.
Then you see that the background hides a part of the border surrounding the
table.
Note2: add the attribute 'background-color="lightgray"'
to the tag. You will see that the background does not hide the borders
of the table,but is one pixel too large in the lower part.
PPS/ BTW, why does xpdf/acroread displays borders not always with the same
size, but
the printed version is okay?
was:
--- cut here ---
http://www.w3.org/1999/XSL/Format;>
Don't care
Border bottom 1
Border bottom 2
Don't care
Border top 1
Border top 2
Don't care
--- cut here ---
When this FO is traformed into PDF, you have a bug with borders:
the bottom border of the cell "Border bottom 1" has disappeared,
hidden by the background of the cell "Border bottom 2".
But if you have a look at the top border of the cell "Border top 2", it did not
disappear
because of the background of the cell "Border top 1".
In fact, background in cells make any adjacent border-bottom to disappear.
I am afraid it is the same with border-left.
Note:
Add the 'background-color="lightgray"'
attribute to the very last "Dont'care" cell.
Then you see that the background hides a part of the border surrounding the
table.
Note2: add the attribute 'background-color="lightgray"'
to the tag. You will see that the background does not hide the borders
of the table,but is one pixel too large in the lower part.
PPS/ BTW, why does xpdf/acroread displays borders not always with the same
size, but
the printed version is okay?
> Cells border hidden by cells background
> ---
>
> Key: FOP-299
> URL: https://issues.apache.org/jira/browse/FOP-299
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 0.20.3
> Environment: Operating System: Linux
> Platform: PC
>Reporter: funkytow
>Assignee: fop-dev
>
> FO Input
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
> page-height="210mm" margin-left="1cm" margin-right="1cm" margin-top="1cm"
> margin-bottom="1cm">
>
>
>
>
>
>
>
>
>
>
> Don't care
>
>
>
>
> Border bottom 1
>
>
>
>
> Border bottom 2
>
>
>
>
> Don't care
>
>
>
>
> Border top 1
>
>
>
>
> Border top 2
>
>
>
>
> Don't care
>
>
>
>
>
>
>
> {code}
> When this FO is traformed into PDF, you have a bug with borders:
> the bottom border of the cell "Border bottom 1" has disappeared,
> hidden by the background of the cell "Border bottom 2".
> But if you have a look at the top border of the cell "Border top 2", it did
> not
> disappear
> because of the background of the cell "Border top 1".
> In fact, background in cells make any adjacent border-bottom to disappear.
> I am afraid it is the same with border-left.
> Note:
> Add the 'background-color="lightgray"'
> attribute to the very last "Dont'care" cell.
> Then you see that the background hides a part of the border surrounding the
> table.
> Note2: add the attribute 'background-color="lightgray"'
> to the tag. You will see that the background does not hide the borders
> of the table,but is one pixel too large in the lower part.
> PPS/ BTW, why does xpdf/acroread displays borders not always with the same
> size, but
> the printed version is okay?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (FOP-299) Cells border hidden by cells background
[ https://issues.apache.org/jira/browse/FOP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-299: - > Cells border hidden by cells background > --- > > Key: FOP-299 > URL: https://issues.apache.org/jira/browse/FOP-299 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.3 > Environment: Operating System: Linux > Platform: PC >Reporter: funkytow >Assignee: fop-dev > > --- cut here --- > > http://www.w3.org/1999/XSL/Format;> > > page-height="210mm" margin-left="1cm" margin-right="1cm" margin-top="1cm" > margin-bottom="1cm"> > > > > > > > > > > > Don't care > > > > > Border bottom 1 > > > > > Border bottom 2 > > > > > Don't care > > > > > Border top 1 > > > > > Border top 2 > > > > > Don't care > > > > > > > > --- cut here --- > When this FO is traformed into PDF, you have a bug with borders: > the bottom border of the cell "Border bottom 1" has disappeared, > hidden by the background of the cell "Border bottom 2". > But if you have a look at the top border of the cell "Border top 2", it did > not > disappear > because of the background of the cell "Border top 1". > In fact, background in cells make any adjacent border-bottom to disappear. > I am afraid it is the same with border-left. > Note: > Add the 'background-color="lightgray"' > attribute to the very last "Dont'care" cell. > Then you see that the background hides a part of the border surrounding the > table. > Note2: add the attribute 'background-color="lightgray"' > to the tag. You will see that the background does not hide the borders > of the table,but is one pixel too large in the lower part. > PPS/ BTW, why does xpdf/acroread displays borders not always with the same > size, but > the printed version is okay? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-290) markers are completely broken (as far as I can tell)
[
https://issues.apache.org/jira/browse/FOP-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-290.
---
Resolution: Duplicate
> markers are completely broken (as far as I can tell)
>
>
> Key: FOP-290
> URL: https://issues.apache.org/jira/browse/FOP-290
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 0.20.3
> Environment: Operating System: All
> Platform: PC
>Reporter: Chuck
>Assignee: fop-dev
>
> [INFO]: FOP 0.20.3rc
> [INFO]: building formatting object tree
> [ERROR]: null
> Here is the simple test case. All it contains is a marker tag
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
> master-name="simple"
> margin-top="1in"
> margin-right="1in"
> margin-left="1in"
> margin-bottom="1in">
>
>
>
>
>
> One
> this is a test this is a test this is a test this is a test this is a test
> this
> is a test this is a test this is a test
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-290) markers are completely broken (as far as I can tell)
[
https://issues.apache.org/jira/browse/FOP-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-290:
Description:
[INFO]: FOP 0.20.3rc
[INFO]: building formatting object tree
[ERROR]: null
Here is the simple test case. All it contains is a marker tag
{code}
http://www.w3.org/1999/XSL/Format;>
One
this is a test this is a test this is a test this is a test this is a test this
is a test this is a test this is a test
{code}
was:
[INFO]: FOP 0.20.3rc
[INFO]: building formatting object tree
[ERROR]: null
Here is the simple test case. All it contains is a marker tag
http://www.w3.org/1999/XSL/Format;>
One
this is a test this is a test this is a test this is a test this is a test this
is a test this is a test this is a test
> markers are completely broken (as far as I can tell)
>
>
> Key: FOP-290
> URL: https://issues.apache.org/jira/browse/FOP-290
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 0.20.3
> Environment: Operating System: All
> Platform: PC
>Reporter: Chuck
>Assignee: fop-dev
>
> [INFO]: FOP 0.20.3rc
> [INFO]: building formatting object tree
> [ERROR]: null
> Here is the simple test case. All it contains is a marker tag
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
> master-name="simple"
> margin-top="1in"
> margin-right="1in"
> margin-left="1in"
> margin-bottom="1in">
>
>
>
>
>
> One
> this is a test this is a test this is a test this is a test this is a test
> this
> is a test this is a test this is a test
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (FOP-290) markers are completely broken (as far as I can tell)
[ https://issues.apache.org/jira/browse/FOP-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-290: - > markers are completely broken (as far as I can tell) > > > Key: FOP-290 > URL: https://issues.apache.org/jira/browse/FOP-290 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.20.3 > Environment: Operating System: All > Platform: PC >Reporter: Chuck >Assignee: fop-dev > > [INFO]: FOP 0.20.3rc > [INFO]: building formatting object tree > [ERROR]: null > Here is the simple test case. All it contains is a marker tag > > http://www.w3.org/1999/XSL/Format;> > > master-name="simple" > margin-top="1in" > margin-right="1in" > margin-left="1in" > margin-bottom="1in"> > > > > > > One > this is a test this is a test this is a test this is a test this is a test > this > is a test this is a test this is a test > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-261) hyphenation does not work with
[
https://issues.apache.org/jira/browse/FOP-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-261.
---
Resolution: Cannot Reproduce
> hyphenation does not work with
> -
>
> Key: FOP-261
> URL: https://issues.apache.org/jira/browse/FOP-261
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.5
> Environment: Operating System: All
> Platform: PC
>Reporter: Teemu Talja
>Assignee: fop-dev
>
> Hi
> I am generating PDF from a xml and xsl file, first to FO,
> then to PDF. I am using XSLT.
> {code}
> language="fi" hyphenate="true">
> kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi
>
>
> {code}
> in the xml document I have the same
> line "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
> inside the tag lahetyksen_tiedot/paino_yhteensa.
> If I comment out the line before instead of the one that is now
> inside a comment, the
> text "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
> shows up differently: without any hyphenation.
> there is this bug reported with problems with a single word inside
> a block, I tried to put additional words to the block too but it
> did not help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-261) hyphenation does not work with
[
https://issues.apache.org/jira/browse/FOP-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-261:
Description:
Hi
I am generating PDF from a xml and xsl file, first to FO,
then to PDF. I am using XSLT.
{code}
kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi
{code}
in the xml document I have the same
line "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
inside the tag lahetyksen_tiedot/paino_yhteensa.
If I comment out the line before instead of the one that is now
inside a comment, the
text "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
shows up differently: without any hyphenation.
there is this bug reported with problems with a single word inside
a block, I tried to put additional words to the block too but it
did not help.
was:
Hi
I am generating PDF from a xml and xsl file, first to FO,
then to PDF. I am using XSLT.
kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi
in the xml document I have the same
line "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
inside the tag lahetyksen_tiedot/paino_yhteensa.
If I comment out the line before instead of the one that is now
inside a comment, the
text "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
shows up differently: without any hyphenation.
there is this bug reported with problems with a single word inside
a block, I tried to put additional words to the block too but it
did not help.
> hyphenation does not work with
> -
>
> Key: FOP-261
> URL: https://issues.apache.org/jira/browse/FOP-261
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.5
> Environment: Operating System: All
> Platform: PC
>Reporter: Teemu Talja
>Assignee: fop-dev
>
> Hi
> I am generating PDF from a xml and xsl file, first to FO,
> then to PDF. I am using XSLT.
> {code}
> language="fi" hyphenate="true">
> kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi
>
>
> {code}
> in the xml document I have the same
> line "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
> inside the tag lahetyksen_tiedot/paino_yhteensa.
> If I comment out the line before instead of the one that is now
> inside a comment, the
> text "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi"
> shows up differently: without any hyphenation.
> there is this bug reported with problems with a single word inside
> a block, I tried to put additional words to the block too but it
> did not help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (FOP-261) hyphenation does not work with
[ https://issues.apache.org/jira/browse/FOP-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-261: - > hyphenation does not work with > - > > Key: FOP-261 > URL: https://issues.apache.org/jira/browse/FOP-261 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: Teemu Talja >Assignee: fop-dev > > Hi > I am generating PDF from a xml and xsl file, first to FO, > then to PDF. I am using XSLT. > language="fi" hyphenate="true"> > kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi > > > in the xml document I have the same > line "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi" > inside the tag lahetyksen_tiedot/paino_yhteensa. > If I comment out the line before instead of the one that is now > inside a comment, the > text "kuusikymmentäkuusituhattakolmesataaneljäkymmentäyksi" > shows up differently: without any hyphenation. > there is this bug reported with problems with a single word inside > a block, I tried to put additional words to the block too but it > did not help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-258) keep-together.within-page="always" not functioning
[ https://issues.apache.org/jira/browse/FOP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-258. --- Resolution: Duplicate move inlined code in description to attachment > keep-together.within-page="always" not functioning > --- > > Key: FOP-258 > URL: https://issues.apache.org/jira/browse/FOP-258 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.15 > Environment: Operating System: other > Platform: All >Reporter: suresh kannaian >Assignee: fop-dev >Priority: Blocker > Attachments: fop-258-description-with-code.txt > > > See attachment fop-258-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-258) keep-together.within-page="always" not functioning
[ https://issues.apache.org/jira/browse/FOP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-258: Description: See attachment fop-258-description-with-code.txt (was: http://www.w3.org/1999/XSL/Transform; xmlns:fo="http://www.w3.org/1999/XSL/Format;> http://www.w3.org/1999/XSL/Format;> Page Advanced Paragraph Attributes - Page Break Control This text tests 'keep-together.within- page' attribute. Subsequent blocks Following paragraphs all have 'keep- together.within-page' attribute set to "always". Therefore, page breaks may occur only between paragraphs with different colors. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks. Page breaks should not split blocks.
[jira] [Updated] (FOP-258) keep-together.within-page="always" not functioning
[ https://issues.apache.org/jira/browse/FOP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-258: Attachment: fop-258-description-with-code.txt > keep-together.within-page="always" not functioning > --- > > Key: FOP-258 > URL: https://issues.apache.org/jira/browse/FOP-258 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.15 > Environment: Operating System: other > Platform: All >Reporter: suresh kannaian >Assignee: fop-dev > Attachments: fop-258-description-with-code.txt > > > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > > http://www.w3.org/1999/XSL/Format;> > >height="11in" page-width="8.26in" margin-top="0.5in" margin-bottom="0.5in" > margin-left="34px" margin-right="36px"> >margin-bottom=".5in"/> > > > > > > >size="10px" font-family="sans-serif" line-height="10px">Page > > > > > > space- > before="18pt" space-before.conditionality="discard" space-after="6pt" > keep-with- > next.within-column="always" keep-together.within-column="always" text- > align="center" padding="3pt" background-color="silver"> Advanced Paragraph > Attributes - Page Break Control > > This text tests 'keep-together.within- > page' attribute. > > keep-with-next.within-column="always" keep-together.within-column="always" > text- > align="center">Subsequent > blocks > > Following paragraphs all have 'keep- > together.within-page' > attribute set to "always". > Therefore, page breaks > may occur only between paragraphs with different colors. > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. >
[jira] [Reopened] (FOP-258) keep-together.within-page="always" not functioning
[ https://issues.apache.org/jira/browse/FOP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-258: - > keep-together.within-page="always" not functioning > --- > > Key: FOP-258 > URL: https://issues.apache.org/jira/browse/FOP-258 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.15 > Environment: Operating System: other > Platform: All >Reporter: suresh kannaian >Assignee: fop-dev > > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > > http://www.w3.org/1999/XSL/Format;> > >height="11in" page-width="8.26in" margin-top="0.5in" margin-bottom="0.5in" > margin-left="34px" margin-right="36px"> >margin-bottom=".5in"/> > > > > > > >size="10px" font-family="sans-serif" line-height="10px">Page > > > > > > space- > before="18pt" space-before.conditionality="discard" space-after="6pt" > keep-with- > next.within-column="always" keep-together.within-column="always" text- > align="center" padding="3pt" background-color="silver"> Advanced Paragraph > Attributes - Page Break Control > > This text tests 'keep-together.within- > page' attribute. > > keep-with-next.within-column="always" keep-together.within-column="always" > text- > align="center">Subsequent > blocks > > Following paragraphs all have 'keep- > together.within-page' > attribute set to "always". > Therefore, page breaks > may occur only between paragraphs with different colors. > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > > > > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. > > Page breaks should not split blocks. >
[jira] [Closed] (FOP-71) text color not working after a page break
[
https://issues.apache.org/jira/browse/FOP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-71.
--
Resolution: Fixed
wrap code in description
> text color not working after a page break
> -
>
> Key: FOP-71
> URL: https://issues.apache.org/jira/browse/FOP-71
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.5
> Environment: Operating System: All
> Platform: PC
>Reporter: Dave Ford
>Assignee: fop-dev
>Priority: Blocker
>
> FO Input
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
>
>
>
>
>
>
> This is red
> This should be red
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-71) text color not working after a page break
[
https://issues.apache.org/jira/browse/FOP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-71:
---
Description:
FO Input
{code}
http://www.w3.org/1999/XSL/Format;>
This is red
This should be red
{code}
was:
http://www.w3.org/1999/XSL/Format;>
This is red
This should be red
Priority: Blocker
> text color not working after a page break
> -
>
> Key: FOP-71
> URL: https://issues.apache.org/jira/browse/FOP-71
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.5
> Environment: Operating System: All
> Platform: PC
>Reporter: Dave Ford
>Assignee: fop-dev
>Priority: Blocker
>
> FO Input
> {code}
>
> http://www.w3.org/1999/XSL/Format;>
>
>
>
>
>
>
>
> This is red
> This should be red
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (FOP-71) text color not working after a page break
[ https://issues.apache.org/jira/browse/FOP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-71: > text color not working after a page break > - > > Key: FOP-71 > URL: https://issues.apache.org/jira/browse/FOP-71 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: Dave Ford >Assignee: fop-dev > > > http://www.w3.org/1999/XSL/Format;> > > > > > > > > This is red > This should be red > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2814) Table header is rendered on bottom when table is put inside fo:inline
[
https://issues.apache.org/jira/browse/FOP-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2814:
-
Attachment: fop-2814-description-with-code.txt
> Table header is rendered on bottom when table is put inside fo:inline
> -
>
> Key: FOP-2814
> URL: https://issues.apache.org/jira/browse/FOP-2814
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.0, 2.1, 2.2, 2.3
>Reporter: Sasa Vilic
>Priority: Major
> Attachments: fop-2814-description-with-code.txt
>
>
> When we put table inside {{}} its header is rendered
> (pdf) at bottom.
> Example file
> See attachment fop-2814-description-with-code.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FOP-2776) NoSuchElementException for list changing ipd
[ https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2776. Resolution: Fixed move inlined code from description and comment into attachments > NoSuchElementException for list changing ipd > > > Key: FOP-2776 > URL: https://issues.apache.org/jira/browse/FOP-2776 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: 2.3 > > Attachments: fop-2776-comment-with-code.txt, > fop-2776-description-with-code.txt, test.fo > > > See attachment fop-2776-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2776) NoSuchElementException for list changing ipd
[ https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2776: - Attachment: fop-2776-comment-with-code.txt > NoSuchElementException for list changing ipd > > > Key: FOP-2776 > URL: https://issues.apache.org/jira/browse/FOP-2776 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: 2.3 > > Attachments: fop-2776-comment-with-code.txt, > fop-2776-description-with-code.txt, test.fo > > > See attachment fop-2776-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-2776) NoSuchElementException for list changing ipd
[
https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756056#comment-16756056
]
Glenn Adams edited comment on FOP-2776 at 4/29/23 8:37 PM:
---
The fix introduced a new bug. If you have two list, one nested into another,
the nested list jumps to the next page instead of spreading on two pages. It is
like the parent list item has a keep-together property set on it. Removing the
code added by this fix solves the problem.
Here is a file to test with.
The item with the number 15 from the parent list item moves on the second page,
together with the nested list. In FOP 2.2 the page breaking was done between
the items of the nested list.
See attachment fop-2776-comment-with-code.txt
was (Author: dc33):
The fix introduced a new bug. If you have two list, one nested into another,
the nested list jumps to the next page instead of spreading on two pages. It is
like the parent list item has a keep-together property set on it. Removing the
code added by this fix solves the problem.
Here is a file to test with.
The item with the number 15 from the parent list item moves on the second page,
together with the nested list. In FOP 2.2 the page breaking was done between
the items of the nested list.
{code}
http://www.w3.org/1999/XSL/Format;>
Sample FO document
1.
outer
2.
outer
3.
outer
4.
outer
5.
outer
6.
outer
7.
outer
8.
outer
9.
outer
10.
outer
11.
outer
12.
outer
13.
outer
14.
outer
15.
Now
a nested long list:
1.
inner
2.
inner
[jira] [Updated] (FOP-2776) NoSuchElementException for list changing ipd
[ https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2776: - Attachment: fop-2776-description-with-code.txt > NoSuchElementException for list changing ipd > > > Key: FOP-2776 > URL: https://issues.apache.org/jira/browse/FOP-2776 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: 2.3 > > Attachments: fop-2776-description-with-code.txt, test.fo > > > See attachment fop-2776-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2776) NoSuchElementException for list changing ipd
[ https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2776: - Description: See attachment fop-2776-description-with-code.txt (was: fop test.fo out.pdf java.util.NoSuchElementException at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) at org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132)) > NoSuchElementException for list changing ipd > > > Key: FOP-2776 > URL: https://issues.apache.org/jira/browse/FOP-2776 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: 2.3 > > Attachments: test.fo > > > See attachment fop-2776-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (FOP-2776) NoSuchElementException for list changing ipd
[ https://issues.apache.org/jira/browse/FOP-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-2776: -- > NoSuchElementException for list changing ipd > > > Key: FOP-2776 > URL: https://issues.apache.org/jira/browse/FOP-2776 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: 2.3 > > Attachments: test.fo > > > fop test.fo out.pdf > > java.util.NoSuchElementException > at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) > at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) > at > org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-2253) Build Failure on Mageia Linux Cauldron (what will be Mageia 4)
[ https://issues.apache.org/jira/browse/FOP-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2253. Resolution: Won't Fix move inlined code from description to attachment > Build Failure on Mageia Linux Cauldron (what will be Mageia 4) > -- > > Key: FOP-2253 > URL: https://issues.apache.org/jira/browse/FOP-2253 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.1 > Environment: Mageia Linux 3 Cauldron x86-64 >Reporter: Shlomi Fish >Priority: Major > Attachments: fop-2253-description-with-code.txt > > > When I run the build on Mageia Linux 3 x86-64 I get these build problems: > See attachment fop-2253-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2253) Build Failure on Mageia Linux Cauldron (what will be Mageia 4)
[ https://issues.apache.org/jira/browse/FOP-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2253: - Attachment: fop-2253-description-with-code.txt > Build Failure on Mageia Linux Cauldron (what will be Mageia 4) > -- > > Key: FOP-2253 > URL: https://issues.apache.org/jira/browse/FOP-2253 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.1 > Environment: Mageia Linux 3 Cauldron x86-64 >Reporter: Shlomi Fish >Priority: Major > Attachments: fop-2253-description-with-code.txt > > > When I run the build on Mageia Linux 3 x86-64 I get these build problems: > See attachment fop-2253-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2253) Build Failure on Mageia Linux Cauldron (what will be Mageia 4)
[
https://issues.apache.org/jira/browse/FOP-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2253:
-
Description:
When I run the build on Mageia Linux 3 x86-64 I get these build problems:
See attachment fop-2253-description-with-code.txt
was:
When I run the build on Mageia Linux 3 x86-64 I get these build problems:
creating package list
processing package fop-1.1-%mkrel 1
building binary packages
Executing(%prep): /bin/sh -e
/home/shlomif/Download/unpack/Mageia/fop/BUILDROOT/rpm-tmp.7CWPCz
+ umask 022
+ cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
+ '[' 1 -eq 1 ']'
+ '[' 1 -eq 1 ']'
+ '[' 1 -eq 1 ']'
+ cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
+ rm -rf fop-1.1
+ /usr/bin/gzip -dc
/home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-1.1-src.tar.gz
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd fop-1.1
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'Patch #0 (fop-1.0-manifest.patch):'
Patch #0 (fop-1.0-manifest.patch):
+ /usr/bin/cat
/home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-1.0-manifest.patch
+ /usr/bin/patch -p1 -b --suffix .mani-patch --fuzz=0
patching file build.xml
patching file fop.mf
+ echo 'Patch #1 (fop-main.patch):'
Patch #1 (fop-main.patch):
+ /usr/bin/cat /home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-main.patch
+ /usr/bin/patch -p0 -b --suffix .main-patch --fuzz=0
patching file src/java/org/apache/fop/cli/Main.java
Hunk #1 succeeded at 204 (offset 11 lines).
+ find -name '*.class' -exec rm -f '{}' ';'
+ find -name '*.jar' -exec rm -f '{}' ';'
+ sed -i -e 's|1.4|1.5|g' build.xml
+ ln -s /usr/share/java/qdox.jar lib/build/qdox.jar
+ unzip -q
/home/shlomif/Download/unpack/Mageia/fop/SOURCES/offo-hyphenation_v2.0.zip
+ mv offo-hyphenation/hyph/af.xml offo-hyphenation/hyph/as.xml
offo-hyphenation/hyph/bg.xml offo-hyphenation/hyph/bn.xml
offo-hyphenation/hyph/ca.xml offo-hyphenation/hyph/cop.xml
offo-hyphenation/hyph/cs.xml offo-hyphenation/hyph/cy.xml
offo-hyphenation/hyph/da.xml offo-hyphenation/hyph/de_1901.xml
offo-hyphenation/hyph/de_CH.xml offo-hyphenation/hyph/de.xml
offo-hyphenation/hyph/el_Polyton.xml offo-hyphenation/hyph/el.xml
offo-hyphenation/hyph/en_GB.xml offo-hyphenation/hyph/en.xml
offo-hyphenation/hyph/eo.xml offo-hyphenation/hyph/es.xml
offo-hyphenation/hyph/et.xml offo-hyphenation/hyph/eu.xml
offo-hyphenation/hyph/fi.xml offo-hyphenation/hyph/fr.xml
offo-hyphenation/hyph/ga.xml offo-hyphenation/hyph/gl.xml
offo-hyphenation/hyph/grc.xml offo-hyphenation/hyph/gu.xml
offo-hyphenation/hyph/hi.xml offo-hyphenation/hyph/hr.xml
offo-hyphenation/hyph/hsb.xml offo-hyphenation/hyph/hy.xml
offo-hyphenation/hyph/ia.xml offo-hyphenation/hyph/id.xml
offo-hyphenation/hyph/is.xml offo-hyphenation/hyph/it.xml
offo-hyphenation/hyph/kmr.xml offo-hyphenation/hyph/kn.xml
offo-hyphenation/hyph/la.xml offo-hyphenation/hyph/lo.xml
offo-hyphenation/hyph/lt.xml offo-hyphenation/hyph/lv.xml
offo-hyphenation/hyph/ml.xml offo-hyphenation/hyph/mn.xml
offo-hyphenation/hyph/mr.xml offo-hyphenation/hyph/nb.xml
offo-hyphenation/hyph/nl.xml offo-hyphenation/hyph/nn.xml
offo-hyphenation/hyph/or.xml offo-hyphenation/hyph/pa.xml
offo-hyphenation/hyph/pl.xml offo-hyphenation/hyph/pt.xml
offo-hyphenation/hyph/ro.xml offo-hyphenation/hyph/ru.xml
offo-hyphenation/hyph/sa.xml offo-hyphenation/hyph/sk.xml
offo-hyphenation/hyph/sl.xml offo-hyphenation/hyph/sr_Cyrl.xml
offo-hyphenation/hyph/sr_Latn.xml offo-hyphenation/hyph/sv.xml
offo-hyphenation/hyph/ta.xml offo-hyphenation/hyph/te.xml
offo-hyphenation/hyph/tk.xml offo-hyphenation/hyph/tr.xml
offo-hyphenation/hyph/uk.xml offo-hyphenation/hyph/zh_Latn.xml hyph
+ exit 0
Executing(%build): /bin/sh -e
/home/shlomif/Download/unpack/Mageia/fop/BUILDROOT/rpm-tmp.fhqisw
+ umask 022
+ cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
+ cd fop-1.1
+ '[' 1 -eq 1 ']'
+ '[' 1 -eq 1 ']'
+ export CLASSPATH=
+ CLASSPATH=
++ build-classpath apache-commons-logging apache-commons-io xmlgraphics-commons
batik-all
+
CLASSPATH=:/usr/share/java/apache-commons-logging.jar:/usr/share/java/apache-commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/batik-all.jar
++ build-classpath avalon-framework-api avalon-framework-impl servlet
batik/batik-svg-dom
+
CLASSPATH=:/usr/share/java/apache-commons-logging.jar:/usr/share/java/apache-commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/batik-all.jar:/usr/share/java/avalon-framework-api.jar:/usr/share/java/avalon-framework-impl.jar:/usr/share/java/servlet.jar:/usr/share/java/batik/batik-svg-dom.jar
++ build-classpath xml-commons-apis xml-commons-apis-ext objectweb-asm/asm-all
xmlunit
+
[jira] [Reopened] (FOP-2253) Build Failure on Mageia Linux Cauldron (what will be Mageia 4)
[
https://issues.apache.org/jira/browse/FOP-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams reopened FOP-2253:
--
> Build Failure on Mageia Linux Cauldron (what will be Mageia 4)
> --
>
> Key: FOP-2253
> URL: https://issues.apache.org/jira/browse/FOP-2253
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 1.1
> Environment: Mageia Linux 3 Cauldron x86-64
>Reporter: Shlomi Fish
>Priority: Major
>
> When I run the build on Mageia Linux 3 x86-64 I get these build problems:
> creating package list
> processing package fop-1.1-%mkrel 1
> building binary packages
> Executing(%prep): /bin/sh -e
> /home/shlomif/Download/unpack/Mageia/fop/BUILDROOT/rpm-tmp.7CWPCz
> + umask 022
> + cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
> + '[' 1 -eq 1 ']'
> + '[' 1 -eq 1 ']'
> + '[' 1 -eq 1 ']'
> + cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
> + rm -rf fop-1.1
> + /usr/bin/gzip -dc
> /home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-1.1-src.tar.gz
> + /usr/bin/tar -xf -
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd fop-1.1
> + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
> + echo 'Patch #0 (fop-1.0-manifest.patch):'
> Patch #0 (fop-1.0-manifest.patch):
> + /usr/bin/cat
> /home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-1.0-manifest.patch
> + /usr/bin/patch -p1 -b --suffix .mani-patch --fuzz=0
> patching file build.xml
> patching file fop.mf
> + echo 'Patch #1 (fop-main.patch):'
> Patch #1 (fop-main.patch):
> + /usr/bin/cat /home/shlomif/Download/unpack/Mageia/fop/SOURCES/fop-main.patch
> + /usr/bin/patch -p0 -b --suffix .main-patch --fuzz=0
> patching file src/java/org/apache/fop/cli/Main.java
> Hunk #1 succeeded at 204 (offset 11 lines).
> + find -name '*.class' -exec rm -f '{}' ';'
> + find -name '*.jar' -exec rm -f '{}' ';'
> + sed -i -e 's|1.4|1.5|g' build.xml
> + ln -s /usr/share/java/qdox.jar lib/build/qdox.jar
> + unzip -q
> /home/shlomif/Download/unpack/Mageia/fop/SOURCES/offo-hyphenation_v2.0.zip
> + mv offo-hyphenation/hyph/af.xml offo-hyphenation/hyph/as.xml
> offo-hyphenation/hyph/bg.xml offo-hyphenation/hyph/bn.xml
> offo-hyphenation/hyph/ca.xml offo-hyphenation/hyph/cop.xml
> offo-hyphenation/hyph/cs.xml offo-hyphenation/hyph/cy.xml
> offo-hyphenation/hyph/da.xml offo-hyphenation/hyph/de_1901.xml
> offo-hyphenation/hyph/de_CH.xml offo-hyphenation/hyph/de.xml
> offo-hyphenation/hyph/el_Polyton.xml offo-hyphenation/hyph/el.xml
> offo-hyphenation/hyph/en_GB.xml offo-hyphenation/hyph/en.xml
> offo-hyphenation/hyph/eo.xml offo-hyphenation/hyph/es.xml
> offo-hyphenation/hyph/et.xml offo-hyphenation/hyph/eu.xml
> offo-hyphenation/hyph/fi.xml offo-hyphenation/hyph/fr.xml
> offo-hyphenation/hyph/ga.xml offo-hyphenation/hyph/gl.xml
> offo-hyphenation/hyph/grc.xml offo-hyphenation/hyph/gu.xml
> offo-hyphenation/hyph/hi.xml offo-hyphenation/hyph/hr.xml
> offo-hyphenation/hyph/hsb.xml offo-hyphenation/hyph/hy.xml
> offo-hyphenation/hyph/ia.xml offo-hyphenation/hyph/id.xml
> offo-hyphenation/hyph/is.xml offo-hyphenation/hyph/it.xml
> offo-hyphenation/hyph/kmr.xml offo-hyphenation/hyph/kn.xml
> offo-hyphenation/hyph/la.xml offo-hyphenation/hyph/lo.xml
> offo-hyphenation/hyph/lt.xml offo-hyphenation/hyph/lv.xml
> offo-hyphenation/hyph/ml.xml offo-hyphenation/hyph/mn.xml
> offo-hyphenation/hyph/mr.xml offo-hyphenation/hyph/nb.xml
> offo-hyphenation/hyph/nl.xml offo-hyphenation/hyph/nn.xml
> offo-hyphenation/hyph/or.xml offo-hyphenation/hyph/pa.xml
> offo-hyphenation/hyph/pl.xml offo-hyphenation/hyph/pt.xml
> offo-hyphenation/hyph/ro.xml offo-hyphenation/hyph/ru.xml
> offo-hyphenation/hyph/sa.xml offo-hyphenation/hyph/sk.xml
> offo-hyphenation/hyph/sl.xml offo-hyphenation/hyph/sr_Cyrl.xml
> offo-hyphenation/hyph/sr_Latn.xml offo-hyphenation/hyph/sv.xml
> offo-hyphenation/hyph/ta.xml offo-hyphenation/hyph/te.xml
> offo-hyphenation/hyph/tk.xml offo-hyphenation/hyph/tr.xml
> offo-hyphenation/hyph/uk.xml offo-hyphenation/hyph/zh_Latn.xml hyph
> + exit 0
> Executing(%build): /bin/sh -e
> /home/shlomif/Download/unpack/Mageia/fop/BUILDROOT/rpm-tmp.fhqisw
> + umask 022
> + cd /home/shlomif/Download/unpack/Mageia/fop/BUILD
> + cd fop-1.1
> + '[' 1 -eq 1 ']'
> + '[' 1 -eq 1 ']'
> + export CLASSPATH=
> + CLASSPATH=
> ++ build-classpath apache-commons-logging apache-commons-io
> xmlgraphics-commons batik-all
> +
> CLASSPATH=:/usr/share/java/apache-commons-logging.jar:/usr/share/java/apache-commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/batik-all.jar
> ++ build-classpath avalon-framework-api avalon-framework-impl servlet
> batik/batik-svg-dom
> +
>
[jira] [Closed] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2005. Resolution: Cannot Reproduce move inlined code from description and comment to attachments > build fails (fop-1_0) > - > > Key: FOP-2005 > URL: https://issues.apache.org/jira/browse/FOP-2005 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.0 > Environment: Operating System: Linux > Platform: PC >Reporter: John L. Poole >Assignee: fop-dev > Attachments: fop-2005-comment-with-code.txt, > fop-2005-description-with-code.txt > > > I attempted to checkout "fop-1_0" and build same. It failed. > See attachment fop-2005-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2005: - Attachment: fop-2005-comment-with-code.txt > build fails (fop-1_0) > - > > Key: FOP-2005 > URL: https://issues.apache.org/jira/browse/FOP-2005 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.0 > Environment: Operating System: Linux > Platform: PC >Reporter: John L. Poole >Assignee: fop-dev > Attachments: fop-2005-comment-with-code.txt, > fop-2005-description-with-code.txt > > > I attempted to checkout "fop-1_0" and build same. It failed. > See attachment fop-2005-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=13524736#comment-13524736 ] Glenn Adams edited comment on FOP-2005 at 4/29/23 8:19 PM: --- (In reply to comment #1) > This issue was changed to "RESOLVED" and works for me without any comment. I > do not understand why the status has been changed without comment. no comment was needed since WORKSFORME speaks for itself; i do not encounter a build error when building from tag fop-1_0 (see output below); if you have new information that warrants reopening this bug, then please do so; otherwise, i am again moving to resolved... see attachment fop-2005-comment-with-code.txt was (Author: gadams): (In reply to comment #1) > This issue was changed to "RESOLVED" and works for me without any comment. I > do not understand why the status has been changed without comment. no comment was needed since WORKSFORME speaks for itself; i do not encounter a build error when building from tag fop-1_0 (see output below); if you have new information that warrants reopening this bug, then please do so; otherwise, i am again moving to resolved... bash-3.2$ svn info Path: . Working Copy Root Path: /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0 URL: http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1309184 Node Kind: directory Schedule: normal Last Changed Author: vhennebert Last Changed Rev: 1141997 Last Changed Date: 2011-07-01 11:25:44 -0600 (Fri, 01 Jul 2011) bash-3.2$ ant -version Apache Ant(TM) version 1.8.2 compiled on October 14 2011 bash-3.2$ javac -version javac 1.6.0_29 bash-3.2$ uname -a Darwin sn-ga-01.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 bash-3.2$ ant all Buildfile: /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build.xml init-avail: [echo] --- Apache FOP 1.0 [1999-2010] [echo] See build.properties and build-local.properties for additional build settings [echo] Apache Ant(TM) version 1.8.2 compiled on October 14 2011 [echo] VM: 20.4-b02-402, Apple Inc. [echo] JAVA_HOME: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home [echo] JAI Support PRESENT [echo] JCE Support PRESENT [echo] JUnit Support PRESENT [echo] XMLUnit Support PRESENT [snip] resourcegen: [mkdir] Created dir: /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/codegen-classes [javac] /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build.xml:354: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 3 source files to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/codegen-classes [copy] Copying 2 files to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/codegen-classes [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/accessibility/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/afp/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/area/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/fo/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/fo/flow/table/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/fonts/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/layoutmgr/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/layoutmgr/inline/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/render/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/render/bitmap/event-model.xml [eventResourceGenerator] Event model written to /users/glenn/Work/xmlgraphics/fop/tags/fop-1_0/build/gensrc/org/apache/fop/render/pcl/event-model.xml [eventResourceGenerator] Event model written to
[jira] [Updated] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2005: - Attachment: fop-2005-description-with-code.txt > build fails (fop-1_0) > - > > Key: FOP-2005 > URL: https://issues.apache.org/jira/browse/FOP-2005 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.0 > Environment: Operating System: Linux > Platform: PC >Reporter: John L. Poole >Assignee: fop-dev > Attachments: fop-2005-description-with-code.txt > > > I attempted to checkout "fop-1_0" and build same. It failed. > See attachment fop-2005-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2005: - Description: I attempted to checkout "fop-1_0" and build same. It failed. See attachment fop-2005-description-with-code.txt was: I attempted to checkout "fop-1_0" and build same. It failed. hip src # svn co http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0/ fop_1_0 ...[snip]... Checked out revision 1225614. hip src # cd fop_1_0/ hip fop_1_0 # svn info Path: . URL: http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1225614 Node Kind: directory Schedule: normal Last Changed Author: vhennebert Last Changed Rev: 1141997 Last Changed Date: 2011-07-01 10:25:44 -0700 (Fri, 01 Jul 2011) hip fop_1_0 # ant -version Apache Ant version 1.8.1 compiled on July 13 2010 hip fop_1_0 # javac -version javac 1.6.0_29 hip fop_1_0 # uname -a Linux hip 2.6.38-gentoo-r6 #3 SMP Wed Sep 14 17:16:28 PDT 2011 i686 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux hip fop_1_0 # ant all Buildfile: /usr/local/src/fop_1_0/build.xml init-avail: [echo] --- Apache FOP 1.0 [1999-2010] [echo] See build.properties and build-local.properties for additional build settings [echo] Apache Ant version 1.8.1 compiled on July 13 2010 [echo] VM: 20.4-b02, Sun Microsystems Inc. [echo] JAVA_HOME: /opt/sun-jdk-1.6.0.29 [echo] JAI Support NOT Present [echo] JCE Support PRESENT [echo] JUnit Support PRESENT [echo] XMLUnit Support PRESENT init: codegen: [echo] Generating the java files from xml resources [mkdir] Created dir: /usr/local/src/fop_1_0/build/gensrc [mkdir] Created dir: /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14 [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/encodings.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/CodePointMapping.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/code-point-mapping.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/Courier.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/Courier.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/CourierOblique.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierOblique.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/CourierBold.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierBold.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/CourierBoldOblique.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierBoldOblique.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/Helvetica.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/Helvetica.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaBold.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaBold.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaOblique.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaOblique.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaBoldOblique.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaBoldOblique.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/TimesRoman.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/TimesRoman.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/TimesItalic.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/TimesItalic.java [xslt] Loading stylesheet /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/TimesBold.xml to /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/TimesBold.java [xslt] Loading stylesheet
[jira] [Reopened] (FOP-2005) build fails (fop-1_0)
[ https://issues.apache.org/jira/browse/FOP-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-2005: -- > build fails (fop-1_0) > - > > Key: FOP-2005 > URL: https://issues.apache.org/jira/browse/FOP-2005 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 1.0 > Environment: Operating System: Linux > Platform: PC >Reporter: John L. Poole >Assignee: fop-dev > > I attempted to checkout "fop-1_0" and build same. It failed. > hip src # svn co > http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0/ fop_1_0 > ...[snip]... > Checked out revision 1225614. > hip src # cd fop_1_0/ > hip fop_1_0 # svn info > Path: . > URL: http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 1225614 > Node Kind: directory > Schedule: normal > Last Changed Author: vhennebert > Last Changed Rev: 1141997 > Last Changed Date: 2011-07-01 10:25:44 -0700 (Fri, 01 Jul 2011) > hip fop_1_0 # ant -version > Apache Ant version 1.8.1 compiled on July 13 2010 > hip fop_1_0 # javac -version > javac 1.6.0_29 > hip fop_1_0 # uname -a > Linux hip 2.6.38-gentoo-r6 #3 SMP Wed Sep 14 17:16:28 PDT 2011 i686 Intel(R) > Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux > hip fop_1_0 # ant all > Buildfile: /usr/local/src/fop_1_0/build.xml > init-avail: > [echo] --- Apache FOP 1.0 [1999-2010] > [echo] See build.properties and build-local.properties for additional > build settings > [echo] Apache Ant version 1.8.1 compiled on July 13 2010 > [echo] VM: 20.4-b02, Sun Microsystems Inc. > [echo] JAVA_HOME: /opt/sun-jdk-1.6.0.29 > [echo] JAI Support NOT Present > [echo] JCE Support PRESENT > [echo] JUnit Support PRESENT > [echo] XMLUnit Support PRESENT > init: > codegen: > [echo] Generating the java files from xml resources > [mkdir] Created dir: /usr/local/src/fop_1_0/build/gensrc > [mkdir] Created dir: > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14 > [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/encodings.xml > to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/CodePointMapping.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/code-point-mapping.xsl > [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/Courier.xml > to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/Courier.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/CourierOblique.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierOblique.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/CourierBold.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierBold.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/CourierBoldOblique.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/CourierBoldOblique.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing /usr/local/src/fop_1_0/src/codegen/fonts/Helvetica.xml > to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/Helvetica.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaBold.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaBold.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaOblique.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaOblique.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/HelveticaBoldOblique.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/HelveticaBoldOblique.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt] Processing > /usr/local/src/fop_1_0/src/codegen/fonts/TimesRoman.xml to > /usr/local/src/fop_1_0/build/gensrc/org/apache/fop/fonts/base14/TimesRoman.java > [xslt] Loading stylesheet > /usr/local/src/fop_1_0/src/codegen/fonts/font-file.xsl > [xslt]
[jira] [Updated] (FOP-1240) Out of Memory when add the attribute keep-together.within-column="always"
[ https://issues.apache.org/jira/browse/FOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1240: - Attachment: fop-1240-description-with-code.txt > Out of Memory when add the attribute keep-together.within-column="always" > - > > Key: FOP-1240 > URL: https://issues.apache.org/jira/browse/FOP-1240 > Project: FOP > Issue Type: Bug > Components: fo/unqualified >Affects Versions: 0.20.5 > Environment: Operating System: Windows XP > Platform: PC >Reporter: KevinTan >Assignee: fop-dev >Priority: Blocker > Attachments: asif.fo, fop-1240-description-with-code.txt > > > The FO file occur out of memory. > After I remove the attribute keep-together.within-column="always",it is work > OK. > Please take a look. > Thanks, > Kevin > The file content: > See attachment fop-1240-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-1240) Out of Memory when add the attribute keep-together.within-column="always"
[ https://issues.apache.org/jira/browse/FOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-1240. Resolution: Won't Fix move inlined code from description to attachment > Out of Memory when add the attribute keep-together.within-column="always" > - > > Key: FOP-1240 > URL: https://issues.apache.org/jira/browse/FOP-1240 > Project: FOP > Issue Type: Bug > Components: fo/unqualified >Affects Versions: 0.20.5 > Environment: Operating System: Windows XP > Platform: PC >Reporter: KevinTan >Assignee: fop-dev >Priority: Blocker > Attachments: asif.fo, fop-1240-description-with-code.txt > > > The FO file occur out of memory. > After I remove the attribute keep-together.within-column="always",it is work > OK. > Please take a look. > Thanks, > Kevin > The file content: > See attachment fop-1240-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-1240) Out of Memory when add the attribute keep-together.within-column="always"
[ https://issues.apache.org/jira/browse/FOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1240: - Description: The FO file occur out of memory. After I remove the attribute keep-together.within-column="always",it is work OK. Please take a look. Thanks, Kevin The file content: See attachment fop-1240-description-with-code.txt was: The FO file occur out of memory. After I remove the attribute keep-together.within-column="always",it is work OK. Please take a look. Thanks, Kevin The file content: http://exslt.org/math; xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:svg="http://www.w3.org/2000/svg; xmlns:fo="http://www.w3.org/1999/XSL/Format;> http://www.w3.org/1999/xlink;> http://www.w3.org/1999/xlink;> Fees and Expenses as of prospectus dated 05-01- 2006 Rider Charges %
[jira] [Reopened] (FOP-1240) Out of Memory when add the attribute keep-together.within-column="always"
[ https://issues.apache.org/jira/browse/FOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-1240: -- > Out of Memory when add the attribute keep-together.within-column="always" > - > > Key: FOP-1240 > URL: https://issues.apache.org/jira/browse/FOP-1240 > Project: FOP > Issue Type: Bug > Components: fo/unqualified >Affects Versions: 0.20.5 > Environment: Operating System: Windows XP > Platform: PC >Reporter: KevinTan >Assignee: fop-dev > Attachments: asif.fo > > > The FO file occur out of memory. > After I remove the attribute keep-together.within-column="always",it is work > OK. > Please take a look. > Thanks, > Kevin > The file content: > weight="normal" xmlns:aws="aws" xmlns:math="http://exslt.org/math; > xmlns:msxsl="urn:schemas-microsoft-com:xslt" > xmlns:svg="http://www.w3.org/2000/svg; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > http://www.w3.org/1999/xlink;> >page-width="8.5in" margin-top="20pt" margin-bottom="28pt" > margin-left="0.75in" > margin-right="0.4in"> > >bottom="46pt"/> > > > >xmlns:xlink="http://www.w3.org/1999/xlink;> > > > > > > >dimension.optimum="100%"> > > > > > >spanned="3"> >space-before="4pt" space-after="0pt" font-size="8pt"> >table-layout="fixed" inline-progression-dimension.optimum="100%"> > > > > > > > > > > > > > > > > > > > > > > > >background-color="rgb(217,217,217)" text-indent="2pt">Fees and > Expenses as of prospectus dated > > 05-01- > 2006 > > > > > > > > > > > > > > > > > >column/> > > > > > > >font-size="8pt"> > >dimension.optimum="100%"> > > > > > >
[jira] [Closed] (FOP-1136) java.lang.NullPointerException when fop parse specific table.
[ https://issues.apache.org/jira/browse/FOP-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-1136. Resolution: Fixed move inlined code from description to attachment > java.lang.NullPointerException when fop parse specific table. > - > > Key: FOP-1136 > URL: https://issues.apache.org/jira/browse/FOP-1136 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.91 > Environment: Operating System: Linux > Platform: Other >Reporter: Victor Andreev >Assignee: fop-dev >Priority: Blocker > Attachments: example.zip, fop-1136-description-with-code.txt > > > Throws the NullPointerException when fop tried parse this intricate table: > See attachment fop-1136-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-1136) java.lang.NullPointerException when fop parse specific table.
[ https://issues.apache.org/jira/browse/FOP-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1136: - Attachment: fop-1136-description-with-code.txt > java.lang.NullPointerException when fop parse specific table. > - > > Key: FOP-1136 > URL: https://issues.apache.org/jira/browse/FOP-1136 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.91 > Environment: Operating System: Linux > Platform: Other >Reporter: Victor Andreev >Assignee: fop-dev >Priority: Blocker > Attachments: example.zip, fop-1136-description-with-code.txt > > > Throws the NullPointerException when fop tried parse this intricate table: > See attachment fop-1136-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-1136) java.lang.NullPointerException when fop parse specific table.
[ https://issues.apache.org/jira/browse/FOP-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1136: - Description: Throws the NullPointerException when fop tried parse this intricate table: See attachment fop-1136-description-with-code.txt was: Throws the NullPointerException when fop tried parse this intricate table: Kinder - und Jugendarbeit Kindergruppen in der Gemeinde Anzahl der Kreise 321 Zahl der Teilnehmer/ innen je Zusammenkunft 322 *) Zeile 321- 324, 327 u. 328: Bei mehreren Kreisen / Gruppen: Summe der durchchnittl . Zahl der Teilnehmer/ innen angeben. Jugendgruppen in der Gemeinde (einschließlich Christenlehre) *) Anzahl der Kreise 327 Zahl der Teilnehmer/ innen je Zusammenkunft 328 Eltern-Kind-Gruppen ( Spielkreise ) *) Anzahl der Gruppen 323 **) Zeile 325 und 326: Mehrtägige Veranstaltungen werden als eine Veranstaltung gezählt. Zahl der Teilnehmer/ innen je Zusammenkunft 1 324
[jira] [Reopened] (FOP-1136) java.lang.NullPointerException when fop parse specific table.
[ https://issues.apache.org/jira/browse/FOP-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-1136: -- > java.lang.NullPointerException when fop parse specific table. > - > > Key: FOP-1136 > URL: https://issues.apache.org/jira/browse/FOP-1136 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.91 > Environment: Operating System: Linux > Platform: Other >Reporter: Victor Andreev >Assignee: fop-dev > Attachments: example.zip > > > Throws the NullPointerException when fop tried parse this intricate table: > > > > > > > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="none" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="solid" > border-right-style="none" > border-left-color="black" border-right-color="black" border-left-width="0.5pt" > border-right-width="0.25pt" number-columns-spanned="2" > number-rows-spanned="2"> > space-before="4pt" space-before.conditionality="retain" font-weight="bold"> > font-size="10pt"> > Kinder > > font-size="8pt"> > > > font-size="10pt"> > - und > > font-size="10pt"> > Jugendarbeit > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="none" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="none" > border-right-style="none" > border-left-color="black" border-right-color="black" > border-left-width="0.25pt" > border-right-width="0.25pt" number-rows-spanned="2"> > space-before="4pt" space-before.conditionality="retain" font-weight="bold"> > font-size="8pt"> > Kindergruppen > > font-size="8pt"> > in > > font-size="8pt"> > der > > > font-weight="bold"> > font-size="8pt"> > Gemeinde > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="solid" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="none" > border-right-style="solid" > border-left-color="black" border-right-color="black" > border-left-width="0.25pt" > border-right-width="0.25pt" display-align="center"> > line-height="9pt" space-before="2pt" space-before.conditionality="retain" > text-align="right"> > > Anzahl der Kreise > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="solid" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="solid" > border-right-style="solid" border-left-color="black" > border-right-color="black" > border-left-width="0.25pt" border-right-width="0.25pt" display-align="center"> > line-height="9pt" space-before="2pt" space-before.conditionality="retain" > text-align="center"> > > 321 > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="solid" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="solid" > border-right-style="solid" border-left-color="black" > border-right-color="black" > border-left-width="0.25pt" border-right-width="0.5pt" display-align="center"> > text-align="center" font-weight="bold"> > font-size="8pt" language="DE"> > select="elements/element[@name='field321']/value"/> > > > > > > padding-left="5.4pt" padding-bottom="0pt" padding-right="5.4pt" > border-top-style="solid" border-bottom-style="solid" border-top-color="black" > border-bottom-color="black" border-top-width="0.25pt" > border-bottom-width="0.25pt" border-left-style="none" > border-right-style="solid" > border-left-color="black" border-right-color="black" >
[jira] [Closed] (FOP-992) Attribute number-columns-spanned leads to the endless loop
[ https://issues.apache.org/jira/browse/FOP-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-992. --- Resolution: Fixed move inlined code from comment to attachment > Attribute number-columns-spanned leads to the endless loop > -- > > Key: FOP-992 > URL: https://issues.apache.org/jira/browse/FOP-992 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: other > Platform: Other >Reporter: maco >Assignee: fop-dev > Attachments: fop-992-comment-with-code.txt > > > In FO, a table is nested into another table and the cell that table locates > in > has the property number-columns-spanned set to 3. If this property is > removed, > then all are OK and the produced PDF has more than one page. Or else the FOP > drops into the infinite loop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-992) Attribute number-columns-spanned leads to the endless loop
[ https://issues.apache.org/jira/browse/FOP-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=13518451#comment-13518451 ] Glenn Adams edited comment on FOP-992 at 4/29/23 7:50 PM: -- See attachment fop-992-comment-with-code.txt was (Author: forevertravel...@hotmail.com): http://www.w3.org/1999/XSL/Format;> Title 6/23/05 2:15 PM Page:
[jira] [Updated] (FOP-992) Attribute number-columns-spanned leads to the endless loop
[ https://issues.apache.org/jira/browse/FOP-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-992: Attachment: fop-992-comment-with-code.txt > Attribute number-columns-spanned leads to the endless loop > -- > > Key: FOP-992 > URL: https://issues.apache.org/jira/browse/FOP-992 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: other > Platform: Other >Reporter: maco >Assignee: fop-dev > Attachments: fop-992-comment-with-code.txt > > > In FO, a table is nested into another table and the cell that table locates > in > has the property number-columns-spanned set to 3. If this property is > removed, > then all are OK and the produced PDF has more than one page. Or else the FOP > drops into the infinite loop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (FOP-992) Attribute number-columns-spanned leads to the endless loop
[ https://issues.apache.org/jira/browse/FOP-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-992: - > Attribute number-columns-spanned leads to the endless loop > -- > > Key: FOP-992 > URL: https://issues.apache.org/jira/browse/FOP-992 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: other > Platform: Other >Reporter: maco >Assignee: fop-dev > > In FO, a table is nested into another table and the cell that table locates > in > has the property number-columns-spanned set to 3. If this property is > removed, > then all are OK and the produced PDF has more than one page. Or else the FOP > drops into the infinite loop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-781) PDF not rendered by 0.20.5
[ https://issues.apache.org/jira/browse/FOP-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-781: Attachment: fop-781-description-with-code.txt > PDF not rendered by 0.20.5 > -- > > Key: FOP-781 > URL: https://issues.apache.org/jira/browse/FOP-781 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: All >Reporter: Sorin >Assignee: fop-dev >Priority: Blocker > Attachments: fop-781-description-with-code.txt > > > I have a FO file for which FOP 0.20.5 does not render any PDF. It worked with > 0.20.4. What is wrong ? > See attachment fop-781-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-781) PDF not rendered by 0.20.5
[ https://issues.apache.org/jira/browse/FOP-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-781. --- Resolution: Not A Problem move inlined code from description to attachment > PDF not rendered by 0.20.5 > -- > > Key: FOP-781 > URL: https://issues.apache.org/jira/browse/FOP-781 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: All >Reporter: Sorin >Assignee: fop-dev >Priority: Blocker > Attachments: fop-781-description-with-code.txt > > > I have a FO file for which FOP 0.20.5 does not render any PDF. It worked with > 0.20.4. What is wrong ? > See attachment fop-781-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-781) PDF not rendered by 0.20.5
[ https://issues.apache.org/jira/browse/FOP-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-781: Description: I have a FO file for which FOP 0.20.5 does not render any PDF. It worked with 0.20.4. What is wrong ? See attachment fop-781-description-with-code.txt was: I have a FO file for which FOP 0.20.5 does not render any PDF. It worked with 0.20.4. What is wrong ? http://www.w3.org/1999/XSL/Format; font-family="serif,Symbol,ZapfDingbats" font-size="10pt" text-align="justify" line-height="normal" font-selection-strategy="character-by-character" language="en"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)" background-attachment="fixed" background-repeat="no-repeat" background-position-horizontal="center" background-position-vertical="center"> http://docbook.sourceforge.net/release/images/draft.png)"
[jira] [Reopened] (FOP-781) PDF not rendered by 0.20.5
[ https://issues.apache.org/jira/browse/FOP-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-781: - > PDF not rendered by 0.20.5 > -- > > Key: FOP-781 > URL: https://issues.apache.org/jira/browse/FOP-781 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: All >Reporter: Sorin >Assignee: fop-dev > > I have a FO file for which FOP 0.20.5 does not render any PDF. It worked with > 0.20.4. What is wrong ? > xmlns:fo="http://www.w3.org/1999/XSL/Format; > font-family="serif,Symbol,ZapfDingbats" > font-size="10pt" text-align="justify" line-height="normal" > font-selection-strategy="character-by-character" language="en"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > margin-top="0.5in" region-name="blank-body"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-width="8.5in" > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" > display-align="before"> > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-right="1in" > margin-left="1in - -4pc"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" > display-align="before"> > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-right="1in" > margin-left="1in - -4pc"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" > display-align="before"> > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-right="1in" > margin-left="1in - -4pc"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> > column-gap="12pt" column-count="1"> > extent="0.4in" > display-align="before"> > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-right="1in" > margin-left="1in - -4pc"> > column-gap="12pt" column-count="1"> > extent="0.4in" display-align="before"> > extent="0.4in" > display-align="after"> > > page-height="11in" > margin-top="0.5in" margin-bottom="0.5in" margin-left="1in - -4pc" > margin-right="1in"> >
[jira] [Updated] (FOP-700) java.lang.ArrayIndexOutOfBoundsException when running FOP
[ https://issues.apache.org/jira/browse/FOP-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-700: Description: I am running the folowing command from the command line and get the ArrayOutoFBoundsException at the bottom. Please find below my example xml, and my example stylesheet ( I have also used xalan to produce my fo which looks ok and is also found below. ) If I change my XPath to just create Page 1 from example xml it runs ok, Page 2 seems to cause the problems - I wonder if it is something to do with it havng many nodes although I decreased these and it still didnt work. Please help! See attachment fop-700-description-with-code.txt was: I am running the folowing command from the command line and get the ArrayOutoFBoundsException at the bottom. Please find below my example xml, and my example stylesheet ( I have also used xalan to produce my fo which looks ok and is also found below. ) If I change my XPath to just create Page 1 from example xml it runs ok, Page 2 seems to cause the problems - I wonder if it is something to do with it havng many nodes although I decreased these and it still didnt work. Please help! CMD and ERROR C:\fop-0.20.5>fop -xml umv-example.xml -xsl Example1.xsl -pdf LC1 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] FOP 0.20.5 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. [ERROR] java.lang.ArrayIndexOutOfBoundsException Example1.xsl - - - http://www.w3.org/1999/XSL/Transform; xmlns:fo="http://www.w3.org/1999/XSL/Format;> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - underline - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - " umv_example xml " sans-serif 9 1 1 1 1 landscape A4 8 3 9 bold Property 10.0 9 bold Value 16.0 0 0 1 9 $REPORTTYPE$ 1 9 DataReportUsers 1 9 ReportLocale 1 9 en_GB 11 Report Generator v0.3 (15/07/2003 08:10) 8 3 9 bold Property 10.0
[jira] [Closed] (FOP-700) java.lang.ArrayIndexOutOfBoundsException when running FOP
[ https://issues.apache.org/jira/browse/FOP-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-700. --- Resolution: Duplicate move inlined code from description into attachment > java.lang.ArrayIndexOutOfBoundsException when running FOP > - > > Key: FOP-700 > URL: https://issues.apache.org/jira/browse/FOP-700 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Louise >Assignee: fop-dev > Attachments: Approval.xsl, UMV-Example.xsl, approval.fo, > approval.xml, fop-700-description-with-code.txt, umv-example.xml, umv.fo > > > I am running the folowing command from the command line and get the > ArrayOutoFBoundsException at the bottom. > Please find below my example xml, and my example stylesheet ( I have also > used > xalan to produce my fo which looks ok and is also found below. ) > If I change my XPath to just create Page 1 from example xml it runs ok, Page > 2 > seems to cause the problems - I wonder if it is something to do with it havng > many nodes although I decreased these and it still didnt work. Please help! > See attachment fop-700-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-700) java.lang.ArrayIndexOutOfBoundsException when running FOP
[ https://issues.apache.org/jira/browse/FOP-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-700: Attachment: fop-700-description-with-code.txt > java.lang.ArrayIndexOutOfBoundsException when running FOP > - > > Key: FOP-700 > URL: https://issues.apache.org/jira/browse/FOP-700 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Louise >Assignee: fop-dev > Attachments: Approval.xsl, UMV-Example.xsl, approval.fo, > approval.xml, fop-700-description-with-code.txt, umv-example.xml, umv.fo > > > I am running the folowing command from the command line and get the > ArrayOutoFBoundsException at the bottom. > Please find below my example xml, and my example stylesheet ( I have also > used > xalan to produce my fo which looks ok and is also found below. ) > If I change my XPath to just create Page 1 from example xml it runs ok, Page > 2 > seems to cause the problems - I wonder if it is something to do with it havng > many nodes although I decreased these and it still didnt work. Please help! > CMD and ERROR > > C:\fop-0.20.5>fop -xml umv-example.xml -xsl Example1.xsl -pdf LC1 > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] FOP 0.20.5 > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] building formatting object tree > [INFO] setting up fonts > [INFO] [1] > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] java.lang.ArrayIndexOutOfBoundsException > Example1.xsl > > - > - > - xmlns:xsl="http://www.w3.org/1999/XSL/Transform; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > - > - > - > - > > > - > > > - > > > - > > - > > > > > - > - > - > - > - > > > - > > > - > > > - > > > - > - > > > - > > > > > > > > > - > - > - > - > - > - > - > - > - > > > - > > > - > - > - > > > > > - > - > - > - > - > > > > > > - > - > - > - > - > > underline > > > > > > > > > > > - > - > > - > - > - > > > - > > > - > - > - > > > > > - > - > - > - > - > > > > > > - > - > - > - > - > > > > > > > > > > > - > - > - > - > - > - > > > - > > > - > > > - > - > > > - > > > - > > > - > > > - > > > - > - > - > > > - > - > - > - > - > > > > > > - > - > - > - > - > > > > > > > > > > > > > > - > - > " umv_example xml > " > context="usermaintenancereport"> > sans-serif > 9 > 1 > 1 > 1 > 1 > landscape > A4 > > > > > 8 > 3 > > > > > > 9 > bold > Property > > > 10.0 > > > > > > 9 > bold > Value > > > 16.0 > > > 0 > 0 > > > > > 1 > > > > 9 > > $REPORTTYPE$ > > > > > 1 > > > > 9 > > DataReportUsers > > > > > > > > > 1 > > > > 9 > >
[jira] [Reopened] (FOP-700) java.lang.ArrayIndexOutOfBoundsException when running FOP
[ https://issues.apache.org/jira/browse/FOP-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-700: - > java.lang.ArrayIndexOutOfBoundsException when running FOP > - > > Key: FOP-700 > URL: https://issues.apache.org/jira/browse/FOP-700 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Louise >Assignee: fop-dev > Attachments: Approval.xsl, UMV-Example.xsl, approval.fo, > approval.xml, umv-example.xml, umv.fo > > > I am running the folowing command from the command line and get the > ArrayOutoFBoundsException at the bottom. > Please find below my example xml, and my example stylesheet ( I have also > used > xalan to produce my fo which looks ok and is also found below. ) > If I change my XPath to just create Page 1 from example xml it runs ok, Page > 2 > seems to cause the problems - I wonder if it is something to do with it havng > many nodes although I decreased these and it still didnt work. Please help! > CMD and ERROR > > C:\fop-0.20.5>fop -xml umv-example.xml -xsl Example1.xsl -pdf LC1 > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] FOP 0.20.5 > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] building formatting object tree > [INFO] setting up fonts > [INFO] [1] > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on > table. > [ERROR] java.lang.ArrayIndexOutOfBoundsException > Example1.xsl > > - > - > - xmlns:xsl="http://www.w3.org/1999/XSL/Transform; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > - > - > - > - > > > - > > > - > > > - > > - > > > > > - > - > - > - > - > > > - > > > - > > > - > > > - > - > > > - > > > > > > > > > - > - > - > - > - > - > - > - > - > > > - > > > - > - > - > > > > > - > - > - > - > - > > > > > > - > - > - > - > - > > underline > > > > > > > > > > > - > - > > - > - > - > > > - > > > - > - > - > > > > > - > - > - > - > - > > > > > > - > - > - > - > - > > > > > > > > > > > - > - > - > - > - > - > > > - > > > - > > > - > - > > > - > > > - > > > - > > > - > > > - > - > - > > > - > - > - > - > - > > > > > > - > - > - > - > - > > > > > > > > > > > > > > - > - > " umv_example xml > " > context="usermaintenancereport"> > sans-serif > 9 > 1 > 1 > 1 > 1 > landscape > A4 > > > > > 8 > 3 > > > > > > 9 > bold > Property > > > 10.0 > > > > > > 9 > bold > Value > > > 16.0 > > > 0 > 0 > > > > > 1 > > > > 9 > > $REPORTTYPE$ > > > > > 1 > > > > 9 > > DataReportUsers > > > > > > > > > 1 > > > > 9 > > ReportLocale > > > >
[jira] [Closed] (FOP-625) multi-page table cellborders are too often added when the page breaks
[ https://issues.apache.org/jira/browse/FOP-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-625. --- Resolution: Fixed move inlined code in description to attachment > multi-page table cellborders are too often added when the page breaks > - > > Key: FOP-625 > URL: https://issues.apache.org/jira/browse/FOP-625 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: thomas.hinterberger >Assignee: fop-dev >Priority: Blocker > Attachments: fop-625-description-with-code.txt > > > I have a xsl-fo file which contains a large table. The table represents an > invoice and only some cells have borders. I convert this document to a > pdf-file > and the output is not correct. If the pagebreak occurs the cellborders are > wrong at the bottom of this page or at the top of the following page. They > are > printed on both pages. > Below the xsl-fo file is attached. If you generate a pdf-file from this, you > can see the bugs e.g. at top of page 3 or bottom of page 6 or the bottom of > page 7. > See attachment fop-625-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-598) height of cells
[
https://issues.apache.org/jira/browse/FOP-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-598.
---
Resolution: Fixed
move inlined code in description to attachment
> height of cells
> ---
>
> Key: FOP-598
> URL: https://issues.apache.org/jira/browse/FOP-598
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 0.15
> Environment: Operating System: other
> Platform: Other
>Reporter: xavier robert
>Assignee: fop-dev
>
> Look to these lines :
> Last line of the table change the height of one cell of the first line
> ("CADRE
> B").
> Why ? What does it mean ?
> See attachment fop-598-description-with-code.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-598) height of cells
[
https://issues.apache.org/jira/browse/FOP-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-598:
Description:
Look to these lines :
Last line of the table change the height of one cell of the first line ("CADRE
B").
Why ? What does it mean ?
See attachment fop-598-description-with-code.txt
was:
Look to these lines :
Last line of the table change the height of one cell of the first line ("CADRE
B").
Why ? What does it mean ?
CADRE B
VENTILATION DES DOTATIONS
AUX AMORTISSEMENTS DE
L'EXERCICE
CADRE C
MOUVEMENTS AFFECTANT LA PROVISION POUR AMORTISSEMENTS
DEROGATOIRES
Immobilisations amortissables
Amortissements linaires
Amortissements
dgressifs
Amortissements
exceptionnels
Dotations
[jira] [Reopened] (FOP-598) height of cells
[
https://issues.apache.org/jira/browse/FOP-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams reopened FOP-598:
-
> height of cells
> ---
>
> Key: FOP-598
> URL: https://issues.apache.org/jira/browse/FOP-598
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 0.15
> Environment: Operating System: other
> Platform: Other
>Reporter: xavier robert
>Assignee: fop-dev
>
> Look to these lines :
> Last line of the table change the height of one cell of the first line
> ("CADRE
> B").
> Why ? What does it mean ?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> style="solid" background-color="silver">
> size="10pt" font-family="Arial, Helvetica, sans-serif" text-
> align="center">CADRE B
>
> style="solid" number-columns-spanned="7" background-color="silver">
>
>
>
> weight="bold">VENTILATION DES DOTATIONS
>
> AUX AMORTISSEMENTS DE
> L'EXERCICE
>
>
>
>
> style="solid" number-columns-spanned="4" background-color="silver">
>
> width="1">
> width="80" nb_col="2" position="1" colspan="1" />
> width="2.25cm" />
> width="120" nb_col="2" position="1" colspan="1" />
> width="3.375cm" />
>
> next="always">
> align="center" border-style="solid">
> family="Arial, Helvetica, sans-serif">
> family="Arial, Helvetica, sans-serif" text-align="center">
> font-
> size="10pt">
>
> font-weight="bold">CADRE C
>
>
>
>
> align="center" border-style="solid" text-align="center">
> family="Arial, Helvetica, sans-serif">
> family="Arial, Helvetica, sans-serif" text-align="center">
> font-
> size="10pt">
>
> font-weight="bold">MOUVEMENTS AFFECTANT LA PROVISION POUR AMORTISSEMENTS
> DEROGATOIRES
>
>
>
>
>
>
>
>
>
>
>
> style="solid" number-columns-spanned="2">
>
>
> size="10pt">Immobilisations amortissables
>
>
>
> style="solid" number-columns-spanned="2">
>
>
[jira] [Closed] (FOP-537) blank pages, strange page-numbers
[ https://issues.apache.org/jira/browse/FOP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-537. --- Resolution: Not A Problem move inlined code in description to attachment > blank pages, strange page-numbers > - > > Key: FOP-537 > URL: https://issues.apache.org/jira/browse/FOP-537 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Oscar Schoof >Assignee: fop-dev >Priority: Blocker > Attachments: fop-537-description-with-code.txt > > > With using version 0.20.5rc i get strange blank pages in the pdfs. This is not > the case with the same fo-docs when i process them with the old 0.20.4. (I > tested this by reinstalling 0.20.4.) > For example, in 0.20.4 i see the following flow-processing: > [1] > [1] > [2] > > (There are multiple flows in my docs.) > With 0.20.5rc on the same doc i get: > [1] > [2 (blank)] > [1] > [2] > . > In these docs i use page-number-citation id's to list pages as "page of > ". > With the same example mentioned here i get with 0.20.4 on the first (and last > page) of the first flow: "page 1 of 1", which is correct. With 0.20.5rc i get > on > the first page: "page 1 of 1" and on the second (blank) page: "page 2 of 1", > which is very strange. > Example fo: > See attachment fop-537-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-537) blank pages, strange page-numbers
[ https://issues.apache.org/jira/browse/FOP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-537: Attachment: fop-537-description-with-code.txt > blank pages, strange page-numbers > - > > Key: FOP-537 > URL: https://issues.apache.org/jira/browse/FOP-537 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Oscar Schoof >Assignee: fop-dev >Priority: Blocker > Attachments: fop-537-description-with-code.txt > > > With using version 0.20.5rc i get strange blank pages in the pdfs. This is not > the case with the same fo-docs when i process them with the old 0.20.4. (I > tested this by reinstalling 0.20.4.) > For example, in 0.20.4 i see the following flow-processing: > [1] > [1] > [2] > > (There are multiple flows in my docs.) > With 0.20.5rc on the same doc i get: > [1] > [2 (blank)] > [1] > [2] > . > In these docs i use page-number-citation id's to list pages as "page of > ". > With the same example mentioned here i get with 0.20.4 on the first (and last > page) of the first flow: "page 1 of 1", which is correct. With 0.20.5rc i get > on > the first page: "page 1 of 1" and on the second (blank) page: "page 2 of 1", > which is very strange. > Example fo: > See attachment fop-537-description-with-code.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-537) blank pages, strange page-numbers
[ https://issues.apache.org/jira/browse/FOP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-537: Description: With using version 0.20.5rc i get strange blank pages in the pdfs. This is not the case with the same fo-docs when i process them with the old 0.20.4. (I tested this by reinstalling 0.20.4.) For example, in 0.20.4 i see the following flow-processing: [1] [1] [2] (There are multiple flows in my docs.) With 0.20.5rc on the same doc i get: [1] [2 (blank)] [1] [2] . In these docs i use page-number-citation id's to list pages as "page of ". With the same example mentioned here i get with 0.20.4 on the first (and last page) of the first flow: "page 1 of 1", which is correct. With 0.20.5rc i get on the first page: "page 1 of 1" and on the second (blank) page: "page 2 of 1", which is very strange. Example fo: See attachment fop-537-description-with-code.txt was: With using version 0.20.5rc i get strange blank pages in the pdfs. This is not the case with the same fo-docs when i process them with the old 0.20.4. (I tested this by reinstalling 0.20.4.) For example, in 0.20.4 i see the following flow-processing: [1] [1] [2] (There are multiple flows in my docs.) With 0.20.5rc on the same doc i get: [1] [2 (blank)] [1] [2] . In these docs i use page-number-citation id's to list pages as "page of ". With the same example mentioned here i get with 0.20.4 on the first (and last page) of the first flow: "page 1 of 1", which is correct. With 0.20.5rc i get on the first page: "page 1 of 1" and on the second (blank) page: "page 2 of 1", which is very strange. Example fo: http://www.w3.org/1999/XSL/Format; xmlns:xlink="http://www.w3.org/1999/xlink; font-family="Helvetica" font-size="9pt" > - Deze analyse-certificaat heeft niet de eindkontrole op samenhang en niveau doorlopen. - Het voorblad bij deze tabel vormt een integraal onderdeel van dit certificaat. - De met een 'Q' gemerkte analyses zijn door STERLAB geaccrediteerd. - Indien niet alle verbindingen aantoonbaar, zijn sommaties gebaseerd op de helft van de detectiegrens. Ref.: 085161_auto-fax_v0 OMEGAM laboratorium H.J.E. Wenckebachweg 120,1096 AR Amsterdam Tel. 020597 Fax 0205976777 Tabel van A N A L Y S E - C E R T I F I C A A T Project code : project code Project omschrijving : project descr Opdrachtgever : client descr Referenties 5123422 = M1 5123423 = M2 Opgegeven bemon.datum : 19/12/2002 19/12/2002 Ontvangsdatum : 20/12/2002 20/12/2002 Monstercode : 5123422 5123423 Materiaal : Bouwstof Bouwstof Bouwstoffenbesluit samenstellingsonderzoek Monstervoorbewerking: Q Start datum 201202 201202 Algemeen onderzoek - fysisch: Q droogrest % 93 ,2 92 ,4 Q organische stof % (m/m ds) 2 ,1 1 ,8 Q lutum % (m/m ds) 1 ,3 1 ,1 Q pH-CaCl2 7 ,9 8 ,3 Anorganische parameters - metalen: Q arseen [As] mg/kg ds 4 ,1 4 Q cadmium [Cd] mg/kg ds 0 ,4 0 ,4 Q chroom [Cr] mg/kg ds 15 15 Q koper [Cu] mg/kg ds 10 11 Q kwik [Hg] mg/kg ds 0 ,07 0 ,07 Q lood [Pb] mg/kg ds 26 27 Q nikkel [Ni] mg/kg ds 7 8 Q zink [Zn] mg/kg ds 46 47 Organische parameters - niet aromatisch: Q minerale olie mg/kg ds 20 20 Organische parameters - aromatisch: Q naftaleen mg/kg ds 0 ,01 0 ,01 Q acenaftyleen mg/kg ds 0 ,01 0 ,01 Q acenafteen mg/kg ds 0 ,05 0 ,02 Q fluoreen mg/kg ds 0 ,03 0 ,01 Q fenanthreen mg/kg ds 0 ,55 0 ,22 Q anthraceen mg/kg ds 0 ,14 0 ,05 Q fluorantheen mg/kg ds 1 ,1 0 ,44 Q pyreen mg/kg ds 0 ,84 0 ,35 Q benz(a)anthraceen mg/kg ds 0 ,45 0 ,22 Q chryseen mg/kg ds 0 ,43 0 ,19 Q benzo(b)fluorantheen mg/kg ds 0 ,51 0 ,23 Q benzo(k)fluorantheen mg/kg ds 0 ,23 0 ,10 Q benzo(a)pyreen mg/kg ds 0 ,51 0 ,22 Q dibenz(a,h)anthraceen mg/kg ds 0 ,06 0 ,02 Q benzo(ghi)peryleen mg/kg ds 0 ,38 0 ,18 Q indeno(1,2,3cd)pyreen mg/kg ds 0 ,34 0 ,14 Sommatie PAK-10 mg/kg ds 4 ,1 1 ,8 Organische parameters - gehalogeneerd: Q extr. org. halogeen mg/kg ds 0 ,1 0 ,1 OMEGAM laboratorium H.J.E. Wenckebachweg 120,1096 AR Amsterdam Tel. 020597 Fax 0205976777 Oliechromatogram van ANALYSEMETHODE Voorbewerking grond:Hexaanextractie afgeleid van NEN 5733. Voorbewerking AP04:Petroleum-etherextractie conform NEN 5733. Voorbewerking water:Hexaanextractie afgeleid van NVN 6678. Analyse:Gaschromatograaf met capillaire kolom en vlamionisatie detectie. Interpretatie:Raadpleeg voor de typering van de oliesoort de OMEGAM oliebibliotheek. Bij grondmonsters is als optie clean-up
[jira] [Reopened] (FOP-537) blank pages, strange page-numbers
[ https://issues.apache.org/jira/browse/FOP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-537: - > blank pages, strange page-numbers > - > > Key: FOP-537 > URL: https://issues.apache.org/jira/browse/FOP-537 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.5 > Environment: Operating System: All > Platform: PC >Reporter: Oscar Schoof >Assignee: fop-dev > > With using version 0.20.5rc i get strange blank pages in the pdfs. This is not > the case with the same fo-docs when i process them with the old 0.20.4. (I > tested this by reinstalling 0.20.4.) > For example, in 0.20.4 i see the following flow-processing: > [1] > [1] > [2] > > (There are multiple flows in my docs.) > With 0.20.5rc on the same doc i get: > [1] > [2 (blank)] > [1] > [2] > . > In these docs i use page-number-citation id's to list pages as "page of > ". > With the same example mentioned here i get with 0.20.4 on the first (and last > page) of the first flow: "page 1 of 1", which is correct. With 0.20.5rc i get > on > the first page: "page 1 of 1" and on the second (blank) page: "page 2 of 1", > which is very strange. > Example fo: > > http://www.w3.org/1999/XSL/Format; > xmlns:xlink="http://www.w3.org/1999/xlink; font-family="Helvetica" > font-size="9pt" > > > >page-height="29.7cm" > page-width="21cm" > margin-top="3.5cm" > margin-bottom="1.5cm" > margin-left="2.5cm" > margin-right="2.2cm"> > > > > >page-height="29.7cm" > page-width="21cm" > margin-top="0.8cm" > margin-bottom="0.7cm" > margin-left="1.7cm" > margin-right="2.2cm"> > > > > >page-height="29.7cm" > page-width="21cm" > margin-top="1.0cm" > margin-bottom="1.5cm" > margin-left="1.7cm" > margin-right="2.2cm"> > > > > >page-height="29.7cm" > page-width="21cm" > margin-top="1.4cm" > margin-bottom="1.5cm" > margin-left="1.7cm" > margin-right="2.2cm"> > > > > > > > > rule-style="double"> > - Deze analyse-certificaat heeft niet de eindkontrole op samenhang > en > niveau doorlopen. > - Het voorblad bij deze tabel vormt een integraal onderdeel van dit > certificaat. > - De met een 'Q' gemerkte analyses zijn door STERLAB > geaccrediteerd. > - Indien niet alle verbindingen aantoonbaar, zijn sommaties > gebaseerd > op de helft van de detectiegrens. > Ref.: 085161_auto-fax_v0 > > > column-width="20mm"/> column-width="76mm"/> > width="15mm" height="15mm" /> > OMEGAM > laboratorium > H.J.E. Wenckebachweg 120,1096 AR Amsterdam >Tel. 020597 Fax 0205976777 > src="file:sterlabq.gif" width="7mm" height="11.2mm" /> space-before="5pt" >Tabel van ref-id="lasttabelpage"/> > > rule-style="double"> > A N A L Y S E - C E R T I F > I > C A A T > leader-pattern="rule" rule-thickness="0.5pt"> > > > > > > > Project > code > : > project > code > > > Project > omschrijving > : > project > descr > > > font-weight="bold">Opdrachtgever > : > client > descr > > > leader-pattern="rule" rule-thickness="1.7pt" > rule-style="double"> > Referenties > 5123422 = M1 > 5123423 = M2 > > rule-thickness="0.5pt"> > > > > > > > > > Opgegeven > bemon.datum > : > font-weight="bold">19/12/2002 > font-weight="bold">19/12/2002 > > > font-weight="bold">Ontvangsdatum > : > font-weight="bold">20/12/2002 > font-weight="bold">20/12/2002 > > > font-weight="bold">Monstercode > : > font-weight="bold">5123422 > font-weight="bold">5123423 > > > font-weight="bold">Materiaal > : > font-weight="bold">Bouwstof > font-weight="bold">Bouwstof > > > leader-pattern="rule" rule-thickness="0.5pt"> > > > > > > > > > > > > > > > > > > keep-with-next="always" >Bouwstoffenbesluit > samenstellingsonderzoek > > keep-with-next="always">Monstervoorbewerking: > > Q > Start datum > > text-align="right">201202 > text-align="left"> > > text-align="right">201202 > text-align="left"> > > > > > > > > > > > > > > > > > > > > > > keep-with-next="always">Algemeen onderzoek - > fysisch: > > Q > droogrest > % > text-align="right">93 > text-align="left">,2 > > text-align="right">92 > text-align="left">,4 > > > > Q > organische stof > % (m/m ds) > text-align="right">2 > text-align="left">,1 >
[jira] [Closed] (FOP-496) basic-link problem
[ https://issues.apache.org/jira/browse/FOP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-496. --- Resolution: Incomplete move inlined code from description to attachment > basic-link problem > -- > > Key: FOP-496 > URL: https://issues.apache.org/jira/browse/FOP-496 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.20.4 > Environment: Operating System: All > Platform: PC >Reporter: Sergio >Assignee: fop-dev > Attachments: fop-496-description-with-code.txt > > > I'm rendering a pdf file of 22 pages. > at the first of the file, I have the following basic links: > > see attachment fop-496-description-with-code.txt > [^fop-496-description-with-code.txt] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-470) [PATCH] Performance tuning
[ https://issues.apache.org/jira/browse/FOP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-470. --- Resolution: Fixed remove inlined patch from description > [PATCH] Performance tuning > -- > > Key: FOP-470 > URL: https://issues.apache.org/jira/browse/FOP-470 > Project: FOP > Issue Type: Improvement > Components: unqualified >Affects Versions: 0.20.4 > Environment: Operating System: All > Platform: PC >Reporter: Henrik Olsson >Assignee: fop-dev >Priority: Blocker > Attachments: cool.patch, performanceTuning.patch, > performanceTuning.zip > > > Made some changes to the fop-0.20.4 that makes it run about 20-30% faster. > Whats done: removed alot of code that made to many strings and unnecessary > objects. > (I know i promised more but...) > diff: > see attachments -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-291) FopServlet does not work!
[ https://issues.apache.org/jira/browse/FOP-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-291. --- Resolution: Incomplete move inlined code in description into attachments > FopServlet does not work! > - > > Key: FOP-291 > URL: https://issues.apache.org/jira/browse/FOP-291 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.20.3 > Environment: Operating System: All > Platform: PC >Reporter: choad >Assignee: fop-dev >Priority: Blocker > Attachments: fop-291-example.xml, fop-291-stacktrace.txt > > > FopServlet and FopPrintServlet, as provided in the 20.3 distribution, do not > work with params 'xsl' and 'xml'. They DO work with param 'fo' > The following error traceback is generated when FopServlet is invoked as: > > http://blah.blah.blah/fop/servlet/FopServlet?xml=c:/testing/f77PDF- > pg1.xml="c:\testing/toPDF.xsl" > Note the above xsl file contains the lines: > example input-- > See attached fop-291-example.xml > error traceback- > See attached fop-291-stacktrace.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-291) FopServlet does not work!
[ https://issues.apache.org/jira/browse/FOP-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-291: Attachment: fop-291-stacktrace.txt fop-291-example.xml Description: FopServlet and FopPrintServlet, as provided in the 20.3 distribution, do not work with params 'xsl' and 'xml'. They DO work with param 'fo' The following error traceback is generated when FopServlet is invoked as: http://blah.blah.blah/fop/servlet/FopServlet?xml=c:/testing/f77PDF- pg1.xml="c:\testing/toPDF.xsl" Note the above xsl file contains the lines: example input-- See attached fop-291-example.xml error traceback- See attached fop-291-stacktrace.txt was: FopServlet and FopPrintServlet, as provided in the 20.3 distribution, do not work with params 'xsl' and 'xml'. They DO work with param 'fo' The following error traceback is generated when FopServlet is invoked as: "http://blah.blah.blah/fop/servlet/FopServlet?xml=c:/testing/f77PDF- pg1.xml="c:\testing/toPDF.xsl> Note the above xsl file contains the line: http://www.w3.org/1999/XSL/Transform; xmlns:fo="http://www.w3.org/1999/XSL/Format; > error traceback- Error: 500 Location: /fop/servlet/FopServlet Internal Servlet Error: javax.servlet.ServletException at FopServlet.renderXML(FopServlet.java:131) at FopServlet.doGet(FopServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) at org.apache.tomcat.core.ContextManager.service(Unknown Source) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection (Unknown Source) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (Unknown Source) at java.lang.Thread.run(Thread.java:484) Root cause: org.apache.fop.apps.FOPException at org.apache.fop.apps.XSLTInputHandler.getParser (XSLTInputHandler.java:109) at FopServlet.renderXML(FopServlet.java:124) at FopServlet.doGet(FopServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) at org.apache.tomcat.core.ContextManager.service(Unknown Source) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection (Unknown Source) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (Unknown Source) at java.lang.Thread.run(Thread.java:484) - java.lang.reflect.InvocationTargetException: org.apache.fop.apps.FOPException: stylesheet requires attribute: version at org.apache.fop.apps.TraxInputHandler.getXMLFilter (TraxInputHandler.java:103) at java.lang.reflect.Method.invoke(Native Method) at org.apache.fop.apps.XSLTInputHandler.getParser (XSLTInputHandler.java:102) at FopServlet.renderXML(FopServlet.java:124) at FopServlet.doGet(FopServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) at org.apache.tomcat.core.ContextManager.service(Unknown Source) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection (Unknown Source) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (Unknown Source) at java.lang.Thread.run(Thread.java:484) - javax.xml.transform.TransformerConfigurationException: stylesheet requires
[jira] [Reopened] (FOP-291) FopServlet does not work!
[ https://issues.apache.org/jira/browse/FOP-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-291: - > FopServlet does not work! > - > > Key: FOP-291 > URL: https://issues.apache.org/jira/browse/FOP-291 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.20.3 > Environment: Operating System: All > Platform: PC >Reporter: choad >Assignee: fop-dev > > FopServlet and FopPrintServlet, as provided in the 20.3 distribution, do not > work with params 'xsl' and 'xml'. They DO work with param 'fo' > The following error traceback is generated when FopServlet is invoked as: > > "http://blah.blah.blah/fop/servlet/FopServlet?xml=c:/testing/f77PDF- > pg1.xml="c:\testing/toPDF.xsl> > Note the above xsl file contains the line: > xmlns:xsl="http://www.w3.org/1999/XSL/Transform; > xmlns:fo="http://www.w3.org/1999/XSL/Format; > > > error traceback- > Error: 500 > Location: /fop/servlet/FopServlet > Internal Servlet Error: > javax.servlet.ServletException > at FopServlet.renderXML(FopServlet.java:131) > at FopServlet.doGet(FopServlet.java:73) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) > at org.apache.tomcat.core.Handler.invoke(Unknown Source) > at org.apache.tomcat.core.Handler.service(Unknown Source) > at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) > at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) > at org.apache.tomcat.core.ContextManager.service(Unknown Source) > at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection > (Unknown Source) > at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (Unknown Source) > at java.lang.Thread.run(Thread.java:484) > Root cause: > org.apache.fop.apps.FOPException > at org.apache.fop.apps.XSLTInputHandler.getParser > (XSLTInputHandler.java:109) > at FopServlet.renderXML(FopServlet.java:124) > at FopServlet.doGet(FopServlet.java:73) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) > at org.apache.tomcat.core.Handler.invoke(Unknown Source) > at org.apache.tomcat.core.Handler.service(Unknown Source) > at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) > at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) > at org.apache.tomcat.core.ContextManager.service(Unknown Source) > at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection > (Unknown Source) > at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (Unknown Source) > at java.lang.Thread.run(Thread.java:484) > - > java.lang.reflect.InvocationTargetException: > org.apache.fop.apps.FOPException: > stylesheet requires attribute: version > at org.apache.fop.apps.TraxInputHandler.getXMLFilter > (TraxInputHandler.java:103) > at java.lang.reflect.Method.invoke(Native Method) > at org.apache.fop.apps.XSLTInputHandler.getParser > (XSLTInputHandler.java:102) > at FopServlet.renderXML(FopServlet.java:124) > at FopServlet.doGet(FopServlet.java:73) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) > at org.apache.tomcat.core.Handler.invoke(Unknown Source) > at org.apache.tomcat.core.Handler.service(Unknown Source) > at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) > at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) > at org.apache.tomcat.core.ContextManager.service(Unknown Source) > at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection > (Unknown Source) > at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (Unknown Source) > at java.lang.Thread.run(Thread.java:484) > - > javax.xml.transform.TransformerConfigurationException: stylesheet requires > attribute: version > at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates > (TransformerFactoryImpl.java:815) > at
[jira] [Closed] (FOP-173) Table Split over 2 pages (Race condition???)
[ https://issues.apache.org/jira/browse/FOP-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-173. --- Resolution: Incomplete move inlined code in description into attachments > Table Split over 2 pages (Race condition???) > > > Key: FOP-173 > URL: https://issues.apache.org/jira/browse/FOP-173 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: All > URL: http://kofal.opencon.ch >Reporter: kof >Assignee: fop-dev >Priority: Blocker > Attachments: fop-173-source.xml, fop-173-stylesheet.xml > > > The XML data below, when combined with the XSL data in versions .16, .17, .18 > produces a table whose last row is split over 2 pages. I have added borders > on > the cells that are drawn to highlight the issue. > In version 0.20.1, the condition is resolved, but ONLY if the Fop application > is run on an xml:fo file from disk (when called with the -xsl xslFile > parameter, it produces an error message regarding only Table Rows are allowed > children of Table, Table Header, or Table Footer). > Big files with lots of instructions, but it should work and it doesn't: > XML DATA > ** > See attached fop-173-source.xml > XSL DATA > ** > See attached fop-173-stylesheet.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FOP-159) Table header sometimes does not work.
[ https://issues.apache.org/jira/browse/FOP-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-159. --- Resolution: Fixed > Table header sometimes does not work. > - > > Key: FOP-159 > URL: https://issues.apache.org/jira/browse/FOP-159 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: password >Assignee: fop-dev >Priority: Blocker > Attachments: fop-159-example.xml > > > The fop I used is from xml-fop_20010810161621.tar.gz > The .fo file I generated is as follows. On page 9 the first table should have > header displaying "Fixed advances", but it does not show in the PDF. > > See attachment fop-159-example.xml > > Regards, > Hongzhi Sun -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-159) Table header sometimes does not work.
[ https://issues.apache.org/jira/browse/FOP-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-159: Attachment: fop-159-example.xml > Table header sometimes does not work. > - > > Key: FOP-159 > URL: https://issues.apache.org/jira/browse/FOP-159 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: password >Assignee: fop-dev >Priority: Blocker > Attachments: fop-159-example.xml > > > The fop I used is from xml-fop_20010810161621.tar.gz > The .fo file I generated is as follows. On page 9 the first table should have > header displaying "Fixed advances", but it does not show in the PDF. > > See attachment fop-159-example.xml > > Regards, > Hongzhi Sun -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-2652) SVG image relative url is broken when rednering PDF
[
https://issues.apache.org/jira/browse/FOP-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams resolved FOP-2652.
--
Resolution: Fixed
Resolved in FOP 2.8.
> SVG image relative url is broken when rednering PDF
> ---
>
> Key: FOP-2652
> URL: https://issues.apache.org/jira/browse/FOP-2652
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: Windows 7 x64
> java 1.8.0_102 64-Bit
>Reporter: Sergey B.
>Priority: Major
> Attachments: batik-svg-error.zip
>
>
> When rendering fo-file into PDF urls to svg images are treated incorrectly
> because some extra componets are preprended to them. Other images with
> similar urls works fine.
> {code}
> doesn't work
> has no problem
> {code}
> Files to reproduce are in zip archive batik-svg-error.zip.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (FOP-2652) SVG image relative url is broken when rednering PDF
[
https://issues.apache.org/jira/browse/FOP-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams reopened FOP-2652:
--
> SVG image relative url is broken when rednering PDF
> ---
>
> Key: FOP-2652
> URL: https://issues.apache.org/jira/browse/FOP-2652
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: Windows 7 x64
> java 1.8.0_102 64-Bit
>Reporter: Sergey B.
>Priority: Major
> Attachments: batik-svg-error.zip
>
>
> When rendering fo-file into PDF urls to svg images are treated incorrectly
> because some extra componets are preprended to them. Other images with
> similar urls works fine.
> {code}
> doesn't work
> has no problem
> {code}
> Files to reproduce are in zip archive batik-svg-error.zip.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FOP-2652) SVG image relative url is broken when rednering PDF
[
https://issues.apache.org/jira/browse/FOP-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams closed FOP-2652.
Resolution: Won't Do
Resolved in FOP 2.8.
> SVG image relative url is broken when rednering PDF
> ---
>
> Key: FOP-2652
> URL: https://issues.apache.org/jira/browse/FOP-2652
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: Windows 7 x64
> java 1.8.0_102 64-Bit
>Reporter: Sergey B.
>Priority: Major
> Attachments: batik-svg-error.zip
>
>
> When rendering fo-file into PDF urls to svg images are treated incorrectly
> because some extra componets are preprended to them. Other images with
> similar urls works fine.
> {code}
> doesn't work
> has no problem
> {code}
> Files to reproduce are in zip archive batik-svg-error.zip.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-1722) [PATCH] Values in PDF Number Trees must be indirect references
[ https://issues.apache.org/jira/browse/FOP-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701798#comment-17701798 ] Glenn Adams commented on FOP-1722: -- LGTM [patch3.txt]. > [PATCH] Values in PDF Number Trees must be indirect references > -- > > Key: FOP-1722 > URL: https://issues.apache.org/jira/browse/FOP-1722 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: All >Reporter: Vincent Hennebert > Attachments: patch3.txt, text.fo, text.pdf > > > See PDF Reference, Third Edition, Section 3.8.5, "Number Trees": the Nums > entry > must be an array of key-value pairs where value is an indirect reference to > the > object associated with the key. > However, the o.a.f.pdf.PDFNumsArray class does nothing to ensure that elements > added to the array are actually indirectly referenced. So generated PDFs are > strictly speaking invalid. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3098) [PATCH] Nullpointer Exception in LMiter.next depending on text
[
https://issues.apache.org/jira/browse/FOP-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698652#comment-17698652
]
Glenn Adams commented on FOP-3098:
--
[~jeremias] Nice to see you are still here. To elaborate on Simon's message, we
recently migrated the XMLGraphics repositories from SVN to GitHub/GitBox. The
SVN repository is now read-only, and not synchronized with GitHub; however, the
GitHub/GitBox repositories have the entire history of commits from SVN.
> [PATCH] Nullpointer Exception in LMiter.next depending on text
> --
>
> Key: FOP-3098
> URL: https://issues.apache.org/jira/browse/FOP-3098
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Michael Heitkamp
>Assignee: Chris Bowditch
>Priority: Major
> Fix For: main
>
> Attachments: Post-FOP-3098-NPE-Bugfix.diff, patch.txt,
> patch_cached.txt, stacktrace.txt, x-fop-error.xml, x-fop-error.xsl
>
>
> Doing a FOP translation with the given XSL and XML input files lead to a
> Nullpointer Exception.
> If the text block is shortened by one character ("dataX" -> "data") then the
> translation succeeds.
> If the text block is replaced by "lore ipsum" of the same length then the
> translation succeeds also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FOP-82) Table Column overflow - endless loop
[ https://issues.apache.org/jira/browse/FOP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-82: --- Attachment: fop-82-example.xml Description: I have a single page document that basically consists of 3 columns. Each column is further divided with additional tables. Each columns contains a number of tables. The first column containing a single table. Columns 2 has 3 tables and columns 3 has 1 table. Col 1 Col 2 Col 3 -- | | | | | Table | Table| Table | | 3 cols | 3 cols | 2 cols | | |--|-| : : Table: : : : 2 cols : : | |--| | | | | | | | Table| | | | 2 cols | | | | | | -- A problem occurs when to much data is entered into the first column. There is not enough data to cause the page to overflow. Removing the data from columns 2 and 3 results in the correct PDF generation. Reducing the column 1 dataset down to approximately 10 rows resolves the problem. Any more and an endless loop results. The FO from the attached file (fop-82-example.xml) has been run through versions 0.14 to 0.18, each with the same result. Any help would be appreciated. was: I have a single page document that basically consists of 3 columns. Each column is further divided with additional tables. Each columns contains a number of tables. The first column containing a single table. Columns 2 has 3 tables and columns 3 has 1 table. Col 1 Col 2 Col 3 -- | | | | | Table | Table| Table | | 3 cols | 3 cols | 2 cols | | |--|-| : : Table: : : : 2 cols : : | |--| | | | | | | | Table| | | | 2 cols | | | | | | -- A problem occurs when to much data is entered into the first column. There is not enough data to cause the page to overflow. Removing the data from columns 2 and 3 results in the correct PDF generation. Reducing the column 1 dataset down to approximately 10 rows resolves the problem. Any more and an endless loop results. The output below has been run through versions 0.14 to 0.18, each with the same result. Any help would be appreciated. http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/Xlink; xmlns:fo="http://www.w3.org/1999/XSL/Format;> TRAIT HIERARCHY REPORTGary Freeman11 JULY 2000 Copyright (c) 1991-2000 Gary Freeman Page Consistency Score:90 PERSONALITY TRAITS Score Incon. Analytical 9.9 0 Analyzes Pitfalls 9.7 0 Assertive 9.6 0 Authoritative 9.6 0 Cause Motivated 9.4 0 Certain 9.2 0 Collaborative 9.1 0 Comfort with Conflict 9.0 0 Creative Thinking 9.0 0 Diplomatic 8.7 0 Enforcing 8.6 0 Enlists Cooperation 8.5 0 Enthusiastic 8.3 7 Flexible 8.2 0 Frank 8.1 0 Helpful 8.0 0 Influencing 7.8 19 Intuitive 7.7 17 Manages Stress Well 7.6 15 Open/Reflective 7.5 16 Optimistic 7.3 13 Organized 7.2 17 Outgoing 7.1 0 Persistent 7.0 15 Planning 6.8 23 Precise 6.7 17 Relaxed 6.6 23 Risking 6.4 0 Self-Acceptance 6.3 9 Self-Improvement 6.2 22 Self-Motivated 6.1 0 Systematic 6.1 23 Takes Initiative 5.8 22 Tempo 5.7 0 Tolerance of Bluntness 5.7 0 Tolerance of Structure 5.7 28 Wants Autonomy 5.7 0 Wants Capable Leader 5.7 0 Wants Challenge 5.7 0 Wants Diplomacy 7.7 24 Wants Frankness 6.7 0 Wants High Pay 5.7 0 Wants Recognition 3.7 7 Wants Stable Career 8.7 0 Wants to Lead 4.7 0 Warmth/Empathy 7.7 0 Physical Work 3.3 0 Public Speaking 3.0 0 Research/Learning 2.9 0 Teaching 2.8 0 N/A 2.6 0 ENVIRONMENTAL PREFERENCES Score Incon. Noise 2.5 0 Outdoors 2.4 0 Pressure 2.4 0 Public Contact 2.4 0 Repetition 2.0 0 Sitting 9.4 0 Standing 9.2 0 Team 9.1 0 INTERESTS Score FINANCE/BUSINESS 8.2 SPORTS 7.1 TRAVEL 7.1 ELECTRONICS 6.8 CHILDREN 6.7 SCIENCE 5.6 WRITING/LANGUAGE 5.4
[jira] [Resolved] (FOP-82) Table Column overflow - endless loop
[ https://issues.apache.org/jira/browse/FOP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams resolved FOP-82. Resolution: Fixed > Table Column overflow - endless loop > > > Key: FOP-82 > URL: https://issues.apache.org/jira/browse/FOP-82 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: gary >Assignee: fop-dev >Priority: Blocker > Attachments: fop-82-example.xml > > > I have a single page document that basically consists of 3 columns. Each > column > is further divided with additional tables. Each columns contains a number of > tables. The first column containing a single table. Columns 2 has 3 tables > and > columns 3 has 1 table. >Col 1 Col 2 Col 3 > -- > | | | | > | Table | Table| Table | > | 3 cols | 3 cols | 2 cols | > | |--|-| > : : Table: : > : : 2 cols : : > | |--| | > | | | | > | | Table| | > | | 2 cols | | > | | | | > -- > A problem occurs when to much data is entered into the first column. > There is not enough data to cause the page to overflow. Removing the data > from > columns 2 and 3 results in the correct PDF generation. Reducing the column 1 > dataset down to approximately 10 rows resolves the problem. Any more and an > endless loop results. > The FO from the attached file (fop-82-example.xml) has been run through > versions 0.14 to 0.18, each with the same result. > Any help would be appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (FOP-82) Table Column overflow - endless loop
[ https://issues.apache.org/jira/browse/FOP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-82: > Table Column overflow - endless loop > > > Key: FOP-82 > URL: https://issues.apache.org/jira/browse/FOP-82 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: PC >Reporter: gary >Assignee: fop-dev > > I have a single page document that basically consists of 3 columns. Each > column > is further divided with additional tables. Each columns contains a number of > tables. The first column containing a single table. Columns 2 has 3 tables > and > columns 3 has 1 table. >Col 1 Col 2 Col 3 > -- > | | | | > | Table | Table| Table | > | 3 cols | 3 cols | 2 cols | > | |--|-| > : : Table: : > : : 2 cols : : > | |--| | > | | | | > | | Table| | > | | 2 cols | | > | | | | > -- > A problem occurs when to much data is entered into the first column. > There is not enough data to cause the page to overflow. Removing the data > from > columns 2 and 3 results in the correct PDF generation. Reducing the column 1 > dataset down to approximately 10 rows resolves the problem. Any more and an > endless loop results. > The output below has been run through versions 0.14 to 0.18, each with > the > same result. > Any help would be appreciated. > > http://www.w3.org/2000/svg; > xmlns:xlink="http://www.w3.org/1999/Xlink; > xmlns:fo="http://www.w3.org/1999/XSL/Format;> > > bottom="1.2cm" margin-top="1cm" page-width="21.59cm" page-height="27.94cm" > master-name="first"> > > > > > bottom="1.2cm" margin-top="1cm" page-width="21.59cm" page-height="27.94cm" > master-name="rest"> > > > > > > > name="first"/> > master-name="rest"/> > > > > > > > > xlink:href="file:LOGO5.jpg" height="75px" width="400px" y="0" > x="0"/> y="25" x="180" style="font-size:16; font-weight:bold; > font-family:serif">TRAIT > HIERARCHY REPORTGary Freeman11 JULY 2000 > > > > > > position="absolute"> > pattern="rule"/> > > height="12pt" height="1cm" width="17.59cm" top="0.3cm" left="0cm" > position="absolute"> > > > > > > > > Copyright (c) 1991-2000 Gary Freeman > > > > > Page > > > > Consistency Score:90 > > > > > > > > > > > > > > > > > > > > > > > > bottom-width="0pt" padding-left="0pt"> > space-before.optimum="2pt" > text-align="start" font-family="sans-serif" font-weight="bold">PERSONALITY > TRAITS > > > bottom-width="0pt"> > before.optimum="2pt" text-align="start" font-family="sans-serif" font- > weight="bold">Score > > > bottom-width="0pt"> > before.optimum="2pt" text-align="center" font-family="sans-serif" font- > weight="bold">Incon. > > > > > > height="11pt">Analytical > > > > height="11pt">9.9 > > > > height="11pt">0 > > > > > > height="11pt">Analyzes Pitfalls > > > > height="11pt">9.7 > > > > height="11pt">0 > > > > > > height="11pt">Assertive > > > > height="11pt">9.6 > > > > height="11pt">0 > > > > > > height="11pt">Authoritative > > > > height="11pt">9.6 > > > > height="11pt">0 > > > > > > height="11pt">Cause Motivated > > > > height="11pt">9.4 > > > > height="11pt">0 > > > > > > height="11pt">Certain > > > > height="11pt">9.2 > > > > height="11pt">0 > > > > > > height="11pt">Collaborative > > > > height="11pt">9.1 > > > > height="11pt">0 > > > > > > height="11pt">Comfort with Conflict > > > > height="11pt">9.0 > > > > height="11pt">0 > > > > > > height="11pt">Creative Thinking > > > > height="11pt">9.0 > > > > height="11pt">0 > > > > > > height="11pt">Diplomatic > > > > height="11pt">8.7 > > > > height="11pt">0 > > > > > > height="11pt">Enforcing > > > > height="11pt">8.6 > > > > height="11pt">0 > > > > > > height="11pt">Enlists Cooperation > > > > height="11pt">8.5 > > > > height="11pt">0 > > > > > > height="11pt">Enthusiastic > > > > height="11pt">8.3 > > > > height="11pt">7 > > > > > > height="11pt">Flexible > > > > height="11pt">8.2 > > > > height="11pt">0 > > > > > > height="11pt">Frank > > > > height="11pt">8.1 > > > > height="11pt">0 > > > > > > height="11pt">Helpful > > > > height="11pt">8.0 > > > > height="11pt">0 > > > > > > height="11pt">Influencing > > > > height="11pt">7.8 > > > > height="11pt">19 > > > > > >
[jira] [Closed] (FOP-46) incorrect page breaks using tables leaving large amounts of white space
[ https://issues.apache.org/jira/browse/FOP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-46. -- Resolution: Fixed > incorrect page breaks using tables leaving large amounts of white space > --- > > Key: FOP-46 > URL: https://issues.apache.org/jira/browse/FOP-46 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.17 > Environment: Operating System: other > Platform: PC >Reporter: Matthew Weiss >Assignee: Glenn Adams >Priority: Blocker > Attachments: fop-46-example.xml > > > maxHeight in xml-fop\src\org\apache\fop\layout\Area.java appears to be > improperly calculated when it intreprets the amount of page remaining when > working with tables. For now, I am band-aiding the problem by simply adding a > constant to maxHeight in order to get my particular table-rich document to > work. > The attached fo test document (fop-46-example.xml) illustrates this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-46) incorrect page breaks using tables leaving large amounts of white space
[ https://issues.apache.org/jira/browse/FOP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-46: --- Attachment: fop-46-example.xml Description: maxHeight in xml-fop\src\org\apache\fop\layout\Area.java appears to be improperly calculated when it intreprets the amount of page remaining when working with tables. For now, I am band-aiding the problem by simply adding a constant to maxHeight in order to get my particular table-rich document to work. The attached fo test document (fop-46-example.xml) illustrates this. was: maxHeight in xml-fop\src\org\apache\fop\layout\Area.java appears to be improperly calculated when it intreprets the amount of page remaining when working with tables. For now, I am band-aiding the problem by simply adding a constant to maxHeight in order to get my particular table-rich document to work. the following fo test document illustrates this: http://www.w3.org/1999/XSL/Format;> line 0 line 0 line 0 line 0 line 1 line 1 line 1 line 1
[jira] [Reopened] (FOP-46) incorrect page breaks using tables leaving large amounts of white space
[ https://issues.apache.org/jira/browse/FOP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams reopened FOP-46: Assignee: Glenn Adams (was: fop-dev) > incorrect page breaks using tables leaving large amounts of white space > --- > > Key: FOP-46 > URL: https://issues.apache.org/jira/browse/FOP-46 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.17 > Environment: Operating System: other > Platform: PC >Reporter: Matthew Weiss >Assignee: Glenn Adams > > maxHeight in xml-fop\src\org\apache\fop\layout\Area.java appears to be > improperly calculated when it intreprets the amount of page remaining when > working with tables. For now, I am band-aiding the problem by simply adding > a > constant to maxHeight in order to get my particular table-rich document to > work. > the following fo test document illustrates this: > > > http://www.w3.org/1999/XSL/Format;> > > > >page-height="29.7cm" > page-width="21cm" > margin-top="1cm" > margin-bottom="2cm" > margin-left="2.5cm" > margin-right="2.5cm"> > > > > > > > > > > > > > > > > > > > > > > >border-width="1pt"> > > >size="14pt" > font-family="sans- > serif" > font- > weight="bold" > text-align="start" > padding- > after="2mm"> > line 0 > > > >size="14pt" > font-family="sans- > serif" > font- > weight="bold" > text-align="start"> > line 0 > > > >size="14pt" > font-family="sans- > serif" > font- > weight="bold" > text-align="start"> > line 0 > > > >size="14pt" > font-family="sans- > serif" > font- > weight="bold" > text-align="start"> > line 0 > > > > > > > > > > > > > > > > > > > >
[jira] [Comment Edited] (FOP-1760) [PATCH] FOP doesn't support change bar generation
[ https://issues.apache.org/jira/browse/FOP-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422964#comment-16422964 ] Glenn Adams edited comment on FOP-1760 at 4/2/18 6:51 PM: -- Changing from "bug" to "new feature". Note that this patch is not a fix, but a proposal for a new feature. was (Author: gadams): Changing from "bug" to "new feature". Note that this patch is not a fix, but a proposal for a new feature outside the scope of XSL-FO. > [PATCH] FOP doesn't support change bar generation > - > > Key: FOP-1760 > URL: https://issues.apache.org/jira/browse/FOP-1760 > Project: FOP > Issue Type: New Feature > Components: unqualified >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Stephan Thesing >Priority: Blocker > Attachments: change-bars.fo, change_bars_diff.txt, changebar.diff, > changebar_20110308.diff, changebars.fo, changebars.pdf, > changebars_20110512.diff, diff_1691612.diff, diff_2010_03_06.txt, > fop_20120507.diff, fop_changebars_20120506.diff, > patch_against_rev_1686494_2015-06-19.patch, > patch_against_rev_1690781_2015-07-19.patch, > patch_against_rev_1755460_2016-08-07.patch, > patch_against_rev_1776640_2016-12-30.patch, test.fo, test.pdf > > > In order to produce change bars along the columns for changed contents, > FO supports the fo:change-bar-begin and fo:change-bar-end elements. > These are not supported by FOP. > Support for change bars should be added. > Effort needed > - add parsing and validation of fo: elements > - determine fo elements under influence of one or more change bars > - when creating areas from such affected fo elements, create additional areas > representing the change bars as defined in the FO standard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-1760) [PATCH] FOP doesn't support change bar generation
[ https://issues.apache.org/jira/browse/FOP-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1760: - Priority: Blocker Issue Type: New Feature (was: Bug) Changing from "bug" to "new feature". Note that this patch is not a fix, but a proposal for a new feature outside the scope of XSL-FO. > [PATCH] FOP doesn't support change bar generation > - > > Key: FOP-1760 > URL: https://issues.apache.org/jira/browse/FOP-1760 > Project: FOP > Issue Type: New Feature > Components: unqualified >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Stephan Thesing >Priority: Blocker > Attachments: change-bars.fo, change_bars_diff.txt, changebar.diff, > changebar_20110308.diff, changebars.fo, changebars.pdf, > changebars_20110512.diff, diff_1691612.diff, diff_2010_03_06.txt, > fop_20120507.diff, fop_changebars_20120506.diff, > patch_against_rev_1686494_2015-06-19.patch, > patch_against_rev_1690781_2015-07-19.patch, > patch_against_rev_1755460_2016-08-07.patch, > patch_against_rev_1776640_2016-12-30.patch, test.fo, test.pdf > > > In order to produce change bars along the columns for changed contents, > FO supports the fo:change-bar-begin and fo:change-bar-end elements. > These are not supported by FOP. > Support for change bars should be added. > Effort needed > - add parsing and validation of fo: elements > - determine fo elements under influence of one or more change bars > - when creating areas from such affected fo elements, create additional areas > representing the change bars as defined in the FO standard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FOP-2777) Add .gitignore file to ignore the build folder
[ https://issues.apache.org/jira/browse/FOP-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2777. FOP doesn't use git (yet). > Add .gitignore file to ignore the build folder > -- > > Key: FOP-2777 > URL: https://issues.apache.org/jira/browse/FOP-2777 > Project: FOP > Issue Type: Wish >Affects Versions: trunk >Reporter: Peter Fleck >Priority: Trivial > Labels: git > Attachments: gitignore > > Original Estimate: 1h > Remaining Estimate: 1h > > Add a .gitignore file to ignore the build folder. > I use the git repo from Github as a submodule and when I build I get > "_Untracked files"_. > To keep both the FOP repo and parent repos clean, a gitignore file would > solve this problem. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FOP-2777) Add .gitignore file to ignore the build folder
[ https://issues.apache.org/jira/browse/FOP-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams resolved FOP-2777. -- Resolution: Not A Problem You can use your own .gitignore, and then ignore that .gitignore using a per-user .gitignore, i.e., from ~/.gitignore. > Add .gitignore file to ignore the build folder > -- > > Key: FOP-2777 > URL: https://issues.apache.org/jira/browse/FOP-2777 > Project: FOP > Issue Type: Wish >Affects Versions: trunk >Reporter: Peter Fleck >Priority: Trivial > Labels: git > Attachments: gitignore > > Original Estimate: 1h > Remaining Estimate: 1h > > Add a .gitignore file to ignore the build folder. > I use the git repo from Github as a submodule and when I build I get > "_Untracked files"_. > To keep both the FOP repo and parent repos clean, a gitignore file would > solve this problem. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FOP-2761) java.lang.ArrayIndexOutOfBoundsException - While Processing URDU (RTL) Contents
[ https://issues.apache.org/jira/browse/FOP-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287349#comment-16287349 ] Glenn Adams commented on FOP-2761: -- Hi Muhammad, All work on FOP is based on volunteerism on the part of committers and contributors. I cannot predict when a committer or contributor will address any particular issue. You are free to contribute a patch to resolve this issue. See [1] for further information. [1] https://xmlgraphics.apache.org/fop/dev/#patches Regards, Glenn > java.lang.ArrayIndexOutOfBoundsException - While Processing URDU (RTL) > Contents > --- > > Key: FOP-2761 > URL: https://issues.apache.org/jira/browse/FOP-2761 > Project: FOP > Issue Type: Bug > Components: fo/block >Affects Versions: 2.2 > Environment: I have tested it on Mac OS & Windows 10 >Reporter: Muhammad Shakeel > Attachments: CommandWithErrorLogMessages.txt, Jameel Noori > Nastaleeq.7z, Sample-UrduContents.fo, fop.xconf > > > Hi, > I am getting "java.lang.ArrayIndexOutOfBoundsException" while I am trying to > process the XSL-FO containing Urdu Language text which is RTL and close to an > Arabic Language. > I have tested the same XSL-FO with Antenna House Formatter (Evaluation > Version) and I am not getting this exception when I use that formatter. > I have attached : > 1. Download the .TTF from http://www.urdujahan.com/font.html > 2. The error logs file with the command I have used > 3. XSL-FO file containing the contents I am having issue with > 4. FOP.XCONF File > Please note that I have "Remarked" the contents which is causing the issue. > Please un-comment the remarked contents and checkout the issue. > I hope you review this reported Bug and share your findings with the issue > soon. > NOTE: I am at the moment experiencing issue to upload the .TTF on JIRA that's > why I have shared the download link. > Thank you, > Kind Regards, > Mumammad Shakeel -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2757) [PATCH] page-height="indefinite"
[ https://issues.apache.org/jira/browse/FOP-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266889#comment-16266889 ] Glenn Adams commented on FOP-2757: -- Thanks for submitting, which clears the way for a current committer to schedule a review of the patch content. > [PATCH] page-height="indefinite" > > > Key: FOP-2757 > URL: https://issues.apache.org/jira/browse/FOP-2757 > Project: FOP > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Axel Rose > Attachments: page-indefinite.patch > > > Hello team, > I'd love to contribute the attached code which works already locally > implementing page-height="indefinite" (http://www.w3.org/TR/xsl/#page-height) > Happy to take further questions on this. > Regards, > Axel. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2733) [PATCH] Drop dependency on Avalon-Framework
[ https://issues.apache.org/jira/browse/FOP-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262596#comment-16262596 ] Glenn Adams commented on FOP-2733: -- In other words, the earliest we could apply this patch is when moving to the next major version, FOP 3.0, which is not under consideration at all at this juncture. > [PATCH] Drop dependency on Avalon-Framework > --- > > Key: FOP-2733 > URL: https://issues.apache.org/jira/browse/FOP-2733 > Project: FOP > Issue Type: Bug >Reporter: Chris West > Attachments: fop-no-avalon-1.patch > > > FOP depends on avalon-framework, an old Apache project officially abandoned > in 2004. Nearly nobody uses avalon-framework anymore, and I'd like to see it > laid to rest. > avalon-framework no-longer compiles with Java 9. Fixing it yet again seems > like insanity. This isn't a problem for Maven users, who can keep using the > old binary (and suffer slow verification on startup), but is a problem for > distros like Debian, who want to be able to build everything. > Others have asked about this before, e.g. > http://apache-fop.1065347.n5.nabble.com/FOP-and-Avalon-td44302.html > I propose removing the dependency on Avalon entirely, fixing the couple of > cases where it breaks, and inlining the two packages that are actually still > used.. I have created a patch here: > https://github.com/apache/fop/compare/trunk...FauxFaux:trunk , also attached. > It's not great to read in patch form, so here's a summary of the changes: > * Remove dependence on avalon-framework from Maven, classpath variables etc. > * Add Avalon's configuration package as main:org.apache.fop.configuration > directly, and keep using it essentially unmodified. > * Add Avalon's logging framework as test:org.apache.fop.threading.logger. > This is only used in test code, in the threaded test code runner. It is > essentially source compatible with log4j/commons-logging, so could probably > be deleted. > * Change `CIDFontType` from a Avalon enum to a Java5 `enum`. This appears to > be source, but not binary, compatible. > * Remove some use of lifecycle management interfaces in test code, which are > not doing anything. > * Change some exception printing in test code to print the full exception > (using the Java api), instead of a truncated exception. The output is not > asserted upon, just sent to stderr. > * Stop using Cascading*Exception in tests, and for ConfigurationException. I > doubt anyone will notice, as it offers no real functionality. > That's it! > The most controversial thing here is probably adding the configuration > package, and the extra lines of code it drags along with it. I am happy to > give it a bit of a polish; make significant changes to fop to remove all the > unused interfaces / abstract classes (which are just waste); put some > generics and formatting in, etc.? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FOP-2758) [PATCH] Font Detection fails for custom URI schemes
[
https://issues.apache.org/jira/browse/FOP-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams reassigned FOP-2758:
Assignee: simon steiner
In principle, I support applying this patch, provided an ICLA is on file and
the details of the patch are reviewed for errors.
> [PATCH] Font Detection fails for custom URI schemes
> ---
>
> Key: FOP-2758
> URL: https://issues.apache.org/jira/browse/FOP-2758
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: adam Retter
>Assignee: simon steiner
> Attachments: fop-font-detector-factory.patch
>
>
> If you are using a custom URI scheme with FOP, then auto-detection of fonts
> currently throws an exception, because it assumes the URI is convertible to a
> URL, however Java by default does not support the custom URIs.
> With FOP in eXist-db we use the URI scheme {{exist}} for resolving resolving
> resources from the database.
> Our FOP setup looks like this:
> {code}
> URI baseUri = new URI("exist://localhost" +
> configFile.getOwnerDocument().getBaseURI());
> final ResourceResolverFactory.SchemeAwareResourceResolverBuilder resBuilder =
> ResourceResolverFactory.createSchemeAwareResourceResolverBuilder(ResourceResolverFactory.createDefaultResourceResolver());
> final URIResolverAdapter uriResolver = new URIResolverAdapter(
> new ExistSchemeRewriter(new EXistURIResolver(broker.getBrokerPool(),
> baseUri))
> );
> resBuilder.registerResourceResolverForScheme("exist", uriResolver);
>
> final EnvironmentProfile environment =
> EnvironmentalProfileFactory.createDefault(baseUri, resBuilder.build());
> FopFactoryBuilder builder = new
> FopFactoryBuilder(environment).setConfiguration(cfg);
> {code}
> Our FOP config file looks like:
> {code}
>
>
>
>
>
>
>
>
>
> {code}
> The error occurs because of these lines in
> {{org.apache.fop.fonts.FontDetectorFactory}}:
> {code}
> URI fontBaseURI =
> fontManager.getResourceResolver().getBaseURI();
> File fontBase = FileUtils.toFile(fontBaseURI.toURL());
> {code}
> In particular the {{fontBaseURI.toURL()}} generates a
> {{MalformedURLException}}. The URL is actually perfectly valid, it is just
> that Java does not have a handler for it.
> The attached patch, simply wraps that in a {{try/catch}} and logs the
> exception as a warning, as this seems to be a non-critical path, after which
> system fonts can still be correctly be detected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FOP-2757) [PATCH] page-height="indefinite"
[ https://issues.apache.org/jira/browse/FOP-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251091#comment-16251091 ] Glenn Adams commented on FOP-2757: -- Note that you will have to have a ICLA on file for this to be used in FOP. See more info at https://www.apache.org/licenses/icla.pdf. > [PATCH] page-height="indefinite" > > > Key: FOP-2757 > URL: https://issues.apache.org/jira/browse/FOP-2757 > Project: FOP > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Axel Rose > Attachments: page-indefinite.patch > > > Hello team, > I'd love to contribute the attached code which works already locally > implementing page-height="indefinite" (http://www.w3.org/TR/xsl/#page-height) > Happy to take further questions on this. > Regards, > Axel. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FOP-2726) FOP 0.93 version has issue with image on tomcat server running with OpenJDK
[ https://issues.apache.org/jira/browse/FOP-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2726. > FOP 0.93 version has issue with image on tomcat server running with OpenJDK > --- > > Key: FOP-2726 > URL: https://issues.apache.org/jira/browse/FOP-2726 > Project: FOP > Issue Type: Bug > Components: image/png > Environment: Tomcat running with OpenJDK1.7 >Reporter: vijay shankar >Priority: Blocker > Attachments: ErrorLog.log > > > We have a web-application and are using FOP-0.93 to generate a pdf. We have > given path of a logo image in the template file as below. > content-height="125pt"/>. > When we are deploying war on local machine's tomcat(using jdk1.7), pdf is > being generated successfully with logo. But when same war file has deployed > on tomcat server(OpenJDK), getting NullPointerException. find the attached > log for more information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2728) Persian (Farsi) output problem with FOP
[ https://issues.apache.org/jira/browse/FOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089192#comment-16089192 ] Glenn Adams commented on FOP-2728: -- Yes, it (handling of language and script attributes) are known bugs: https://issues.apache.org/jira/browse/FOP-2093 https://issues.apache.org/jira/browse/FOP-2094 > Persian (Farsi) output problem with FOP > --- > > Key: FOP-2728 > URL: https://issues.apache.org/jira/browse/FOP-2728 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Ubuntu 16.04 with xmlto 0.0.28 >Reporter: Navid Emami > Labels: drupal > Attachments: mkebooks.sh, pdf-farsi.xsl, sample-output-final.zip, > sample-output.zip, simple.fo, simple-nolang.pdf, simple.pdf > > > We are having trouble making Persian (Farsi) language output with FOP. > We are using the *xmlto* script with the --with-fop option to convert a > DocBook file to PDF using FOP, which uses XSLT to first make a FO file, and > then FOP to convert to PDF. We used the --noclean option to capture the > intermediate FO XML file. > We have verified that the Persian (Farsi) characters are readable in the > DocBook and FO files. However, when we generate the PDF, the output is not > readable. There are both _joined_ and _separated_ letters in Persian (Farsi) > language but the output in PDF format has just separated ones. > Note that there are some font issues in the PDF output as well -- missing > glyphs -- those show as # characters, and are in the chapter/section > headings. However, the main body of the text has no # characters, and it > still has this problem. > *Attachments:* > * sample-output.zip contains small.docbook, small.fo, small.epub and > small.pdf. The final output of PDF should be similar to EPUB. > * sample-output-full.zip contains guide.epub and guide.pdf which are the > complete documents but with wrong rendering of characters in PDF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2728) Persian (Farsi) output problem with FOP
[ https://issues.apache.org/jira/browse/FOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089139#comment-16089139 ] Glenn Adams commented on FOP-2728: -- Try removing the language tag (entirely) and see what happens. Don't even bother trying to use sans-serif (or any other non-Arabic or Farsi font), as that won't work (though perhaps "MS Sans Unicode" might work). > Persian (Farsi) output problem with FOP > --- > > Key: FOP-2728 > URL: https://issues.apache.org/jira/browse/FOP-2728 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Ubuntu 16.04 with xmlto 0.0.28 >Reporter: Navid Emami > Labels: drupal > Attachments: mkebooks.sh, pdf-farsi.xsl, sample-output-final.zip, > sample-output.zip, simple.fo, simple.pdf > > > We are having trouble making Persian (Farsi) language output with FOP. > We are using the *xmlto* script with the --with-fop option to convert a > DocBook file to PDF using FOP, which uses XSLT to first make a FO file, and > then FOP to convert to PDF. We used the --noclean option to capture the > intermediate FO XML file. > We have verified that the Persian (Farsi) characters are readable in the > DocBook and FO files. However, when we generate the PDF, the output is not > readable. There are both _joined_ and _separated_ letters in Persian (Farsi) > language but the output in PDF format has just separated ones. > Note that there are some font issues in the PDF output as well -- missing > glyphs -- those show as # characters, and are in the chapter/section > headings. However, the main body of the text has no # characters, and it > still has this problem. > *Attachments:* > * sample-output.zip contains small.docbook, small.fo, small.epub and > small.pdf. The final output of PDF should be similar to EPUB. > * sample-output-full.zip contains guide.epub and guide.pdf which are the > complete documents but with wrong rendering of characters in PDF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2728) Persian (Farsi) output problem with FOP
[ https://issues.apache.org/jira/browse/FOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089037#comment-16089037 ] Glenn Adams commented on FOP-2728: -- The reason I suggest a really simple FO input file for testing presentation is because that is the real input of FOP. All XSLT processing is just noise that makes it difficult to test and understand the formatting semantics of FOP processing. I haven't tested any Farsi fonts. You might try the Arabic fonts mentioned in the link I provided above. > Persian (Farsi) output problem with FOP > --- > > Key: FOP-2728 > URL: https://issues.apache.org/jira/browse/FOP-2728 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Ubuntu 16.04 with xmlto 0.0.28 >Reporter: Navid Emami > Labels: drupal > Attachments: mkebooks.sh, pdf-farsi.xsl, sample-output-final.zip, > sample-output.zip > > > We are having trouble making Persian (Farsi) language output with FOP. > We are using the *xmlto* script with the --with-fop option to convert a > DocBook file to PDF using FOP, which uses XSLT to first make a FO file, and > then FOP to convert to PDF. We used the --noclean option to capture the > intermediate FO XML file. > We have verified that the Persian (Farsi) characters are readable in the > DocBook and FO files. However, when we generate the PDF, the output is not > readable. There are both _joined_ and _separated_ letters in Persian (Farsi) > language but the output in PDF format has just separated ones. > Note that there are some font issues in the PDF output as well -- missing > glyphs -- those show as # characters, and are in the chapter/section > headings. However, the main body of the text has no # characters, and it > still has this problem. > *Attachments:* > * sample-output.zip contains small.docbook, small.fo, small.epub and > small.pdf. The final output of PDF should be similar to EPUB. > * sample-output-full.zip contains guide.epub and guide.pdf which are the > complete documents but with wrong rendering of characters in PDF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2728) Persian (Farsi) output problem with FOP
[ https://issues.apache.org/jira/browse/FOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089015#comment-16089015 ] Glenn Adams commented on FOP-2728: -- You should focus on creating a (MUCH simpler) version of simple.fo and use that as input to FOP for testing purposes so you can bypass all docbook pre-processing via XSLT. Make sure you specify writing-mode="rl" or "rl-tb" on fo:page-sequence, not fo:root. Regarding font support, you have it backwards. The primary support is for OpenType, and only OT tables are supported for complex script processing. > Persian (Farsi) output problem with FOP > --- > > Key: FOP-2728 > URL: https://issues.apache.org/jira/browse/FOP-2728 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Ubuntu 16.04 with xmlto 0.0.28 >Reporter: Navid Emami > Labels: drupal > Attachments: mkebooks.sh, pdf-farsi.xsl, sample-output-final.zip, > sample-output.zip > > > We are having trouble making Persian (Farsi) language output with FOP. > We are using the *xmlto* script with the --with-fop option to convert a > DocBook file to PDF using FOP, which uses XSLT to first make a FO file, and > then FOP to convert to PDF. We used the --noclean option to capture the > intermediate FO XML file. > We have verified that the Persian (Farsi) characters are readable in the > DocBook and FO files. However, when we generate the PDF, the output is not > readable. There are both _joined_ and _separated_ letters in Persian (Farsi) > language but the output in PDF format has just separated ones. > Note that there are some font issues in the PDF output as well -- missing > glyphs -- those show as # characters, and are in the chapter/section > headings. However, the main body of the text has no # characters, and it > still has this problem. > *Attachments:* > * sample-output.zip contains small.docbook, small.fo, small.epub and > small.pdf. The final output of PDF should be similar to EPUB. > * sample-output-full.zip contains guide.epub and guide.pdf which are the > complete documents but with wrong rendering of characters in PDF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FOP-2728) Persian (Farsi) output problem with FOP
[ https://issues.apache.org/jira/browse/FOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088846#comment-16088846 ] Glenn Adams commented on FOP-2728: -- Try removing the language="fa" attribute (in order to have the font engine use default font tables). If that doesn't work, then it may be due to your use of an untested font "FreeFarsi". See [1] for list of tested fonts. N.B. that I have done no testing on Farsi targeted fonts to date; only Arabic. [1] https://xmlgraphics.apache.org/fop/2.1/complexscripts.html#supported_fonts > Persian (Farsi) output problem with FOP > --- > > Key: FOP-2728 > URL: https://issues.apache.org/jira/browse/FOP-2728 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Ubuntu 16.04 with xmlto 0.0.28 >Reporter: Navid Emami > Labels: drupal > Attachments: sample-output-final.zip, sample-output.zip > > > We are having trouble making Persian (Farsi) language output with FOP. > We are using the *xmlto* script with the --with-fop option to convert a > DocBook file to PDF using FOP, which uses XSLT to first make a FO file, and > then FOP to convert to PDF. We used the --noclean option to capture the > intermediate FO XML file. > We have verified that the Persian (Farsi) characters are readable in the > DocBook and FO files. However, when we generate the PDF, the output is not > readable. There are both _joined_ and _separated_ letters in Persian (Farsi) > language but the output in PDF format has just separated ones. > Note that there are some font issues in the PDF output as well -- missing > glyphs -- those show as # characters, and are in the chapter/section > headings. However, the main body of the text has no # characters, and it > still has this problem. > *Attachments:* > * sample-output.zip contains small.docbook, small.fo, small.epub and > small.pdf. The final output of PDF should be similar to EPUB. > * sample-output-full.zip contains guide.epub and guide.pdf which are the > complete documents but with wrong rendering of characters in PDF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FOP-2726) FOP 0.93 version has issue with image on tomcat server running with OpenJDK
[ https://issues.apache.org/jira/browse/FOP-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams closed FOP-2726. > FOP 0.93 version has issue with image on tomcat server running with OpenJDK > --- > > Key: FOP-2726 > URL: https://issues.apache.org/jira/browse/FOP-2726 > Project: FOP > Issue Type: Bug > Components: image/png > Environment: Tomcat running with OpenJDK1.7 >Reporter: vijay shankar >Priority: Blocker > Attachments: ErrorLog.log > > > We have a web-application and are using FOP-0.93 to generate a pdf. We have > given path of a logo image in the template file as below. > content-height="125pt"/>. > When we are deploying war on local machine's tomcat(using jdk1.7), pdf is > being generated successfully with logo. But when same war file has deployed > on tomcat server(OpenJDK), getting NullPointerException. find the attached > log for more information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
