[jira] [Resolved] (FOP-3073) PDF to PDF may not print
[ https://issues.apache.org/jira/browse/FOP-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3073. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1900953 > PDF to PDF may not print > > > Key: FOP-3073 > URL: https://issues.apache.org/jira/browse/FOP-3073 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo out.pdf > Open PDF in Adobe Acrobat and run preflight syntax check, no errors should be > reported -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3073) PDF to PDF may not print
[ https://issues.apache.org/jira/browse/FOP-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3073: --- Description: fop test.fo out.pdf Open PDF in Adobe Acrobat and run preflight syntax check, no errors should be reported > PDF to PDF may not print > > > Key: FOP-3073 > URL: https://issues.apache.org/jira/browse/FOP-3073 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > Open PDF in Adobe Acrobat and run preflight syntax check, no errors should be > reported -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3073) PDF to PDF may not print
[ https://issues.apache.org/jira/browse/FOP-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3073: --- Attachment: test.fo > PDF to PDF may not print > > > Key: FOP-3073 > URL: https://issues.apache.org/jira/browse/FOP-3073 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > Open PDF in Adobe Acrobat and run preflight syntax check, no errors should be > reported -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (FOP-3073) PDF to PDF may not print
Simon Steiner created FOP-3073: -- Summary: PDF to PDF may not print Key: FOP-3073 URL: https://issues.apache.org/jira/browse/FOP-3073 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (FOP-3072) Empty link url gives NPE
[ https://issues.apache.org/jira/browse/FOP-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3072. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1900951 > Empty link url gives NPE > > > Key: FOP-3072 > URL: https://issues.apache.org/jira/browse/FOP-3072 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: simple.fo > > > fop simple.fo out.pdf > Gives java.lang.NullPointerException > at > org.apache.fop.render.intermediate.IFRenderer.renderInlineParent(IFRenderer.java:983) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3072) Empty link url gives NPE
[ https://issues.apache.org/jira/browse/FOP-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3072: --- Description: fop simple.fo out.pdf Gives java.lang.NullPointerException at org.apache.fop.render.intermediate.IFRenderer.renderInlineParent(IFRenderer.java:983) > Empty link url gives NPE > > > Key: FOP-3072 > URL: https://issues.apache.org/jira/browse/FOP-3072 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop simple.fo out.pdf > Gives java.lang.NullPointerException > at > org.apache.fop.render.intermediate.IFRenderer.renderInlineParent(IFRenderer.java:983) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3072) Empty link url gives NPE
[ https://issues.apache.org/jira/browse/FOP-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3072: --- Attachment: simple.fo > Empty link url gives NPE > > > Key: FOP-3072 > URL: https://issues.apache.org/jira/browse/FOP-3072 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (FOP-3072) Empty link url gives NPE
Simon Steiner created FOP-3072: -- Summary: Empty link url gives NPE Key: FOP-3072 URL: https://issues.apache.org/jira/browse/FOP-3072 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: simple.fo -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (FOP-3071) AFP mediummap in wrong place when added before page-group
[ https://issues.apache.org/jira/browse/FOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3071. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1900949 > AFP mediummap in wrong place when added before page-group > - > > Key: FOP-3071 > URL: https://issues.apache.org/jira/browse/FOP-3071 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo -afp out.afp > Open AFP in AFPLookup and you should see in this order: > IMM > Page 1 > Page 2 > Named Group -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3071) AFP mediummap in wrong place when added before page-group
[ https://issues.apache.org/jira/browse/FOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3071: --- Attachment: test.fo > AFP mediummap in wrong place when added before page-group > - > > Key: FOP-3071 > URL: https://issues.apache.org/jira/browse/FOP-3071 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo -afp out.afp > Open AFP in AFPLookup and you should see in this order: > IMM > Page 1 > Page 2 > Named Group -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FOP-3071) AFP mediummap in wrong place when added before page-group
[ https://issues.apache.org/jira/browse/FOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3071: --- Description: fop test.fo -afp out.afp Open AFP in AFPLookup and you should see in this order: IMM Page 1 Page 2 Named Group > AFP mediummap in wrong place when added before page-group > - > > Key: FOP-3071 > URL: https://issues.apache.org/jira/browse/FOP-3071 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo -afp out.afp > Open AFP in AFPLookup and you should see in this order: > IMM > Page 1 > Page 2 > Named Group -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (FOP-3071) AFP mediummap in wrong place when added before page-group
Simon Steiner created FOP-3071: -- Summary: AFP mediummap in wrong place when added before page-group Key: FOP-3071 URL: https://issues.apache.org/jira/browse/FOP-3071 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FOP-3069) Empty results in infinite loop when strict-validation is set to false
[
https://issues.apache.org/jira/browse/FOP-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537461#comment-17537461
]
Michael Kainzbauer commented on FOP-3069:
-
I know the xml FO is incorrect and how to get it rendered correctly. But this
doesn't solve the issue. The issue is: no input should cause the program to
loop forever, regardless if the input is well formed, or not. If the input
can't be rendered, it should terminate throwing an exception. It must not run
infinitely!
> Empty results in infinite loop when strict-validation is set
> to false
> -
>
> Key: FOP-3069
> URL: https://issues.apache.org/jira/browse/FOP-3069
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 1.1, 2.0, 2.1, 2.2, 2.3, 2.4, 2.6, 2.7
>Reporter: Michael Kainzbauer
>Priority: Major
>
> +_Since Apache FOP 1.1 (not reproducible in 1.0)_+
> When disabling strict-validation, ApacheFOP will loop infinitely when a
> is empty, e.g.:
> As a result in class
> {color:#57d9a3}org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(LayoutContext
> context, int alignment);{color}
> (line 111)
> is called infinitely.
> Yes, the XML-FO is incorrect and not according to the standard, but this is
> an issue that can cause real trouble when the given conditions are met.
> Turning on strict-validation will result in an error with a clear and
> understandable error message:
> {quote}{color:#57d9a3}{{Error on line 26 column 29 }}{color}
> {color:#57d9a3}{{ SXCH0003 org.apache.fop.fo.ValidationException:
> "fo:table-body" is missing child}}{color}
> {color:#57d9a3}{{ elements. Required content model: marker*
> (table-row+|table-cell+) (Siehe Position 26:29).}}{color}
> {color:#57d9a3}{{ Caused by org.apache.fop.fo.ValidationException:
> null:26:29: "fo:table-body" is missing}}{color}
> {color:#57d9a3}{{ child elements. Required content model: marker*
> (table-row+|table-cell+) (See position 26:29)}}{color}
> {quote}
> Example XML-FO:
> {quote}{{{color:#57d9a3}{color}}}
> {{{color:#57d9a3} xmlns:fo="http://www.w3.org/1999/XSL/Format;>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} page-width="210mm" page-height="297mm">{color}}}
> {{{color:#57d9a3} margin-right="5mm" margin-top="10mm"/>{color}}}
> {{{color:#57d9a3} region-name="main-reg-before"/>{color}}}
> {{{color:#57d9a3} region-name="main-reg-after"/>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} master-reference="A4-main" page-position="any"/>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3}{color}}}
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (FOP-3069) Empty results in infinite loop when strict-validation is set to false
[
https://issues.apache.org/jira/browse/FOP-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537458#comment-17537458
]
J Frank commented on FOP-3069:
--
I would suggest, try adding an empty block to the table, instead of having
empty standalone table.
> Empty results in infinite loop when strict-validation is set
> to false
> -
>
> Key: FOP-3069
> URL: https://issues.apache.org/jira/browse/FOP-3069
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 1.1, 2.0, 2.1, 2.2, 2.3, 2.4, 2.6, 2.7
>Reporter: Michael Kainzbauer
>Priority: Major
>
> +_Since Apache FOP 1.1 (not reproducible in 1.0)_+
> When disabling strict-validation, ApacheFOP will loop infinitely when a
> is empty, e.g.:
> As a result in class
> {color:#57d9a3}org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(LayoutContext
> context, int alignment);{color}
> (line 111)
> is called infinitely.
> Yes, the XML-FO is incorrect and not according to the standard, but this is
> an issue that can cause real trouble when the given conditions are met.
> Turning on strict-validation will result in an error with a clear and
> understandable error message:
> {quote}{color:#57d9a3}{{Error on line 26 column 29 }}{color}
> {color:#57d9a3}{{ SXCH0003 org.apache.fop.fo.ValidationException:
> "fo:table-body" is missing child}}{color}
> {color:#57d9a3}{{ elements. Required content model: marker*
> (table-row+|table-cell+) (Siehe Position 26:29).}}{color}
> {color:#57d9a3}{{ Caused by org.apache.fop.fo.ValidationException:
> null:26:29: "fo:table-body" is missing}}{color}
> {color:#57d9a3}{{ child elements. Required content model: marker*
> (table-row+|table-cell+) (See position 26:29)}}{color}
> {quote}
> Example XML-FO:
> {quote}{{{color:#57d9a3}{color}}}
> {{{color:#57d9a3} xmlns:fo="http://www.w3.org/1999/XSL/Format;>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} page-width="210mm" page-height="297mm">{color}}}
> {{{color:#57d9a3} margin-right="5mm" margin-top="10mm"/>{color}}}
> {{{color:#57d9a3} region-name="main-reg-before"/>{color}}}
> {{{color:#57d9a3} region-name="main-reg-after"/>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} master-reference="A4-main" page-position="any"/>{color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3} {color}}}
> {{{color:#57d9a3}{color}}}
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (FOP-3069) Empty results in infinite loop when strict-validation is set to false
[
https://issues.apache.org/jira/browse/FOP-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Kainzbauer updated FOP-3069:
Description:
+_Since Apache FOP 1.1 (not reproducible in 1.0)_+
When disabling strict-validation, ApacheFOP will loop infinitely when a
is empty, e.g.:
As a result in class
{color:#57d9a3}org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(LayoutContext
context, int alignment);{color}
(line 111)
is called infinitely.
Yes, the XML-FO is incorrect and not according to the standard, but this is an
issue that can cause real trouble when the given conditions are met. Turning on
strict-validation will result in an error with a clear and understandable error
message:
{quote}{color:#57d9a3}{{Error on line 26 column 29 }}{color}
{color:#57d9a3}{{ SXCH0003 org.apache.fop.fo.ValidationException:
"fo:table-body" is missing child}}{color}
{color:#57d9a3}{{ elements. Required content model: marker*
(table-row+|table-cell+) (Siehe Position 26:29).}}{color}
{color:#57d9a3}{{ Caused by org.apache.fop.fo.ValidationException: null:26:29:
"fo:table-body" is missing}}{color}
{color:#57d9a3}{{ child elements. Required content model: marker*
(table-row+|table-cell+) (See position 26:29)}}{color}
{quote}
Example XML-FO:
{quote}{{{color:#57d9a3}{color}}}
{{{color:#57d9a3}http://www.w3.org/1999/XSL/Format;>{color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3}{color}}}
{quote}
was:
+_Since Apache FOP 1.1 (not reproducible in 1.0)_+
When disabling strict-validation, ApacheFOP will loop infinitely when a
is empty, e.g.:
As a result in class
{color:#57d9a3}{\{
org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(LayoutContext
context, int alignment)}}{color}
(line 111)
is called infinitely.
Yes, the XML-FO is incorrect and not according to the standard, but this is an
issue that can cause real trouble when the given conditions are met. Turning on
strict-validation will result in an error with a clear and understandable error
message:
{quote}{color:#57d9a3}{{Error on line 26 column 29 }}{color}
{color:#57d9a3}{{ SXCH0003 org.apache.fop.fo.ValidationException:
"fo:table-body" is missing child}}{color}
{color:#57d9a3}{{ elements. Required content model: marker*
(table-row+|table-cell+) (Siehe Position 26:29).}}{color}
{color:#57d9a3}{{ Caused by org.apache.fop.fo.ValidationException: null:26:29:
"fo:table-body" is missing}}{color}
{color:#57d9a3}{{ child elements. Required content model: marker*
(table-row+|table-cell+) (See position 26:29)}}{color}
{quote}
Example XML-FO:
{quote}{{{color:#57d9a3}{color}}}
{{{color:#57d9a3}http://www.w3.org/1999/XSL/Format;>{color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3} {color}}}
{{{color:#57d9a3}{color}}}{quote}
> Empty results in infinite loop when strict-validation is set
> to false
> -
>
> Key: FOP-3069
> URL: https://issues.apache.org/jira/browse/FOP-3069
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 1.1, 2.0, 2.1, 2.2, 2.3, 2.4, 2.6, 2.7
>Reporter: Michael Kainzbauer
>Priority: Major
>
> +_Since Apache FOP 1.1 (not reproducible in 1.0)_+
> When disabling strict-validation, ApacheFOP will loop infinitely when a
> is empty, e.g.:
> As a result in class
>
