https://bugs.kde.org/show_bug.cgi?id=467328
--- Comment #5 from Sergio <sergio.calleg...@gmail.com> --- @Oliver Sanders > (In reply to Oliver Sander from comment #4) > Printing in Okular is a bit special. > > I conjecture that you can print your document if you select the 'force > rasterization' option in the print dialog. Your conjecture is correct. Even if this workaround is effective, I think that this issue deserves attention: - first, forcing rasterization does not fix the wrong preview; - secondly, one typically works with force rasterization off (also because it can slow things down in some cases and I am not sure whether it can affect the printout quality in some cases). It is not nice when you discover that you have printed 200 bad pages that you should have forced rasterization; - thirdly, in some occasions the issue is subtle. Here, I have managed crafting a PDF where all the characters get substituted by little squares when printing, which make the bug quite detectable. However, in some cases out of a multipage document you end up only missing a word on a single page or a few characters here and there. It is very easy to miss the issue and pass around an unprofessionally looking document or even signing an incomplete document; - finally, due to the complexity of the PDF standard issues like this one tend to make one doubt the correctness of the original PDF. Is it OK or slightly out of specs, so that some viewer can print it and some other cannot? Unfortunately, this issue has already prompted the opening of inquires on the Libreoffice tracker and the Source Sans 3 font tracker. Out of curiosity, in what sense printing in Okular is a bit special? In cases where rasterization is not explicitly required, cannot the PDF be passed to the printing subsystem more or less as is? -- You are receiving this mail because: You are the assignee for the bug.
