v0.9.6

Breaking Changes

• Move #suppress_warnings to a namespaced Module by @MatheusRich in #37
• Move constants out of global namespace by @MatheusRich in #38

v0.9.5.2

Change the path for temporary files to use the OS default.

Previously, all temporary files would be briefly created within the same directory as the original PDF file and destroyed shortly after. This did not work on read-only file systems, such as the ones provided by AWS lambda. Now all temporary files are stored in a directory that is defined by the operating system, which is writeable in AWS Lambda.

v0.9.5.1

Fixed an issue with incorrect or blank checkbox appearances.

In a previous commit, iText's generateAppearance field was set to true for all fields except checkboxes in order to enable custom checkboxes to show correctly. However, this had unintended consequences for some developers where checkboxes with the default appearance were completely blank.

In order to work correctly with both custom checkboxes (such as square, circle, diamond, or other) and default checkboxes, developers can now set generate_appearance themselves to whatever suits their type of PDF file.

Breaking Changes

• When using set_fields, you now must include braces {} when passing a hash of key/value pairs.
• generate_appearance is no longer set to true by default. You may now need to manually set it to true or false if your form fields are not displaying correctly. See the documentation for set_field and set_fields methods, as well as the Troubleshooting Issues section for more information.

v0.9.5

Fixed a bug that changed a checkbox's appearance when checked.

Using iText's setValue function for PdfFormField without a second parameter would automatically set the boolean generateAppearance to true, thus changing all checkboxes - be they a check, a circle, a diamond, or other - to a cross. By setting generateAppearance to false for PdfButtonFormField fields only, the checkbox appearance will remain unchanged.

v0.9.4

• Upgraded iText binaries to v.7.2.3.
• Bumped the rjb gem to latest version.
• Updated documentation to indicate JDK requirements.

v0.9.3

Added support for images in signature/image fields.

Whether a signature field expects a digital signature or a text signature, an image can now be added into that field from a file or a base64 encoded string. In fact, adding images works for any field, and the image will always overwrite whatever was in the field while automatically resizing to fill the bounds.

v0.9.2

• Fixed an issue that caused an IllegalArgumentException when passing an instance of Pathname instead of a string to FillablePDF.new.
• Upgraded iText and SLF4J JAR file dependencies to latest versions.
• Downgraded the rjb gem dependency to a latest stable version, as rjb versions 1.6.3 and 1.6.4 currently cause crashes on macOS 10.13.6 (High Sierra) and 12.0.1 (Monterey).

v0.9.1

• Fixed an issue where with File.rename, which can error out with "Invalid cross-device link @ rb_file_s_rename" in e.g. Docker containers (thanks @xxx).
• UUpgraded iText and SLF4J JAR file dependencies to latest versions.

v0.8.0

• Added support for Asian fonts (thanks @tombroomfield).
• Added the ability to close PDF documents to prevent memory leaks.
• Improved error handling when opening invalid or incompatible PDF documents.

v0.7.1

• Upgraded from iText 5 to iText 7.
• Added smarter error checking for common issues, such as using a non-existent PDF file or a non-existent field name within a PDF.
• Modified several core method names (breaking change!).
• Added automated tests using minitest.
• Added Travic CI support.