We are back with a major release of Aspose.PDF for .NET as v19.12 introducing the support of cross-references and hyperlinks when converting PDF to DOCX format. In addition, we have added the strategies for font subset optimization in the PDF documents. Not only this, but we have also provided important bug fixes for PDF to DOCX, PDF to HTML, PDF to TIFF, PDF to PNG, PDF to PPTX, SVG to PDF, and PCL to PDF conversions. So let’s have a look at the new features, enhancements, and bug fixes in a bit more detail.
Support of Cross-References and Hyperlinks – PDF to DOCX
Cross-references in documents are used to refer the reader to some other part or objects such as graphs, charts or figures in the document. The PDF format allows inserting the cross-references in the documents to navigate the user to the referenced content. Similarly, hyperlinks are also used to take the reader to a particular destination inside or outside the document.
Aspose.PDF for .NET supports converting PDF to Word (DOC, DOCX) formats, however, the previous versions of the API lacked the ability to support hyperlinks and cross-references in the converted Word document. This feature has now been added and the hyperlinks and cross-references are supported in the PDF to Word conversion.
Font Subsets Optimization in PDF
Aspose.PDF for .NET allows embedding fonts to the PDF documents. The font can be embedded completely or as a subset of the font. However, in some cases, you may want to optimize the fonts by reducing the fully embedded font set to only subsets that are used in the PDF document. In the latest release, we have provided the optimization options to tune the font subset strategies using the SubsetFonts method. This method accepts FontSubsetStrategy which has the following variants:
- SubsetAllFonts – This option will subset all the fonts that are used in the PDF document.
- SubsetEmbeddedFontsOnly – This option subsets only the fonts which are fully embedded into the PDF document.
The following C# code sample shows how to apply the font subset strategy to optimize the PDF documents.
Please visit this documentation article for more details on this feature.
The following is the list of some important bug fixes we have added to the latest release.
- PDF to Word – System.ArgumentNullException exception occurs
- PDF to Word – Hyperlink is lost
- PDF to PNG – Conversion issue
- PDF to HTML – Formatting issues in the resultant file
- PDF to HTML – Hyperlink is removed in the resultant file
- PDF to HTML – Text is not being rendered properly (character overwrite)
- TIFF to PDF – Images in PDF are blurred
- PDF to TIFF – Image conversion issue
- SVG to PDF – Conversion adds some random lines in output PDF
- SVG to PDF – Conversion renders the incorrect document
- SVG to PDF – Resultant PDF appears blank
- PCL to PDF – Resultant PDF document is missing the text
- PCL to PDF – Conversion throws SystemException
- PCL to PDF – An unhandled exception of type ‘ ‘ occurs
- PCL to PDF – Conversion fails
- PCL to PDF – Output PDF document is not correct
- PCL to PDF – Output PDF has wrong Fonts layout
- PCL to PDF – System.SystemException: ‘Font Line Printer is absent.’
- PCL to PDF – The method or operation is not implemented
- PDF to PPTX – Chart Labels are missing in output
- Cannot retrieve TextField Value
- Exception when saving EPUB to HTML
- Incorrect font used when viewing output HTML in Chrome
- NullReferenceException occurs when saving PDF
- Exception when loading a particular LaTeX (.tex) file
- Exception when accessing page annotations of PDF document with 3D object
For a complete list of bug fixes, please visit the release notes.
Alright! You can download the latest release of Aspose.PDF for .NET and check out the new features using the source code examples. Consult the documentation for more details about every feature along with the code samples. In case you would find anything difficult for you, please feel free to let us know via our forum.