[Poppler-bugs] [Bug 87637] pdfseparate+pdftoppm renders different than original file

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87637

--- Comment #19 from Thomas Freitag <Thomas.Freitag at alfa.de> ---
(In reply to Albert Astals Cid from comment #18)
> No that doesn't help, somehow it ends up breaking the file output.
> 

Oh, there is a bug in the goo formatter which produces illegal floating point
strings in this case. 

> I realized it goes away if i don't use -r 72 on the pdftoppm call, any idea
> why that may be?

Yes, it's definetely the difference in the mediabox. If You have an exact look
at the pixel which changed You will encounter that they are always at the
beginning or end of a line which is drawn by the stroke command. The comes from
the different mediabox and anti aliasing effects computed for the start or the
end of a stroke path.

With 144 dpi the difference is small enough so that the output is the same.

With pdfcairo there are no differences in the output.

Also if You compile poppler with 

#define USE_FIXEDPOINT 1

You will see no difference. But to prove it beyond doubt I will upload a small
patch just for testing purposes with rounds the mediabox at the tenth decimal
place :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/poppler-bugs/attachments/20160205/03e13d01/attachment.html>