It's claimed here that the bug is in evince, but I don't actually see the evidence. The "bad" PDFs produced by evince display render perfectly in evince, xpdf, and gs; the output of pstopdf on those files also renders perfectly in evince and gs. It's just the printer that is complaining.
It seems to me that *if* the PDF/PS files evince is generating are legal, and just happen to trigger a printer bug, then it's really cups' job to work around that printer bug, not evince's to somehow intuit what sort of printer the file will eventually be sent to after being passed through some set of filters they have no control over. Of course, it maybe be that evince/xpdf/gs are in just lenient when displaying stuff, and evince is actually generating buggy PDF/PS, in which case it should be fixed. But to make that argument surely we need someone to actually look at the postscript spec and figure things out. -- Printing from evince (and perhaps other GTK apps) to PostScript printers is broken https://bugs.launchpad.net/bugs/419143 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
