PDF4NET 11.2.x
Released: Mar 29, 2022
Updates in 11.2.x
11.2.2
Updated May 30, 2022
Fixes
- PDF4NET
- Content cannot be extracted from some PDF files.
- Form fields are not saved correctly after appending a file with multi-level PDF fields.
- Font objects are not merged correctly in some situations.
- Damaged PDF file cannot be loaded.
- Page cannot be extracted if the declared number of pages in a document is different from the actual number of pages.
- Flow images are not laid out correctly in some scenarios.
- PDF4NET.Render
- Shadings with multiple functions are not rendered correctly.
- Gray images with chroma key mask are not rendered.
- Very large clip path causes image not to be displayed.
11.2.1
Updated Apr 29, 2022
Fixes
- PDF4NET
- Extracted page content with annotations is invalid if the original annotation appearances are invalid.
- Damaged PDF file cannot be loaded.
- Words cannot be extracted from PDF file.
- Textbox fields with multiple widgets are not flattened correctly with PdfFileEx class.
- PDF4NET.Render
- Some accented characters in Type1 fonts are not rendered correctly in some situations.
- Damaged PDF file is not rendered correctly.
- Text using KSC-EUC-H encoding is not rendered.
11.2.0
Updated Mar 29, 2022
Features
- PDF4NET
- Added low-overhead API for form filling and watermarking.
- Optimized resources for PDF merging.
- Added dedicated Microsoft .NET and '.NET-Windows' assemblies.
Fixes
- PDF4NET
- Extracted JPEG & JPEG2000 images are saved as RAW when save format is Native.
- Damaged PDF file enters infinite loop during save.
- UTF8 encoded strings in PDF objects are not decoded correctly.
- Some PDF dictionaries are not parsed correctly.
- PDF4NET.Render
- Stroked clipped path is not rendered correctly.
- Document with very large page size cannot be converted to multi-page TIFF.
- IndexOutOfRange exception is thrown when rendering a very large page.
- .NET Standard - Some extended ASCII characters are not rendered when the font is not embedded.