Vincent Hennebert (JIRA | 22 Jul 20:46 2014
Picon

[jira] [Resolved] (FOP-2297) Degraded output from SVG external graphic on upgrade from fop-1.0 to fop-1.1


     [
https://issues.apache.org/jira/browse/FOP-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Hennebert resolved FOP-2297.
------------------------------------

    Resolution: Not a Problem

AFAICT, the code is working as expected. In fact, before the change from rev. 987423 there were two bugs:
* the target-resolution was having an effect on the image size, while it shouldn't (this is
source-resolution's purpose);
* the target-resolution was not being taken into account when generating raster images to represent
constructs like filter effects.

That means that raster images were being generated according to the SVG's original size rather than the
target resolution.

If the SVG ended up being scaled down in the FO document, the result was fine since the raster image was also
scaled down. However, if the SVG had to be scaled up, the pixellisation was showing up. This is what
prompted the change from rev. 987423.

The consequence of that change is that, with default settings, images from scaled-down SVGs are now
generated at a lower resolution (smaller number of pixels) than before. Which may make them look more
pixellated, like for the attached Google.svg image.

The good news is that it is now possible to control the resolution of raster images generated from SVG,
thanks to the target-resolution config parameter being effective. The default value of 72dpi is
probably a bit low for a printed output, and it wouldn't be unreasonable to set it at 300dpi.

(Continue reading)

Luis Bernardo (JIRA | 22 Jul 20:02 2014
Picon

[jira] [Commented] (FOP-2396) font tag attribute embed-url is expecting absoulte-URL


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

Luis Bernardo commented on FOP-2396:
------------------------------------

please provide information regarding the version you are using, whether you are running from the command
line, and whether the current directory is the same where the FO file, the config file, and the fonts
directory are.

> font tag attribute embed-url is expecting absoulte-URL
> ------------------------------------------------------
>
>                 Key: FOP-2396
>                 URL: https://issues.apache.org/jira/browse/FOP-2396
>             Project: Fop
>          Issue Type: Bug
>            Reporter: ramakanthreddy
>
> Hi,
> I have specified the font tag as below:
>  <font  kerning="yes" embed-url="fonts/arial.ttf">
>     <font-triplet name="Arial" style="normal" weight="normal"/>
>     <font-triplet name="ArialMT" style="normal" weight="normal"/>
>  </font>
> but the code is expecting absoulte-URL.throws error as below when specify the relative path
> org.apache.fop.apps.FOPException: Failed to resolve font with embed-url 'fonts/arial.ttf'
> 	at org.apache.fop.util.LogUtil.handleError(LogUtil.java:42)
(Continue reading)

Glenn Adams (JIRA | 22 Jul 18:00 2014
Picon

[jira] [Resolved] (FOP-2397) Unable to set font base url programatically


     [
https://issues.apache.org/jira/browse/FOP-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glenn Adams resolved FOP-2397.
------------------------------

    Resolution: Invalid

A comment description that says "X doesn't work" is not a bug report. You need to provide details. I'm
marking this issue as INVALID at this point. If you do provide sufficient details, then it can be reopened.

> Unable to set font base url programatically
> -------------------------------------------
>
>                 Key: FOP-2397
>                 URL: https://issues.apache.org/jira/browse/FOP-2397
>             Project: Fop
>          Issue Type: Bug
>            Reporter: ramakanthreddy
>
> I tried to set font base url as below but it is not working.
> fopFactory.getFontManager().setFontBaseURL("file://C:/WINDOWS/Fonts");

--
This message was sent by Atlassian JIRA
(v6.2#6252)

Luis Bernardo (JIRA | 22 Jul 15:39 2014
Picon

[jira] [Resolved] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


     [
https://issues.apache.org/jira/browse/FOP-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luis Bernardo resolved FOP-2398.
--------------------------------

       Resolution: Fixed
    Fix Version/s: trunk

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
written with the default resolution of 72 DPI.

(Continue reading)

Luis Bernardo (JIRA | 22 Jul 15:39 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Luis Bernardo commented on FOP-2398:
------------------------------------

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1612567 and http://svn.apache.org/viewvc?view=revision&revision=1612568.

Default source resolution is only used if not set yet (in the APP0 segment).

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
(Continue reading)

Seifeddine Dridi (JIRA | 22 Jul 15:25 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Seifeddine Dridi commented on FOP-2398:
---------------------------------------

Setting the source-resolution is not an option. I'll see if adding the missing tags in the image fixes the
problem, otherwise there must be a problem with the JPEG preloader. Either way I'll report back here.

Thanks

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
written with the default resolution of 72 DPI.
(Continue reading)

Luis Bernardo (JIRA | 22 Jul 15:12 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Luis Bernardo commented on FOP-2398:
------------------------------------

Yes, the image has an EXIF entry but apparently is missing many of the expected tags (see
http://www.media.mit.edu/pia/Research/deepview/exif.html) and that is the source of the problem.
This needs to be investigated. Meanwhile set your source-resolution to 96 in the config file and you
should get the same behavior as before. 

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
written with the default resolution of 72 DPI.
(Continue reading)

Seifeddine Dridi (JIRA | 22 Jul 14:26 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Seifeddine Dridi commented on FOP-2398:
---------------------------------------

My image has an APP0 segment followed by APP1. When reading the first segment, FOP correctly parses the
image resolution but then it is overridden by the APP1 segment right after.

Thanks

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
written with the default resolution of 72 DPI.
(Continue reading)

Luis Bernardo (JIRA | 22 Jul 14:10 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Luis Bernardo commented on FOP-2398:
------------------------------------

I need to check the image but the intrinsic resolution can be set in the (old) APP0 segment or in the (newer)
APP1 (EXIF) segment. The code was ignoring the APP1 segment which was causing problems with newer images
that do not have the APP0 segment. The current code can handle both APP0 and APP1 and the first found is the
one used. Now, images can have both segments, and can have different intrinsic resolutions in the
different segments. If your image has APP1 before APP0 and the intrinsic resolution there is 72 that would
explain the issue you see.

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
(Continue reading)

Luis Bernardo (JIRA | 22 Jul 13:58 2014
Picon

[jira] [Commented] (FOP-2307) Weird border color inheritance (hashCode collisions)


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

Luis Bernardo commented on FOP-2307:
------------------------------------

The original issue does not happen in current trunk due to changes to
CommonBorderPaddingBackground.equals(), which now, incorrectly, compares two colors by comparing
that they are the same instance. This effectively disables caching since a cached color property will be
replaced by a new instance of the same color (whether that has practical performance implications is
another question...).

> Weird border color inheritance (hashCode collisions)
> ----------------------------------------------------
>
>                 Key: FOP-2307
>                 URL: https://issues.apache.org/jira/browse/FOP-2307
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/pdf
>    Affects Versions: 1.1
>         Environment: Windows 7/64-bit, Oracle JDK 7.0.45 64-bit
>            Reporter: Jan Tošovský
>              Labels: border, cmyk, color
>
> When I define an object with a specific border and the thickness of this border matches with the one defined
in the static-content, the latter color is used instead. But it appears only if my object color is
specified using the pseudo #CMYK profile.
(Continue reading)

Seifeddine Dridi (JIRA | 22 Jul 13:38 2014
Picon

[jira] [Commented] (FOP-2398) [AFP] Image written as having 72 DPI instead of its intrinstic resolution


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

Seifeddine Dridi commented on FOP-2398:
---------------------------------------

Luis any explanation?

> [AFP] Image written as having 72 DPI instead of its intrinstic resolution
> -------------------------------------------------------------------------
>
>                 Key: FOP-2398
>                 URL: https://issues.apache.org/jira/browse/FOP-2398
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/afp
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>         Attachments: afp-config.xml, bug-image-dpi.afp, bug-image-dpi.fo, image.jpg
>
>
> Prior to a change made in XMLGraphicsCommons (https://issues.apache.org/jira/browse/XGC-87),
rendering the attached FO to AFP always results in an image with its original resolution. Now the image is
written with the default resolution of 72 DPI.

--
This message was sent by Atlassian JIRA
(Continue reading)


Gmane