Dear developers, thanks for the great app!
I am running: prince file.svg -o file.pdf
The issue I am reporting is that the resulting PDF contains an embedded image which is far from identical to the original image embedded in SVG (the two screenshots are provided in attachments). Looks like the image is being rasterized at low resolution when it shouldn't be rasterized at all: it can be embedded without loss of quality via /FlateDecode.
The issue is most evident in prince-bug.svg (attached), where an apparent resolution of the rasterized image embedded in PDF looks like 100-150dpi. prince-bug-minimal.svg is my attempt to minimally reproduce the problem, and in this case the embedded image in PDF looks fine.
In any case, rasterization is unnecessary in all such cases.
P.S.
And also, it seem like Price XML sets the <interpolate> tag for the images that it embeds in PDF. I may be subjective here, but it seems like it's both unnecessary and detrimental to the visual quality of the result. It was mostly used in the old days when Adobe Reader used a simplistic algorithm for bitmap image rendering (neares-neighbour) with bad quality results, and turning on the <interpolate> tag seemed to help somewhat. It has long fallen out of fashion since then. Again, this is, obviously, not a bug in Price XML, it's just my opinion on the feature.
I am running: prince file.svg -o file.pdf
The issue I am reporting is that the resulting PDF contains an embedded image which is far from identical to the original image embedded in SVG (the two screenshots are provided in attachments). Looks like the image is being rasterized at low resolution when it shouldn't be rasterized at all: it can be embedded without loss of quality via /FlateDecode.
The issue is most evident in prince-bug.svg (attached), where an apparent resolution of the rasterized image embedded in PDF looks like 100-150dpi. prince-bug-minimal.svg is my attempt to minimally reproduce the problem, and in this case the embedded image in PDF looks fine.
In any case, rasterization is unnecessary in all such cases.
P.S.
And also, it seem like Price XML sets the <interpolate> tag for the images that it embeds in PDF. I may be subjective here, but it seems like it's both unnecessary and detrimental to the visual quality of the result. It was mostly used in the old days when Adobe Reader used a simplistic algorithm for bitmap image rendering (neares-neighbour) with bad quality results, and turning on the <interpolate> tag seemed to help somewhat. It has long fallen out of fashion since then. Again, this is, obviously, not a bug in Price XML, it's just my opinion on the feature.