Skip to content

2025.1.1

Latest
Compare
Choose a tag to compare
@chaknith-ironsoftware chaknith-ironsoftware released this 15 Jan 09:18
914b6b8

IronPDF for Java v2025.1.1

Release Notes
New Features

  • New IronPdf.Native.UpdatedChrome packages for Linux and Windows based on the latest CEF 131.
  • Added new RenderHtmlAsPdfUA API.
  • Added new RenderZipFileAsPdf API overloads.

Enhancements

  • Improved overall PDF form operation performance.
  • Improved HTML Form Generation performance.
  • Improved PDF text extraction quality.
  • Update the engine to 2025.1.1

Bug Fixes

  • Fixed an issue where the RenderRazorViewToPdf() method caused compile errors after upgrading IronPdf from version 2024.8.3 to higher versions.
  • Fixed an issue where the ReplaceTextOnPage(), ReplaceTextOnPages(), ReplaceTextOnAllPages(), and DrawText() methods incorrectly rendered the newline character (\n) as ÿ instead of creating a new line.
  • Fixed an issue where converting some RTF files to PDF resulted in an exception due to unsupported elements within the RTF file.
  • Fixed an issue where the ReplaceText() method did not throw an exception when it failed to render text due to missing glyphs in embedded subset fonts.
  • Fixed an issue where internal hyperlinks were not working after applying password protection and other security settings to the PDF document.
  • Fixed an issue where the Line and TextChunk properties of the PdfPage object were not correctly detecting and displaying the number of lines and text chunks within the PDF page.
  • Fixed an issue where the DPI parameter in the PDF to image conversion methods was not being respected, resulting in images with incorrect DPI values.
  • Fixed an issue where the Flatten() method modified the dimensions of the PDF document and resulted in the cropping of content, particularly the header section.
  • Fixed an issue where HTML headers and footers were not displayed on PDF document pages after a background PDF was added.
  • Fixed an issue where certain Base64-encoded images interfered with UTF-8 encoding of content in headers and footers, while not affecting the main content.
  • Fixed an issue where setting a custom metadata key containing spaces (e.g., "My Custom Key") would throw an exception.