[ 
https://issues.apache.org/jira/browse/FOP-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422699#comment-17422699
 ] 

Martin Leitner commented on FOP-2524:
-------------------------------------

[~ssteiner] You tried something different than the original submitter described.

It may well be that initializing FopFactoryBuilder works when providing the 
config as an InputStream. That does not mean that the issue is not reproducible.

You have not checked if fopFactoryBuilder.setConfiguration(fopConfig) works as 
expected. I can confirm that it does not, and among the configuration fields 
that are ignored are the following: source-resolution, target-resolution, 
complex-scripts, accessibility

I get the impression that "Cannot reproduce" is just Apache-speak for "We don't 
care"

> FOP 2.0: target-resolution not set in FoUserAgent
> -------------------------------------------------
>
>                 Key: FOP-2524
>                 URL: https://issues.apache.org/jira/browse/FOP-2524
>             Project: FOP
>          Issue Type: Bug
>          Components: renderer/png
>    Affects Versions: 2.0
>         Environment: Java 1.8.0_51, 64 Bit, Windows 7, Windows 2008 R2
>            Reporter: MH
>            Priority: Major
>         Attachments: screenshot-FOP-PNG-Renderer.png
>
>
> We upgraded from FOP 1.0 to FOP 2.0 (as we had to skip FOP 1.1 due to a 
> blocker bug in 1.1). After converting all Java embedding code, we are now in 
> test phase. Almost everything looks good, but our PNG rendered documents 
> suddenly all look very blurry (see atachement). We had the same problem with 
> FOP 1.0 but "solved" it by setting the target resolution to 288:
> <target-resolution>288</target-resolution>
> We still have this setting in the fop user config XML file, but it seems that 
> it has no effect anymore!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to