Aspose team is pleased to announce the release of Aspose.PDF for Java 18.4. Some of Aspose 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. It has implemented tracking background processing of multi-line text fragments in text adding scenarios. Users can use getNotifications() method of Page Class, in order to log the line breaks. Aspose team has already have been planning to add features in the API regarding such scenarios, and are working over providing support for these features in scenarios of manipulating existing PDF documents as well. Aspose team 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. 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, it has 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, this release has made some important bug fixes, such as 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 and RedactArea corrupts the PDF if with setLicense method.