All Versions
79
Latest Version
Avg Release Cycle
92 days
Latest Release
-

Changelog History
Page 1

  • v1.0.22 Changes

    🛠 Fix: fix fonts dereferencing issue (#203), credit to @MarcWeber (Marc Weber) for identifying the issue.

    🛠 Fix: fix metrix dependency, credit to @casperisfine (Jean byroot Boussier) for PR #195.

  • v1.0.21 Changes

    🛠 Fix: possible fix for issue #184, where nested PDF files within an object stream could break the parser. Credit to Greg Sparrow (@hazelsparrow) for exposng the issue.

  • v1.0.20 Changes

    December 07, 2020

    🛠 Fix: merges PR #180, TypeError: can't dup NilClass. Credit to Adam Trepanier (@adam-e-trepanier) for the merge.

  • v1.0.19 Changes

    October 23, 2020

    🛠 Fix: fixes font height and width detection issue. Issue #179. Credit to @5anchezzz for opening the issue.

    🛠 Fix: fixes an indentation warning. Issue #173. Credit to @rubyFeedback for exposing this issue.

  • v1.0.18 Changes

    July 20, 2020

    🛠 Fix: fixed issue with the 1.0.17 release where ProcSet PDF Arrays should have been expected but where ignored and a PDF Object was assumed instead (issue #171) - credit to @chuchiperriman (Jesús Barbero Rodríguez).

  • v1.0.17 Changes

    July 17, 2020

    💎 NB: yanked from RubyGems.org.

    🛠 Fix: fixed issue where nested structure equality tests might provide false positives, resulting in lost data (issue #166) - credit to @cschilbe (Conrad Schilbe).

  • v1.0.16 Changes

    February 22, 2019

    🛠 Fix: some documentation typos were fixed (PR #147) - credit to @djhopper01 (Derek Hopper).

  • v1.0.15 Changes

    August 12, 2018

    🛠 Fix: An attempt to fix JRuby compatibility concerns (issue #127).

  • v1.0.14 Changes

    July 17, 2018

    🛠 Fix: Fixed an issue related to PDF XRef table data, where a malformed EOL marker would cause the parser to fail. Credit to @dangerous (David Rainsford) for exposing this issue in a comment to issue #140.

  • v1.0.13 Changes

    July 11, 2018

    🛠 Fix: Fixed an issue related to PDF object streams (version 1.6) where a numerical object at the beginning of the stream might be mis-parsed as an object reference number rather than an object. Credit to @Defoncesko for reporting issue #141.