Pdfkit update exciting pdf8/10/2023 Along with that, it has also made some fixes to the bugs, reported in earlier versions of the API. This new release has introduced new features related to text manipulations and PDF/UA validation. Other most recent bug fixes are also included in this release.Īspose team is very excited to announce the new version of Aspose.PDF for. PDF to PDFA1b conversion results in-compliant PDFA document.When PDF is converted to DOCX, the text is missing.(converted to image).For Helvetica and Courier fonts, page number in the TOC entry is missing.When PDF is converted to PDF_A_1B, the text looks different.Stamp looks incorrect when size and rotate angle are set.Failed to validate PDF_X_3 and PDF_X_1A.PDF to PDFA conversion performance issue.Exception thrown when trying to get the names of the fields in a form.Exception when trying to get signature names.Exception when trying to load PDF document.ArgumentException is thrown when trying to get artifact text.NullReferenceException is thrown when trying to get artifact text. Create separate local links for duplicate text.The flattened file from XFA form cannot be opened in Chrome or Firefox.The list of important new and improved features are given below Also please note that with this change, the size of product binaries will also be reduced. This change may impact some customers who haven’t yet migrated their code from legacy to new DOM approach, but Aspose team is always delighted to help Aspose customers and would love to facilitate them regarding their migration towards new DOM. Nevertheless, the new DOM approach contains all the features offered by legacy. NET 17.5, Aspose team is going to discontinue namespace from API. So in order to minimize / eliminate the confusion of customers to stumbled upon between legacy and new Aspose.Pdf namespace, starting next release of Aspose.Pdf for. But the new DOM approach of Aspose.Pdf namespace facilitates the creation of PDF files from scratch as well as manipulation of existing PDF files. NET provided the functionality to manipulate existing PDF files. The legacy only provided the capabilities to create PDF documents from scratch and legacy for. NET under namespace and a new Document Object Model for PDF files creation as well as manipulation under Aspose.Pdf namespace. NET under namespace, the Classes and Enumerations of legacy for. NET 6.0 in July-2011, it has included the Classes and Enumerations from legacy Aspose.Pdf for. Ever since the release of the first MergedAPI version of Aspose.Pdf for. Furthermore, the PDF file conversion to other supported file formats is also improved. However in this release, Aspose team has specifically improved the Text extraction feature and many of the customers reported issues related to this feature have been fixed in this release version. This API is also amazing in Text manipulation, whether its Text Addition, Text extraction, Text Search or Text replacement. Therefore in this new release, Aspose team has made improvements in PDF to PDF/A conversion feature to cater more customers scenarios and to handle documents with different structure and complexity. Keeping same aspects of stability and reliability in mind, with every new release, Aspose team are introducing some exciting new features as well as strive to bring more stability to existing features of API. Therefore apart from standard desktop versions of Windows, it is equally supported on Server editions of Windows and users can use it in Desktop and Web Enterprise Applications. NET is widely being used by many customers and trusted name due to its robustness and reliability on various platforms. It has specifically focused towards stability of existing features for PDF files creation as well as manipulation. Aspose team is pleased to announce the release of Aspose.Pdf for.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |