Gimp is also, for now, limited to srgb, so anything coming from gimp
will work fine with cairo.
And, for a postscript printer, jpegs should be converted directly to ps,
not via pdf, so that wouldn't matter either.
But if you used a workflow which used, say, AdobeRGB as the colour
working space, a
pdftocairo is limited by the fact that cairo only handles sRGB.
It is therefore unsuitable any time color is important, eg if the pdf
uses cmyk or named colors or icc profiles, et cetera.
It is fine for printing most web pages, since the browser likely also is
limited to sRGB.
And for simple per
pdftops and pdftocairo are both from poppler.
pdftops is based on the original xpdf code and does not use cairo at
all.
modern cairo tries to limit the size of tranparency groups to just where
it is needed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
[I posted this to the poppler bug, but it may be of interest here, too.
-JimC]
The reason the level3 ghostscript generates does not cause the problem
is that ghostscript’s level3 is essentially the same as its level2; only
the name of the procset is different.
Xpdf, OTOH, does generate different
