1. 18 May, 2020 3 commits
  2. 16 May, 2020 1 commit
  3. 15 May, 2020 6 commits
  4. 13 May, 2020 2 commits
  5. 12 May, 2020 1 commit
    • Marek Kasik's avatar
      cairo: Fix tiling patterns when pattern cell is too far · 9c3b18b8
      Marek Kasik authored
      Rendering of tiling pattern which has pattern matrix moving pattern cell
      far away can fail on allocation of memory. This commit solves the issue by
      modifying of cairo pattern matrix so that its offset is closer to the path
      filled by the pattern.
      Fixes #190
  6. 11 May, 2020 4 commits
  7. 09 May, 2020 1 commit
  8. 02 May, 2020 1 commit
    • Oliver Sander's avatar
      Allow almost-singular tiling pattern matrices · 2c17c9ed
      Oliver Sander authored
      Issue poppler/poppler#894
      sports a file with a diagonal tiling pattern matrices with
      diagonal entries in the range of 5e-4.  While entries of this
      size are unusual but okay, the determinant is below the rather
      arbitrary threshold of 1e-6.  Therefore, poppler decided that
      the matrix is singular and aborts the rendering.
      Fix this by really only aborting if inverting the determinant
      (which is the first thing that is being done with it) results
      in a non-finite number.
      As a side effect the code now also allows pattern matrices
      with a negative determinant.  This does not seem to appear
      in the wild all that often, but I didn't find anything
      in the spec that rules it out.
      BUG: poppler/poppler#894
  9. 27 Apr, 2020 1 commit
  10. 25 Apr, 2020 1 commit
    • Nelson Benítez León's avatar
      glib: implement rotation for 'flagNoRotate' annots · b7aed3eb
      Nelson Benítez León authored
      previously poppler_page_get_annot_mapping() function
      was ignoring to rotate annots flagged as 'flagNoRotate'
      probably because they require a special rotation where
      the annotation pivots on the upper left corner, as
      described in PDF 1.7 spec "8.4.2 Annotation Flags"
      NoRotate flag.
      Added support for that, while refactoring the code to
      make it more readable.
      Fixes #767
  11. 23 Apr, 2020 3 commits
    • Albert Astals Cid's avatar
      Update (C) year · 33f34557
      Albert Astals Cid authored
    • Albert Astals Cid's avatar
      qt5: Add Document::signatures · 12eeb475
      Albert Astals Cid authored
      Returns all the signatures of a given document, this is better
      than iterating over all the pages getting the form fields that
      are of signature type since there's documents with signatures not
      associated to a given page
      Fixes part of #895
    • Albert Astals Cid's avatar
      pdfsig: Show also signatures that aren't attached to any page · ba311960
      Albert Astals Cid authored
      Move two methods from FormWidgetSignature to FormFieldSignature where
      they actually belong
      Rename PDFDoc::getSignatureWidgets to getSignatureFields, making it go
      through the FormsFields instead of the Page FormWidgets
      Remove the gotos from pdfsig code
      Add a few const here and there
      Fixes part of #895
  12. 21 Apr, 2020 1 commit
  13. 19 Apr, 2020 3 commits
  14. 18 Apr, 2020 1 commit
  15. 17 Apr, 2020 2 commits
  16. 16 Apr, 2020 1 commit
  17. 10 Apr, 2020 2 commits
    • Albert Astals Cid's avatar
      Update (C) of last commit · 9cf9356d
      Albert Astals Cid authored
    • Oliver Sander's avatar
      [arthur] Fix font hinting · 162fdf21
      Oliver Sander authored
      Previously, the ArthurOutputDev would always use the Qt default value
      for the QFont hinting preference.  At the same time, it contained
      a custom enum type with various hinting levels that didn't do anything
      at all.  This patch removes the custom enum, uses
      QFont::HintingPreference instead, and actually passes the chosen value
      to the font renderer.
  18. 08 Apr, 2020 1 commit
  19. 07 Apr, 2020 2 commits
  20. 06 Apr, 2020 1 commit
  21. 05 Apr, 2020 1 commit
    • Nelson Benítez León's avatar
      support 'de facto' tooltip feature · e4badf4d
      Nelson Benítez León authored
      Most pdf readers implement a tooltip feature by
      showing the string content of 'TU' field of a
      widget annotation that is not linked to any
      form field.
      Normally, widget annotations carry a reference to a
      form field which are used together to implement the
      different form widgets. But, the PDF spec does not
      forbid standalone (i.e. not linked to any form field)
      widget annotations, and the fact is they're been used
      by most pdf readers to show a tooltip when the area
      of that AnnotWidget is hovered.
      Some API added for this feature:
      bool FormField::isStandAlone()
      void FormField::setStandAlone (bool value)
      A standalone FormField means it's not part of Catalog's
      Field array, because of that we store them in a new
      member inside Page class:
      std::vector<FormField*> standaloneFields;
      and send them alongside the rest of FormWidgets in the
      existant API:
      FormPageWidgets *Page::getFormWidgets();
      Poppler issue #34
      Evince issue:
  22. 01 Apr, 2020 1 commit