D7949: Allow to print pdf doc directly into a QPrinter

Oliver Sander noreply at phabricator.kde.org
Wed Oct 11 15:55:03 UTC 2017


sander added a comment.


  Hi, thanks again for the review.  I just updated the patch to include most of your suggestions.
  
  >>  I tagged this option as 'experimental' in the GUI.
  >  Having it only in the tooltip is definitely not enough, this should be directly in the combobox. The tooltip could contain additional information (Which > features are missing? What rendering problems are expected? Are bug reports / contributions encouraged?). Optionally add a longer "What's this?" help.
  
  I implemented  a longer "What's this" help, but I couldn't make it appear in the GUI.  What's the magic button for that?
  
  > Therefore, I would highly recommend to only enable Arthur if Poppler is recent enough (add an #ifdef).
  
  Poppler 0.60 or a Windows OS is required now.
  
  > I took https://arxiv.org/pdf/1708.01455.pdf and printed to a "PDF file" (can be observed in an Arthur based Okular, too):
  > 
  >   page 21: parts of vector (?) illustration missing
  
  A patch for this can be found at https://bugs.freedesktop.org/show_bug.cgi?id=103118
  
  >   large filesize (5x), because of letters being vectors instead of fonts 
  
  Yeah, I know about this one.  There's nothing really do be done about this on the Okular side, this is Qt's doing.
  On the other hand one could argue that this is what "printing to a file" actually means: you lose all semantic
  information like letters, annotations, tags, etc.
  
  > (might lead to problems regarding the printer's cpu/memory resources?)
  
  No idea.

REVISION DETAIL
  https://phabricator.kde.org/D7949

To: sander, #okular
Cc: ltoscano, rkflx, michaelweghorn, ngraham, aacid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/okular-devel/attachments/20171011/fd72bb08/attachment.html>


More information about the Okular-devel mailing list