[jira] [Commented] (FOP-2469) [PATCH] Auto table layout
[ https://issues.apache.org/jira/browse/FOP-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150100#comment-17150100 ] Mathieu Malaterre commented on FOP-2469: [~esclim] any progress ? Thanks > [PATCH] Auto table layout > - > > Key: FOP-2469 > URL: https://issues.apache.org/jira/browse/FOP-2469 > Project: FOP > Issue Type: Bug > Components: layout/unqualified >Affects Versions: 2.5 > Environment: Windows 7, JDK 7 >Reporter: Gregor Berg >Assignee: Andreas L. Delmelle >Priority: Major > Attachments: 2015-05-13-auto-table-layout.patch, > 2015-05-27-LM-to-LC-refactoring.patch, > 2015-06-09-LM-to-LC-refactoring-update.patch, FOP-2469-2018-07-17.patch, > FOP-2469_20150621.patch, FOP2469-auto-table-layout.xml, > resize-all-but-static-spanned-columns.xml, resize-spanned-columns.xml, > test.fo, test2.fo, warning-only-static-columns-are-spanned.xml > > > Hi, > this is a patch which enables table-layout=auto. It is quite robust, it can > not only handle linebreaks and pagebreaks, but it also copes with auto tables > in fixed tables in auto tables. > Essentially, it is the patch of issue FOP-2450 adapted to the trunk version > of FOP. > Best regards, > Gregor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FOP-1196) [PATCH] GSoC: floats implementation
[
https://issues.apache.org/jira/browse/FOP-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054978#comment-17054978
]
Mathieu Malaterre commented on FOP-1196:
It seems I can no longer reproduce the bug using fop 2.4.
> [PATCH] GSoC: floats implementation
> ---
>
> Key: FOP-1196
> URL: https://issues.apache.org/jira/browse/FOP-1196
> Project: FOP
> Issue Type: Improvement
> Components: layout/unqualified
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: Vincent Hennebert
>Priority: Major
> Labels: PatchAvailable
> Attachments: patch.diff, patch2.diff, patchBeforeFloats-2.diff,
> patchBeforeFloats.diff, patchDisabledTestcases.diff, patchTestcases.diff
>
>
> This patch isn't really meant to be applied... Rather to be reviewed by
> interested parties to check if I'm not wrong. Changelog:
> * javadocs for the Knuth line- and page-breaking algorithms. Some items are
> marked with double question marks because I haven't found out yet what is
> their
> purpose. I will probably find eventually, but if anybody has immediate hints
> they will be welcome.
> * some methods have been marked deprecated because AFAICT they are not called
> anywhere. If this is agreed I'll remove them in my next patch
> * bugfix? In the last for loop of the method
> layoutmgr.PageBreakingAlgorithm.noBreakBetween I think the exit condition
> should
> be a strict comparison ('<' instead of '<='). Confirmation?
> * the javadoc comments for some methods have been removed because they will
> inherit them from their super-class
> * some checkstyle fixes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FOP-1776) NPE caused by nested empty fo:inline with id
[ https://issues.apache.org/jira/browse/FOP-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053190#comment-17053190 ] Mathieu Malaterre commented on FOP-1776: The famous https://issues.apache.org/bugzilla/show_bug.cgi?id=42748 > NPE caused by nested empty fo:inline with id > > > Key: FOP-1776 > URL: https://issues.apache.org/jira/browse/FOP-1776 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Mathieu Malaterre >Priority: Major > Attachments: _test.fo, anchor.id.patch, fop1776.patch, test2.fo > > > Here is my input docbook file: > > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; []> > > > title > > > The id="example.anchor.1"/>anchor element is empty and > contributes > nothing to the flow of the content in which it occurs. It is only useful > as a target. > > > > > which I process with: > /usr/bin/xsltproc --stringparam fop1.extensions 1 --stringparam > ulink.show 0 --xinclude -o test2.fo > /usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl test2.xml > and lead to: > $ ./fop test2.fo test2.pdf > Feb 17, 2010 2:52:18 PM org.apache.fop.apps.FOURIResolver resolve > SEVERE: Error with opening URL > 'http://docbook.sourceforge.net/release/images/draft.png': Network is > unreachable > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:9588) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10285) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10980) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:11672) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:12361) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13050) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13736) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:14427) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15118) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15806) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:16496) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17186) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17873) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:18563) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19253) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19940) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:20631) > Feb 17, 2010 2:52:18
[jira] [Commented] (FOP-2916) Error: Could not find or load main class org.apache.fop.hyphenation.SerializeHyphPattern
[
https://issues.apache.org/jira/browse/FOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052135#comment-17052135
]
Mathieu Malaterre commented on FOP-2916:
OK, found the issue:
{code}
$ grep -A 2 libs-build-classpath fop/build.xml | head -3
{code}
At least during building of Debian package, the jar files et generated in
'target' directory.
> Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
>
>
> Key: FOP-2916
> URL: https://issues.apache.org/jira/browse/FOP-2916
> Project: FOP
> Issue Type: Bug
>Reporter: Mathieu Malaterre
>Priority: Major
>
> This is getting more and more complex to build fop-hyph.
> Here is the compilation log:
> {code}
> mkdir -p fop/lib/build
> # While the README mention those are deprecated build instructions it
> # seems those targets have not been moved to the new maven build system
> ant -f fop/build.xml -lib
> /usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
> jar-hyphenation
> Buildfile:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
> Trying to override old definition of task javac
> Trying to override old definition of task junit
> compile-hyphenation:
> [mkdir] Created dir:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
> [java] Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Caused by: java.lang.ClassNotFoundException:
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Java Result: 1
> [echo] Hyphenation failed
> uptodate-jar-hyphenation:
> jar-hyphenation:
> [jar] Building MANIFEST-only jar:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
> BUILD SUCCESSFUL
> Total time: 0 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (FOP-2916) Error: Could not find or load main class org.apache.fop.hyphenation.SerializeHyphPattern
[
https://issues.apache.org/jira/browse/FOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu Malaterre closed FOP-2916.
--
Resolution: Not A Problem
It is easy to copy from one output dir to the other.
> Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
>
>
> Key: FOP-2916
> URL: https://issues.apache.org/jira/browse/FOP-2916
> Project: FOP
> Issue Type: Bug
>Reporter: Mathieu Malaterre
>Priority: Major
>
> This is getting more and more complex to build fop-hyph.
> Here is the compilation log:
> {code}
> mkdir -p fop/lib/build
> # While the README mention those are deprecated build instructions it
> # seems those targets have not been moved to the new maven build system
> ant -f fop/build.xml -lib
> /usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
> jar-hyphenation
> Buildfile:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
> Trying to override old definition of task javac
> Trying to override old definition of task junit
> compile-hyphenation:
> [mkdir] Created dir:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
> [java] Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Caused by: java.lang.ClassNotFoundException:
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Java Result: 1
> [echo] Hyphenation failed
> uptodate-jar-hyphenation:
> jar-hyphenation:
> [jar] Building MANIFEST-only jar:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
> BUILD SUCCESSFUL
> Total time: 0 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FOP-2916) Error: Could not find or load main class org.apache.fop.hyphenation.SerializeHyphPattern
[
https://issues.apache.org/jira/browse/FOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu Malaterre updated FOP-2916:
---
Description:
This is getting more and more complex to build fop-hyph.
Here is the compilation log:
{code}
mkdir -p fop/lib/build
# While the README mention those are deprecated build instructions it
# seems those targets have not been moved to the new maven build system
ant -f fop/build.xml -lib
/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
jar-hyphenation
Buildfile:
/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
Trying to override old definition of task javac
Trying to override old definition of task junit
compile-hyphenation:
[mkdir] Created dir:
/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
[java] Error: Could not find or load main class
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Caused by: java.lang.ClassNotFoundException:
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Java Result: 1
[echo] Hyphenation failed
uptodate-jar-hyphenation:
jar-hyphenation:
[jar] Building MANIFEST-only jar:
/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
BUILD SUCCESSFUL
Total time: 0 seconds
{code}
was:
This is getting more and more complex to build fop-hyph.
Here is the compilation log:
{code}
mkdir -p fop/lib/build
# While the README mention those are deprecated build instructions it
# seems those targets have not been moved to the new maven build system
ant -f fop/build.xml -lib
/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
jar-hyphenation
Buildfile:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
Trying to override old definition of task javac
Trying to override old definition of task junit
compile-hyphenation:
[mkdir] Created dir:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
[java] Error: Could not find or load main class
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Caused by: java.lang.ClassNotFoundException:
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Java Result: 1
[echo] Hyphenation failed
uptodate-jar-hyphenation:
jar-hyphenation:
[jar] Building MANIFEST-only jar:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
BUILD SUCCESSFUL
Total time: 0 seconds
{code}
> Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
>
>
> Key: FOP-2916
> URL: https://issues.apache.org/jira/browse/FOP-2916
> Project: FOP
> Issue Type: Bug
>Reporter: Mathieu Malaterre
>Priority: Major
>
> This is getting more and more complex to build fop-hyph.
> Here is the compilation log:
> {code}
> mkdir -p fop/lib/build
> # While the README mention those are deprecated build instructions it
> # seems those targets have not been moved to the new maven build system
> ant -f fop/build.xml -lib
> /usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
> jar-hyphenation
> Buildfile:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
> Trying to override old definition of task javac
> Trying to override old definition of task junit
> compile-hyphenation:
> [mkdir] Created dir:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
> [java] Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Caused by: java.lang.ClassNotFoundException:
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Java Result: 1
> [echo] Hyphenation failed
> uptodate-jar-hyphenation:
> jar-hyphenation:
> [jar] Building MANIFEST-only jar:
> /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
> BUILD SUCCESSFUL
> Total time: 0 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FOP-2916) Error: Could not find or load main class org.apache.fop.hyphenation.SerializeHyphPattern
[
https://issues.apache.org/jira/browse/FOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052113#comment-17052113
]
Mathieu Malaterre commented on FOP-2916:
The error message does not make any sense to me since:
{code}
$ jar xvf /usr/share/java/fop.jar | grep SerializeHyphPattern
inflated: org/apache/fop/hyphenation/SerializeHyphPattern$1.class
inflated: org/apache/fop/hyphenation/SerializeHyphPattern.class
{code}
> Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
>
>
> Key: FOP-2916
> URL: https://issues.apache.org/jira/browse/FOP-2916
> Project: FOP
> Issue Type: Bug
>Reporter: Mathieu Malaterre
>Priority: Major
>
> This is getting more and more complex to build fop-hyph.
> Here is the compilation log:
> {code}
> mkdir -p fop/lib/build
> # While the README mention those are deprecated build instructions it
> # seems those targets have not been moved to the new maven build system
> ant -f fop/build.xml -lib
> /usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
> jar-hyphenation
> Buildfile:
> /mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
> Trying to override old definition of task javac
> Trying to override old definition of task junit
> compile-hyphenation:
> [mkdir] Created dir:
> /mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
> [java] Error: Could not find or load main class
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Caused by: java.lang.ClassNotFoundException:
> org.apache.fop.hyphenation.SerializeHyphPattern
> [java] Java Result: 1
> [echo] Hyphenation failed
> uptodate-jar-hyphenation:
> jar-hyphenation:
> [jar] Building MANIFEST-only jar:
> /mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
> BUILD SUCCESSFUL
> Total time: 0 seconds
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FOP-2916) Error: Could not find or load main class org.apache.fop.hyphenation.SerializeHyphPattern
Mathieu Malaterre created FOP-2916:
--
Summary: Error: Could not find or load main class
org.apache.fop.hyphenation.SerializeHyphPattern
Key: FOP-2916
URL: https://issues.apache.org/jira/browse/FOP-2916
Project: FOP
Issue Type: Bug
Reporter: Mathieu Malaterre
This is getting more and more complex to build fop-hyph.
Here is the compilation log:
{code}
mkdir -p fop/lib/build
# While the README mention those are deprecated build instructions it
# seems those targets have not been moved to the new maven build system
ant -f fop/build.xml -lib
/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/batik-libs.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/fontbox2.jar:/usr/share/java/servlet-api-3.1.jar:/usr/share/java/fop.jar
jar-hyphenation
Buildfile:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build.xml
Trying to override old definition of task javac
Trying to override old definition of task junit
compile-hyphenation:
[mkdir] Created dir:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/classes/hyph
[java] Error: Could not find or load main class
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Caused by: java.lang.ClassNotFoundException:
org.apache.fop.hyphenation.SerializeHyphPattern
[java] Java Result: 1
[echo] Hyphenation failed
uptodate-jar-hyphenation:
jar-hyphenation:
[jar] Building MANIFEST-only jar:
/mnt/bdc64c37-340a-49e5-8184-a69e01e5e231/mathieu/debian/fop/fop/build/fop-hyph.jar
BUILD SUCCESSFUL
Total time: 0 seconds
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (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=17052100#comment-17052100
]
Mathieu Malaterre edited comment on FOP-2733 at 3/5/20, 12:51 PM:
--
Could someone please confirm this is fixed in 2.4.
Here is what I see on my side:
{code}
$ grep -r avalon-framework
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ basictests.xml
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ bugtests.xml
fop/examples/hyphenation/analyse.cmd:set
LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-4.2.0.jar
{code}
was (Author: malaterre):
Could someone please confirm this is fixed in 2.4.
Here is what I see on my side:
{{$ grep -r avalon-framework
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ basictests.xml
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ bugtests.xml
fop/examples/hyphenation/analyse.cmd:set
LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-4.2.0.jar}}
> [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
>Assignee: Simon Steiner
>Priority: Major
> Attachments: barcode.pdf, 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
(v8.3.4#803005)
[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=17052100#comment-17052100
]
Mathieu Malaterre commented on FOP-2733:
Could someone please confirm this is fixed in 2.4.
Here is what I see on my side:
{{$ grep -r avalon-framework
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ basictests.xml
fop/test/createpdf.sh:$JAVA_HOME/bin/java -cp
../build/fop.jar:../lib/batik.jar:../lib/xalan-2.0.0.jar:../lib/xerces-1.2.3.jar:../lib/avalon-framework-4.0.jar:../lib/logkit-1.0b4.jar:../lib/jimi-1.0.jar
org.apache.fop.tools.TestConverter -pdf -b ./ bugtests.xml
fop/examples/hyphenation/analyse.cmd:set
LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-4.2.0.jar}}
> [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
>Assignee: Simon Steiner
>Priority: Major
> Attachments: barcode.pdf, 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
(v8.3.4#803005)
[jira] [Updated] (FOP-1776) NPE caused by nested empty fo:inline with id
[ https://issues.apache.org/jira/browse/FOP-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathieu Malaterre updated FOP-1776: --- Attachment: fop1776.patch > NPE caused by nested empty fo:inline with id > > > Key: FOP-1776 > URL: https://issues.apache.org/jira/browse/FOP-1776 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Mathieu Malaterre >Priority: Major > Attachments: _test.fo, anchor.id.patch, fop1776.patch, test2.fo > > > Here is my input docbook file: > > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; []> > > > title > > > The id="example.anchor.1"/>anchor element is empty and > contributes > nothing to the flow of the content in which it occurs. It is only useful > as a target. > > > > > which I process with: > /usr/bin/xsltproc --stringparam fop1.extensions 1 --stringparam > ulink.show 0 --xinclude -o test2.fo > /usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl test2.xml > and lead to: > $ ./fop test2.fo test2.pdf > Feb 17, 2010 2:52:18 PM org.apache.fop.apps.FOURIResolver resolve > SEVERE: Error with opening URL > 'http://docbook.sourceforge.net/release/images/draft.png': Network is > unreachable > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:9588) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10285) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10980) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:11672) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:12361) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13050) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13736) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:14427) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15118) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15806) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:16496) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17186) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17873) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:18563) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19253) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19940) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:20631) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image
[jira] [Commented] (FOP-1776) NPE caused by nested empty fo:inline with id
[ https://issues.apache.org/jira/browse/FOP-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051008#comment-17051008 ] Mathieu Malaterre commented on FOP-1776: Attached patch from Dan as fop1776.patch > NPE caused by nested empty fo:inline with id > > > Key: FOP-1776 > URL: https://issues.apache.org/jira/browse/FOP-1776 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Mathieu Malaterre >Priority: Major > Attachments: _test.fo, anchor.id.patch, fop1776.patch, test2.fo > > > Here is my input docbook file: > > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; []> > > > title > > > The id="example.anchor.1"/>anchor element is empty and > contributes > nothing to the flow of the content in which it occurs. It is only useful > as a target. > > > > > which I process with: > /usr/bin/xsltproc --stringparam fop1.extensions 1 --stringparam > ulink.show 0 --xinclude -o test2.fo > /usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl test2.xml > and lead to: > $ ./fop test2.fo test2.pdf > Feb 17, 2010 2:52:18 PM org.apache.fop.apps.FOURIResolver resolve > SEVERE: Error with opening URL > 'http://docbook.sourceforge.net/release/images/draft.png': Network is > unreachable > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:9588) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10285) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:10980) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:11672) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:12361) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13050) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:13736) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:14427) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15118) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:15806) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:16496) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17186) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:17873) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:18563) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19253) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:19940) > Feb 17, 2010 2:52:18 PM org.apache.fop.events.LoggingEventListener > processEvent > SEVERE: Image not found. URI: > http://docbook.sourceforge.net/release/images/draft.png. (See position > 2:20631) > Feb 17, 2010 2:52:18 PM
[jira] [Commented] (FOP-2469) [PATCH] auto table layout
[ https://issues.apache.org/jira/browse/FOP-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725230#comment-15725230 ] Mathieu Malaterre commented on FOP-2469: This is getting very confusing. I suspect that from reading: https://wiki.apache.org/xmlgraphics-fop/AutoTableLayout the following issues should be assumed to be closed (invalid / marked as duplicates?): * https://issues.apache.org/jira/browse/FOP-1226 * https://issues.apache.org/jira/browse/FOP-1674 * https://issues.apache.org/jira/browse/FOP-2450 Could someone please clarify that the issue associated with auto table layout really is #2469 > [PATCH] auto table layout > - > > Key: FOP-2469 > URL: https://issues.apache.org/jira/browse/FOP-2469 > Project: FOP > Issue Type: Bug > Components: layout/unqualified >Affects Versions: trunk > Environment: Windows 7, JDK 7 >Reporter: Gregor Berg >Assignee: Andreas L. Delmelle > Fix For: trunk > > Attachments: 2015-05-13-auto-table-layout.patch, > 2015-05-27-LM-to-LC-refactoring.patch, > 2015-06-09-LM-to-LC-refactoring-update.patch, FOP-2469_20150621.patch, > FOP2469-auto-table-layout.xml, resize-all-but-static-spanned-columns.xml, > resize-spanned-columns.xml, warning-only-static-columns-are-spanned.xml > > > Hi, > this is a patch which enables table-layout=auto. It is quite robust, it can > not only handle linebreaks and pagebreaks, but it also copes with auto tables > in fixed tables in auto tables. > Essentially, it is the patch of issue FOP-2450 adapted to the trunk version > of FOP. > Best regards, > Gregor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2569) Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[ https://issues.apache.org/jira/browse/FOP-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131937#comment-15131937 ] Mathieu Malaterre commented on FOP-2569: As explained in my post, I am not looking for newer OFFO release. I'd like to be able to generate *.hyp from *.xml input file, which used to be the case (eg. fop 1.1). AFAIK the XML -> HYP conversion is maintained within the fop team and not by the OFFO team. > Exception in thread "main" java.lang.StackOverflowError at > org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > -- > > Key: FOP-2569 > URL: https://issues.apache.org/jira/browse/FOP-2569 > Project: FOP > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mathieu Malaterre > Fix For: 1.1 > > > fop + offo is broken since release 2.0 (and 2.1). It used to be possible to > build fop-hyph.jar using fop 1.1. Please resurrect a working hyph building > mechanism. > Here is what it states: > $ /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Xss512k -classpath > /home/mathieu/debian/fop/fop-2.1/build/classes > org.apache.fop.hyphenation.SerializeHyphPattern > /home/mathieu/debian/fop/fop-2.1/hyph > /home/mathieu/debian/fop/fop-2.1/build/classes/hyph > Processing /home/mathieu/debian/fop/fop-2.1/hyph/sa.xml > Exception in thread "main" java.lang.StackOverflowError > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > [...] > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > See thread: > http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201602.mbox/%3CCA%2B7wUszWN2PdZY_t_Kgn0E4eatL7CUQswOWj9XC%3Dg9GDdgsyXw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2569) Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
Mathieu Malaterre created FOP-2569: -- Summary: Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) Key: FOP-2569 URL: https://issues.apache.org/jira/browse/FOP-2569 Project: FOP Issue Type: Bug Affects Versions: 2.0 Reporter: Mathieu Malaterre Fix For: 1.1 fop + offo is broken since release 2.0 (and 2.1). It used to be possible to build fop-hyph.jar using fop 1.1. Please resurrect a working hyph building mechanism. Here is what it states: $ /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Xss512k -classpath /home/mathieu/debian/fop/fop-2.1/build/classes org.apache.fop.hyphenation.SerializeHyphPattern /home/mathieu/debian/fop/fop-2.1/hyph /home/mathieu/debian/fop/fop-2.1/build/classes/hyph Processing /home/mathieu/debian/fop/fop-2.1/hyph/sa.xml Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) [...] at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) See thread: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201602.mbox/%3CCA%2B7wUszWN2PdZY_t_Kgn0E4eatL7CUQswOWj9XC%3Dg9GDdgsyXw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2569) Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[ https://issues.apache.org/jira/browse/FOP-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130016#comment-15130016 ] Mathieu Malaterre commented on FOP-2569: It would be nice it ant jar-hyphenation would return a non-zero return code, so that this issue does not come back later on. ``` $ CLASSPATH=/usr/share/java/xmlgraphics-commons-2.1.jar ant jar-hyphenation [...] [java] at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) [java] at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) [java] at org.apache.f [java] Java Result: 1 [echo] Hyphenation failed uptodate-jar-hyphenation: jar-hyphenation: BUILD SUCCESSFUL Total time: 45 seconds ``` > Exception in thread "main" java.lang.StackOverflowError at > org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > -- > > Key: FOP-2569 > URL: https://issues.apache.org/jira/browse/FOP-2569 > Project: FOP > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mathieu Malaterre > Fix For: 1.1 > > > fop + offo is broken since release 2.0 (and 2.1). It used to be possible to > build fop-hyph.jar using fop 1.1. Please resurrect a working hyph building > mechanism. > Here is what it states: > $ /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Xss512k -classpath > /home/mathieu/debian/fop/fop-2.1/build/classes > org.apache.fop.hyphenation.SerializeHyphPattern > /home/mathieu/debian/fop/fop-2.1/hyph > /home/mathieu/debian/fop/fop-2.1/build/classes/hyph > Processing /home/mathieu/debian/fop/fop-2.1/hyph/sa.xml > Exception in thread "main" java.lang.StackOverflowError > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > [...] > at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244) > See thread: > http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201602.mbox/%3CCA%2B7wUszWN2PdZY_t_Kgn0E4eatL7CUQswOWj9XC%3Dg9GDdgsyXw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2569) Exception in thread "main" java.lang.StackOverflowError at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[
https://issues.apache.org/jira/browse/FOP-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130016#comment-15130016
]
Mathieu Malaterre edited comment on FOP-2569 at 2/3/16 8:29 AM:
It would be nice it ant jar-hyphenation would return a non-zero return code, so
that this issue does not come back later on.
{{{
$ CLASSPATH=/usr/share/java/xmlgraphics-commons-2.1.jar ant jar-hyphenation
[...]
[java] at
org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[java] at
org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[java] at org.apache.f
[java] Java Result: 1
[echo] Hyphenation failed
uptodate-jar-hyphenation:
jar-hyphenation:
BUILD SUCCESSFUL
Total time: 45 seconds
}}}
was (Author: malaterre):
It would be nice it ant jar-hyphenation would return a non-zero return code, so
that this issue does not come back later on.
```
$ CLASSPATH=/usr/share/java/xmlgraphics-commons-2.1.jar ant jar-hyphenation
[...]
[java] at
org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[java] at
org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
[java] at org.apache.f
[java] Java Result: 1
[echo] Hyphenation failed
uptodate-jar-hyphenation:
jar-hyphenation:
BUILD SUCCESSFUL
Total time: 45 seconds
```
> Exception in thread "main" java.lang.StackOverflowError at
> org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> --
>
> Key: FOP-2569
> URL: https://issues.apache.org/jira/browse/FOP-2569
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mathieu Malaterre
> Fix For: 1.1
>
>
> fop + offo is broken since release 2.0 (and 2.1). It used to be possible to
> build fop-hyph.jar using fop 1.1. Please resurrect a working hyph building
> mechanism.
> Here is what it states:
> $ /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Xss512k -classpath
> /home/mathieu/debian/fop/fop-2.1/build/classes
> org.apache.fop.hyphenation.SerializeHyphPattern
> /home/mathieu/debian/fop/fop-2.1/hyph
> /home/mathieu/debian/fop/fop-2.1/build/classes/hyph
> Processing /home/mathieu/debian/fop/fop-2.1/hyph/sa.xml
> Exception in thread "main" java.lang.StackOverflowError
> at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> [...]
> at org.apache.fop.hyphenation.TernaryTree.insert(TernaryTree.java:244)
> See thread:
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201602.mbox/%3CCA%2B7wUszWN2PdZY_t_Kgn0E4eatL7CUQswOWj9XC%3Dg9GDdgsyXw%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2512) java.lang.NullPointerException: Parameter alpha must not be null
[ https://issues.apache.org/jira/browse/FOP-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791731#comment-14791731 ] Mathieu Malaterre commented on FOP-2512: Adding direct link: https://jmodalwindow.java.net/manual/dpl/html_single/index.html#prg.perl.image.magick.pdf > java.lang.NullPointerException: Parameter alpha must not be null > > > Key: FOP-2512 > URL: https://issues.apache.org/jira/browse/FOP-2512 > Project: FOP > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mathieu Malaterre > > fop is not capable of dealing with some PNG, it keeps on failing with: > Error while rendering page 9 > java.lang.NullPointerException: Parameter alpha must not be null > Exception > java.lang.NullPointerException: Parameter alpha must not be null > Input is: > $ pnginfo test.png > test.png... > Image Width: 411 Image Length: 225 > Bitdepth (Bits/Sample): 8 > Channels (Samples/Pixel): 1 > Pixel depth (Pixel Depth): 8 > Colour Type (Photometric Interpretation): PALETTED COLOUR with alpha (18 > colours, 17 transparent) > Image filter: Single row per byte filter > Interlacing: No interlacing > Compression Scheme: Deflate method 8, 32k window > Resolution: 0, 0 (unit unknown) > FillOrder: msb-to-lsb > Byte Order: Network (Big Endian) > Number of text strings: 0 of 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2512) java.lang.NullPointerException: Parameter alpha must not be null
Mathieu Malaterre created FOP-2512: -- Summary: java.lang.NullPointerException: Parameter alpha must not be null Key: FOP-2512 URL: https://issues.apache.org/jira/browse/FOP-2512 Project: FOP Issue Type: Bug Affects Versions: 2.0 Reporter: Mathieu Malaterre fop is not capable of dealing with some PNG, it keeps on failing with: Error while rendering page 9 java.lang.NullPointerException: Parameter alpha must not be null Exception java.lang.NullPointerException: Parameter alpha must not be null Input is: $ pnginfo test.png test.png... Image Width: 411 Image Length: 225 Bitdepth (Bits/Sample): 8 Channels (Samples/Pixel): 1 Pixel depth (Pixel Depth): 8 Colour Type (Photometric Interpretation): PALETTED COLOUR with alpha (18 colours, 17 transparent) Image filter: Single row per byte filter Interlacing: No interlacing Compression Scheme: Deflate method 8, 32k window Resolution: 0, 0 (unit unknown) FillOrder: msb-to-lsb Byte Order: Network (Big Endian) Number of text strings: 0 of 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2513) First element must be the fo:root formatting object
Mathieu Malaterre created FOP-2513: -- Summary: First element must be the fo:root formatting object Key: FOP-2513 URL: https://issues.apache.org/jira/browse/FOP-2513 Project: FOP Issue Type: Bug Affects Versions: 2.0 Reporter: Mathieu Malaterre With: $ cat in.xml /tmp ?xml version=1.0 encoding=UTF-8? !DOCTYPE article PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; article articleinfo titletitle/title author firstnameauthor/firstname surnameauthor2/surname affiliation orgnamebla/orgname /affiliation /author pubdate2001/pubdate /articleinfo section titlesection 1/title paratext section 1/para figure titlefirst/title mediaobject imageobject imagedata fileref=openlogo-100.png/ /imageobject /mediaobject /figure /section /article and: $ wget http://www.debian.org/logos/openlogo-100.png here is what I get: $ fop in.xml in.pdf [ERROR] FOP - Exception org.apache.fop.apps.FOPException: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document. javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document.org.apache.fop.apps.FOPException: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document. javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document. at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document. at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:502) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:285) ... 3 more Caused by: org.apache.fop.fo.ValidationException: First element must be the fo:root formatting object. Found (Namespace URI: , Local Name: article) instead. Please make sure you're producing a valid XSL-FO document. at org.apache.fop.events.ValidationExceptionFactory.createException(ValidationExceptionFactory.java:38) at org.apache.fop.events.EventExceptionManager.throwException(EventExceptionManager.java:58) at org.apache.fop.events.DefaultEventBroadcaster$1.invoke(DefaultEventBroadcaster.java:175) at com.sun.proxy.$Proxy0.invalidFORoot(Unknown Source) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:269) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:179) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at
[jira] [Created] (FOP-2182) org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221)
Mathieu Malaterre created FOP-2182: -- Summary: org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) Key: FOP-2182 URL: https://issues.apache.org/jira/browse/FOP-2182 Project: Fop Issue Type: Bug Reporter: Mathieu Malaterre I cannot build an rtf file from a fo. It keep on failing with: java.lang.NullPointerException at org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) at org.apache.fop.fo.pagination.PageSequence.startOfNode(PageSequence.java:119) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:325) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:300) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:130) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2182) org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221)
[ https://issues.apache.org/jira/browse/FOP-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathieu Malaterre updated FOP-2182: --- Attachment: demo.fo $ fop -fo demo.fo -rtf demo.rtf org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) --- Key: FOP-2182 URL: https://issues.apache.org/jira/browse/FOP-2182 Project: Fop Issue Type: Bug Reporter: Mathieu Malaterre Attachments: demo.fo I cannot build an rtf file from a fo. It keep on failing with: java.lang.NullPointerException at org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) at org.apache.fop.fo.pagination.PageSequence.startOfNode(PageSequence.java:119) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:325) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:300) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:130) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
