What?s new in this release?
The latest version of Aspose.Pdf for .NET (9.3.0) has been released. Aspose.Pdf for .NET is an award winning API. Over the years it helped developers with PDF document creation as well as manipulation. In every new release, the development team works really hard to introduce new features and fix issues to deliver a better version of the API. Dynamic forms are based on an XML specification known as XFA, the ?XML Forms Architecture?. The information about the form (as far as PDF is concerned) is very vague ? it specifies that fields exist, with properties, and JavaScript events, but does not specify any rendering. The contents of such forms are rendered during the PDF display process by respective viewer application. Due to this nature and structure of the forms, if we directly try to convert it to image format, nothing is rendered. Therefore, the forms have to be converted to Standard AcroForms first and then to image. Aspose.Pdf for .NET supports the feature to convert XFA forms to standard forms. In order to cater for this requirement, the values from an enumeration named FormType can be passed to the Document.Form.Type property. The Aspose.Pdf.Generator namespace makes it possible to create PDF files from scratch. During PDF creation, you might want to set document access privileges (restrictions). Similarly, the Aspose.Pdf.Facades namespace has offered the feature to set document access privileges to existing PDF documents for quite some time. Recently, we were asked to support a similar feature in the new Document Object Model of the Aspose.Pdf namespace, so that a single approach can be used to set access privileges when creating new documents or manipulating existing files. For further details, please visit the article in the documentation section about Set Privileges on an Existing PDF File. Adding layers to a PDF is a unique concept. It can be very useful for cases where you want to distribute multi-lingual file and want text in each language to appear on different layers, with the background design appearing on a separate layer. Aspose.Pdf for .NET 9.3.0 supports adding layers to PDF documents. Hyperlinks are added as LinkAnnotation in PDF files. Aspose.Pdf for .NET supports the feature to add a hyperlink to a PDF file, update links, and extract links. It can also get the destination URL of a LinkAnnotation (hyperlink) in PDF documents. We received a requirement for removing only the signature and keeping the signature field, so that the same field can be used to sign the document again and this feature is now available. Prior to the release of Aspose.Pdf for .NET 9.3.0, the API supported the feature to either save fonts as WOFF or TTF. Unfortunately this meant that fonts could not be loaded in Internet Explorer 6 through 8, so documents didn?t look right when viewed in these browsers. Also for mobile browsers, TTF fonts are required for maximum compatibility. So the solution was to generate 3 sets of fonts, to ensure maximum browser compatibility, and then reference all fonts in the CSS like as shown below. As well as the new features above, this new version includes fixes related to PDF to image conversion, saving PDF files in a particular PDF version, deleting images from PDF files, performance improvements when generating PDF files and much more. The list of important new and improved features are given below
- XFA document to static pdf document
- Use DocumentPrivilege to set encryption in DOM Encryption
- Adding Layer on existing PDF
- [HTML to PDF] Support Javascript code
- Getting PDF Hyperlink Destination (URL)
- Printer queue document name
- Identify Watermark Image from XImage collection
- To remove the signature and keep signature field
- Pdf file size increased after optimization
- Update DocumentPrivilege class to allow Page extraction
- Correct spelling mistakes in IfHtmlTagSupportedOverwrightHtmlFontNames property
- Resultant images should not be SVG is now fixed
- Generate 3 sets of fonts to ensure maximum browser compatibility
- How to break a nested table is enhanced
- To get submit button URL
- Pdf Producer field is showing incorrect product version
- Form field does not get filled
- Unable to retrieve form field names is now fixed
- Unable to use Aspose.Pdf for .NET when trust level for web application is defined is fixed
- Margins Issue is resolved in HTML2 PDF conversion
- output file still corrupted with 0kb of space
- Convert Pdf to HTML
- Add signature in PDF
- New line character/carriage return is ignored when clicked inside the text field.
- Extract text from PDF return garbage
- PDF Portfolio is now converted into Image format
- Extract text from PDF
- Application hangs during HTML to PDF conversion
- Border of RadioButton is not appearing in resultant PDF
- HTML to PDF - ordered list being rendered as an unordered list
- PDF - Save to HTML
- External CSS Issue in HTML to PDF conversion: CSS does not apply without specifying the full path is now fixed
- Invalid PDF/A 1b document
- Problem with Document.Encrypt is now fixed
- Generated PDF - [Summarize Comments] was disabled and fixed
- Removing a signature field after the document is signed corrupts any remaining signature fields
- Added watermark issue is resolved and now not visible
- Password protected file is throwing exception, created using Foxit PhantomPDF Printer.
- Time stamp issue, while signing a document with Aspose.Pdf.facdaes and - Aspose.Pdf.Kit is now fixed
- Image transparency issue is resolved on different OS
- Issue is fixed in adding image using operators
- Aspose Optimize function doesn't reduce the size is now fixed
- PDF to TIFF conversion is throwing ArgumentException
- FIPS compliance issue is resolved
- Text is now properly being extracted from PDF file
- PDFA_1a file is now properly generated
- PDF to TIFF conversion throws Exception while passing page size argument
- PdfFileEditor - merging the documents loses the form fields is now fixed
- Incorrect data display after importing data is now fixed
- The newly inserted page is very small size is now corrected
- TXT to PDF - Conversion process issue is resolved and now completed
- PDF to TIFF - Resultant image issue is resolved it was blank
- Submit button generates Expected a name object error
- HTML to PDF renders incorrect font size is now fixed
- Images are now being recognized in PDF file
- PDF to TIFF - Checkbox value is now being retained in TIFF
- PDF to PDF/A_1b conversion failure is fixed
- HTML to PDF - CSS is now properly referenced
- Extracting Annotation image appears as black rectangle and are fixed
- PDF to JPEG - Annotations are now appearing on resultant files
- PDF to HTML Fidelity Issue is fixed
- Unable to get exact text using coordinates is now fixed
- HTML to PDF - Unable to update Page dimensions is now fixed
- Insert page - First page was blank in resultant file and is fixed
Other most recent bug fixes are also included in this release.
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Pdf for .NET documentation that may guide you briefly how to use Aspose.Pdf for performing different tasks like the followings.
- Set Privileges on an Existing PDF File (Facades)
- Get PDF Hyperlink Destination (URL)
Overview: Aspose.Pdf for .NET
Aspose.Pdf is a .Net Pdf component for the creation and manipulation of Pdf documents without using Adobe Acrobat. Create PDF by API, XML templates & XSL-FO files. It supports form field creation, PDF compression options, table creation & manipulation, graph objects, extensive hyperlink functionality, extended security controls, custom font handling, add or remove bookmarks; TOC; attachments & annotations; import or export PDF form data and many more. Also convert HTML, XSL-FO and MS WORD to PDF.
More about Aspose.Pdf for .NET
- Homepage of Aspose.Pdf for .NET C#
- Online Demo for Aspose.Pdf for .NET
- Download Aspose.Pdf for .NET
- Read online documentation of Aspose.Pdf for .NET
Contact Information
Aspose Pty Ltd, Suite 163,
79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
The latest version of Aspose.Pdf for .NET (9.3.0) has been released. Aspose.Pdf for .NET is an award winning API. Over the years it helped developers with PDF document creation as well as manipulation. In every new release, the development team works really hard to introduce new features and fix issues to deliver a better version of the API. Dynamic forms are based on an XML specification known as XFA, the ?XML Forms Architecture?. The information about the form (as far as PDF is concerned) is very vague ? it specifies that fields exist, with properties, and JavaScript events, but does not specify any rendering. The contents of such forms are rendered during the PDF display process by respective viewer application. Due to this nature and structure of the forms, if we directly try to convert it to image format, nothing is rendered. Therefore, the forms have to be converted to Standard AcroForms first and then to image. Aspose.Pdf for .NET supports the feature to convert XFA forms to standard forms. In order to cater for this requirement, the values from an enumeration named FormType can be passed to the Document.Form.Type property. The Aspose.Pdf.Generator namespace makes it possible to create PDF files from scratch. During PDF creation, you might want to set document access privileges (restrictions). Similarly, the Aspose.Pdf.Facades namespace has offered the feature to set document access privileges to existing PDF documents for quite some time. Recently, we were asked to support a similar feature in the new Document Object Model of the Aspose.Pdf namespace, so that a single approach can be used to set access privileges when creating new documents or manipulating existing files. For further details, please visit the article in the documentation section about Set Privileges on an Existing PDF File. Adding layers to a PDF is a unique concept. It can be very useful for cases where you want to distribute multi-lingual file and want text in each language to appear on different layers, with the background design appearing on a separate layer. Aspose.Pdf for .NET 9.3.0 supports adding layers to PDF documents. Hyperlinks are added as LinkAnnotation in PDF files. Aspose.Pdf for .NET supports the feature to add a hyperlink to a PDF file, update links, and extract links. It can also get the destination URL of a LinkAnnotation (hyperlink) in PDF documents. We received a requirement for removing only the signature and keeping the signature field, so that the same field can be used to sign the document again and this feature is now available. Prior to the release of Aspose.Pdf for .NET 9.3.0, the API supported the feature to either save fonts as WOFF or TTF. Unfortunately this meant that fonts could not be loaded in Internet Explorer 6 through 8, so documents didn?t look right when viewed in these browsers. Also for mobile browsers, TTF fonts are required for maximum compatibility. So the solution was to generate 3 sets of fonts, to ensure maximum browser compatibility, and then reference all fonts in the CSS like as shown below. As well as the new features above, this new version includes fixes related to PDF to image conversion, saving PDF files in a particular PDF version, deleting images from PDF files, performance improvements when generating PDF files and much more. The list of important new and improved features are given below
- XFA document to static pdf document
- Use DocumentPrivilege to set encryption in DOM Encryption
- Adding Layer on existing PDF
- [HTML to PDF] Support Javascript code
- Getting PDF Hyperlink Destination (URL)
- Printer queue document name
- Identify Watermark Image from XImage collection
- To remove the signature and keep signature field
- Pdf file size increased after optimization
- Update DocumentPrivilege class to allow Page extraction
- Correct spelling mistakes in IfHtmlTagSupportedOverwrightHtmlFontNames property
- Resultant images should not be SVG is now fixed
- Generate 3 sets of fonts to ensure maximum browser compatibility
- How to break a nested table is enhanced
- To get submit button URL
- Pdf Producer field is showing incorrect product version
- Form field does not get filled
- Unable to retrieve form field names is now fixed
- Unable to use Aspose.Pdf for .NET when trust level for web application is defined is fixed
- Margins Issue is resolved in HTML2 PDF conversion
- output file still corrupted with 0kb of space
- Convert Pdf to HTML
- Add signature in PDF
- New line character/carriage return is ignored when clicked inside the text field.
- Extract text from PDF return garbage
- PDF Portfolio is now converted into Image format
- Extract text from PDF
- Application hangs during HTML to PDF conversion
- Border of RadioButton is not appearing in resultant PDF
- HTML to PDF - ordered list being rendered as an unordered list
- PDF - Save to HTML
- External CSS Issue in HTML to PDF conversion: CSS does not apply without specifying the full path is now fixed
- Invalid PDF/A 1b document
- Problem with Document.Encrypt is now fixed
- Generated PDF - [Summarize Comments] was disabled and fixed
- Removing a signature field after the document is signed corrupts any remaining signature fields
- Added watermark issue is resolved and now not visible
- Password protected file is throwing exception, created using Foxit PhantomPDF Printer.
- Time stamp issue, while signing a document with Aspose.Pdf.facdaes and - Aspose.Pdf.Kit is now fixed
- Image transparency issue is resolved on different OS
- Issue is fixed in adding image using operators
- Aspose Optimize function doesn't reduce the size is now fixed
- PDF to TIFF conversion is throwing ArgumentException
- FIPS compliance issue is resolved
- Text is now properly being extracted from PDF file
- PDFA_1a file is now properly generated
- PDF to TIFF conversion throws Exception while passing page size argument
- PdfFileEditor - merging the documents loses the form fields is now fixed
- Incorrect data display after importing data is now fixed
- The newly inserted page is very small size is now corrected
- TXT to PDF - Conversion process issue is resolved and now completed
- PDF to TIFF - Resultant image issue is resolved it was blank
- Submit button generates Expected a name object error
- HTML to PDF renders incorrect font size is now fixed
- Images are now being recognized in PDF file
- PDF to TIFF - Checkbox value is now being retained in TIFF
- PDF to PDF/A_1b conversion failure is fixed
- HTML to PDF - CSS is now properly referenced
- Extracting Annotation image appears as black rectangle and are fixed
- PDF to JPEG - Annotations are now appearing on resultant files
- PDF to HTML Fidelity Issue is fixed
- Unable to get exact text using coordinates is now fixed
- HTML to PDF - Unable to update Page dimensions is now fixed
- Insert page - First page was blank in resultant file and is fixed
Other most recent bug fixes are also included in this release.
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Pdf for .NET documentation that may guide you briefly how to use Aspose.Pdf for performing different tasks like the followings.
- Set Privileges on an Existing PDF File (Facades)
- Get PDF Hyperlink Destination (URL)
Overview: Aspose.Pdf for .NET
Aspose.Pdf is a .Net Pdf component for the creation and manipulation of Pdf documents without using Adobe Acrobat. Create PDF by API, XML templates & XSL-FO files. It supports form field creation, PDF compression options, table creation & manipulation, graph objects, extensive hyperlink functionality, extended security controls, custom font handling, add or remove bookmarks; TOC; attachments & annotations; import or export PDF form data and many more. Also convert HTML, XSL-FO and MS WORD to PDF.
More about Aspose.Pdf for .NET
- Homepage of Aspose.Pdf for .NET C#
- Online Demo for Aspose.Pdf for .NET
- Download Aspose.Pdf for .NET
- Read online documentation of Aspose.Pdf for .NET
Contact Information
Aspose Pty Ltd, Suite 163,
79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
