Hi,
To keep issue alive, I reported a bug:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51149
Regards,
Ognjen
On 19.3.2011 12:30, Ognjen Blagojevic wrote:
Jeremias,
For this particular image, with Java 6u17 I get:
[DEBUG] New ImageAdapter created for key:
I suppose you have JAI installed in both 6u17 and 6u18/24?
Peter West
Why do you seek the living among the dead? He is not here, but is risen.
On 04/05/2011, at 8:17 PM, Ognjen Blagojevic wrote:
Hi,
To keep issue alive, I reported a bug:
Hi Peter,
I didn't install anything other than regular JDK for Linux.
Do you mean JAI library or JAI Image I/O tools? They are both
mentioned in FOP docs [1], but from what I understand neither is
necessary for PNG image manipulation:
(BMP, TIFF) Requires the presence of JAI Image I/O Tools
Ognjen,
You may well have it, depending on where you got your Java installation. I see
you're on windows, so it's probably already included. With linux, I used to
have to install it myself, but I've been using OS X for a while now, so I don't
know about either Windows or linux any more.
The
On 11.3.2011 12:54, Ognjen Blagojevic wrote:
Having said all this, my proposal is:
1. if someone can help me to track bug further (remember, 1.6.0_17 was
working just fine) we could file the bug report to Oracle, or
2. we could just add the info in FOP/xmlgraphics docs that color profile
in PNG
@xmlgraphics.apache.org
Subject: Re: 20x slowdown in PNG processing when switching from JDK
1.6.0_17 to 1.6.0_18
On 11.3.2011 12:54, Ognjen Blagojevic wrote:
Having said all this, my proposal is:
1. if someone can help me to track bug further (remember, 1.6.0_17 was
working just fine) we could file
Ognjen,
sorry for the late answer. Could you please set the following log level
to FINE/DEBUG: org.apache.fop.render.pdf.AbstractImageAdapter
If you get the line Image returns ICC profile: sRGB, default sRGB=true,
your PNG is a normal sRGB bitmap. This will (normally) allow FOP to dump
the bitmap
To: fop-dev@xmlgraphics.apache.org
Subject: Re: 20x slowdown in PNG processing when switching from JDK
1.6.0_17 to 1.6.0_18
On 11.3.2011 12:54, Ognjen Blagojevic wrote:
Having said all this, my proposal is:
1. if someone can help me to track bug further (remember, 1.6.0_17 was
working just
