Skip to main content
Skip table of contents

Release iText 7.1.5

iText 7.1.5 is the fifth maintenance release for iText 7.1 Core/Community. We're also updating the add-ons pdfHTML to 2.1.2pdfCalligraph and pdfSweep to 2.0.3, and pdfXFA to 2.0.1

In total, about 50 tickets were closed, many of which were of significant complexity. 

iText Core/Community 7.1.5 for Java - for .NET

kernel

  • We can now also read MMType1 fonts (we treat them like regular Type1 fonts)
  • We now support 24bit and 8bit depth Transparent PNG images
  • A fix for a very rare yet stingy memory leak

layout

  • It is now possible to add a Link element to a Canvas
  • Improvements to Font parsing and resolving
  • Reported issues with character spacing and text chunk repositioning

sign

  • Fix security incident where our signature checker is too lenient. The CVE number for this vulnerability is pending.

svg

  • The much requested feature clipPath is now supported
  • Path operator improvements

Other modules

Small fixes for forms, pdfa, styled-xml-parser, and barcodes. Fixes in io are for pdfCalligraph

pdfHTML 2.1.2 for Java - for .NET


Features

  • support for SVG encoded in a data-uri
  • support for a table's caption element
  • support for border-radius on img tags
  • support for value in list items

Fixes

  • incorrect page-margin box dimensions calculation
  • bugs related to font providers, RTL, and property inheritance
  • "!important" CSS attribute ignores "display:none"

pdfCalligraph 2.0.3 for Java - for .NET

  • Fix for when GlyphLine content throws an exception if it contains an empty ActualText field
  • Thai mark combinations are now supported
  • Improved support for Hebrew table nesting

pdfSweep 2.0.3 for Java - for .NET

pdfSweep now supports redacting all annotation types

pdfXFA 2.0.1 for Java - for .NET

4 fixes for JavaScript evaluation problems (1 specifically for .NET)


Bugs:

New features

Tasks

Improvements


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.