Determine Line Break Scenario and Performance Improvements during PDF to HTML Conversion

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

As per regular monthly update process, we are pleased to announce Aspose.PDF for Java 18.4. New version of Aspose.PDF for Java API has been released and available on Aspose Artifactory for download and to be used in Java Projects. Like every release of Java API, we have ported features from .NET library of Aspose.PDF as well as made several bug fixes in Aspose.PDF for Java 18.4. Public API Changes are given in release notes page of Aspose.PDF for Java 18.4 and we recommend you to go through release notes of the API before using it.

Process Line Breaking

Some of our customers have requirements to determine the points/positions where an Enter/Line Break was added to create new line or contents of a line were moved to subsequent line, after content reaching to the edge of the page. We have implemented tracking background processing of multi-line text fragments in text adding scenarios. You can use getNotifications() method of Page Class, in order to log the line breaks. You may please check respective example in API documentation on following link, where code snippet for such functionality has been showcased:

We already have been planning to add features in our API regarding such scenarios, and we are working over providing support for these features in scenarios of manipulating existing PDF documents as well. We hope to provide more enhancements in API regarding this feature in upcoming versions. For now, only notifications about paragraph events in text adding scenarios are supported.

PDF to HTML Conversion Performance

Regarding performance of the API during PDF to HTML conversion, there were some issues reported for earlier versions of Aspose.PDF for Java. For some particular PDF documents (i.e. containing images and annotations), API was taking more time than expected in order to render them as HTML. However, we have improved API for such type of conversions and processing time is much reduced in Aspose.PDF for Java 18.4.

Along with the improvements and enhancements mentioned above, we have made following bug fixes in this release of API:

  • Cannot retrieve the watermark text of PDF
  • Security error on setting custom font directory
  • PDF to HTML: Header text is not been rendered correctly
  • PDF to HTML: Text rendered incorrectly
  • RedactArea corrupts the PDF if with setLicense method

Miscellaneous Fixes

As it is always recommended to use latest release of our API’s because they include latest features/improvements and fixes related to issues reported in earlier released versions. Therefore, please download the latest release of Aspose.PDF for Java 18.4.


To keep up with our news, you can follow us on Twitter or follow our Facebook page.