[
https://issues.apache.org/jira/browse/XGC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010892#comment-15010892
]
Luis Bernardo commented on XGC-102:
-----------------------------------
ImageLoaderRawPNG was not available in FOP 1.0. Can you provide the output
generated with FOP 1.0 and the original PNG used?. I think the issue you see is
not resolution but the gamma chunk. The ImageLoaderRawPNG does not handle the
gamma chunk. And not all viewers apply the gamma transformation. It is possible
that the ImageLoaderImageIO applies the gamma transformation, in which case you
get the desired output, even if it looks different from what your viewer shows
(if the viewer ignores the gamma chunk).
> Problem in rendering PNG images with ImageLoaderRawPNG in XMLGraphics 2.0.1
> and FOP2.0
> --------------------------------------------------------------------------------------
>
> Key: XGC-102
> URL: https://issues.apache.org/jira/browse/XGC-102
> Project: XMLGraphicsCommons
> Issue Type: Bug
> Components: general
> Affects Versions: 2.0.1
> Environment: FOP 2.0., PDF rendering of a PNG Image using
> ImageLoaderRawPNG
> Reporter: Mandar Nimbkar
> Fix For: 2.0.1
>
> Attachments: Docs.zip, FOP_2.0.rar, Images.rar
>
>
> I am migrating from FOP 1.0 to FOP 2.0
> I have made the required Java code changes as per the changed API.
> There are PNG images used in the report generated using PDF renderer..
> Initially with FOP 1.0, I tried ImageLoaderPNG. However, the resolution of
> the image gets impacted. So I shifted to ImageLoaderRawPNG which rendered it
> properly.
> So this was working fine with FOP 1.0
> However, FOP 2.0 is not able to render the image with ImageLoaderRawPNG and
> throws exception..
> Attached the PNG image, exception and the intermediate XSL-FO file (partial)
> generated with ImageLoaderRawPNG.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
