Convert Word Document to HTML Format by using Aspose.Words for SharePoint 18.12
We are really delighted to announce the release of version 18.12 of the Aspose.Words for SharePoint API. This release comes with some very exciting features to enhance the usability of the API. You can now convert Word document to HTML Format by using Aspose.Words for SharePoint 18.12. This version also sees the codebase better tweaked and the core functionality closer to Aspose.Words for .NET 18.12, which is the base product that Aspose.
Scale WMF Fonts to Match Metafile Size using Aspose.Words for Java 18.12
We are pleased to announce the new monthly release of Aspose.Words for Java 18.12. The release of this month contains a number of new features, enhancements and bug fixes of the issues reported by our users in previous versions. Please check the detailed release notes of Aspose.Words for Java 18.12 to get an idea about all the new features/enhancements and fixes made in this release. Furthermore, if you are planning to upgrade the API from any previous version, we strongly recommend you to check the Public API Changes section of current release and other intermediate releases from release notes folder, to know what has been changed since your current revision of the API.
Resolve Fonts According to FontSettings, WMF Fonts Scaling, and Mimic MS Word 2016 Behavior for Fixed-Page Formats
We are pleased to announce our next version Aspose.Words for .NET 18.12. This month’s release contains over 96 useful new features, enhancements and bug fixes. Please check the release notes to get an idea about all new features, enhancements and fixes made in this release. If you are planning to upgrade from older version of Aspose.Words to the current version, we would strongly suggest you to check the Public API and Backward Incompatible Changes section to know what APIs are changed so far.
SMART Uses Aspose.Words for .NET to Import and Split Word Documents into Sections Based on Heading Styles
About SMART At Smart Global Solutions, we help our clients to remain safety compliant through the use of our SMART Insight solution. A complete solution enabling businesses to adopt, monitor and improve a risk management strategy across its entire enterprise.
Problem As the process of importing and splitting the Word document was to occur on a website. The usual methods that would be employed on a Windows desktop environment could not be used.
Upgraded Aspose.Words for Reporting Services to Aspose.Words for .NET 18.10
We are pleased to announce new release of Aspose.Words for Reporting Services. We have upgraded this release to Aspose.Words for .NET 18.10. Please see the release notes for more detail. You can download the latest release of Aspose.Words for Reporting Services 18.10 from the following link:
Download Aspose.Words for Reporting Services 18.10
Aspose.Words for Reporting Services Resources The following resources will help you work with Aspose.Words for Reporting Services :
Export Word Document (DOC/DOCX) Headers Footers to Plain TXT File
We are pleased to announce the new monthly release of Aspose.Words for Java 18.11. The release of this month contains number of new features, enhancements and bug fixes of the issues reported by our users in previous versions. Please check the detailed release notes of Aspose.Words for Java 18.11 to get an idea about all the new features/enhancements and fixes made in this release. Furthermore, if you are planning to upgrade the API from any previous version, we strongly recommend you to check the Public API Changes section of current release and other intermediate releases from release notes folder, to know what has been changed since your current revision of the API.
Export Headers and Footers of Word Document to a TXT File using C#
We are pleased to announce our next version Aspose.Words for .NET 18.11. This month’s release contains over 69 useful new features, enhancements, and bug fixes. Please check the release notes to get an idea about all new features, enhancements, and fixes made in this release. If you are planning to upgrade from an older version of Aspose.Words to the current version, we would strongly suggest you to check the Public API and Backward Incompatible Changes section to know what APIs are changed so far.
Rename Packages from Aspose.Words JAR to Avoid Name Coincidence in Aspose.Words for JasperReports
We are pleased to announce new release of Aspose.Words for JasperReports. We have upgraded this release to the latest version of Aspose.Words for Java 18.10, rename packages from Aspose.Words JAR to avoid name coincidence, and fix an issue related to table. Please see the release notes for more detail. You can download the latest release of Aspose.Words for JasperReports 18.10 from the following link:
Download Aspose.Words for JasperReports 18.10
Starting from release 1.
Copy All Styles from Template and Insert Horizontal Rule in Word Documents
We are pleased to announce the new monthly release of Aspose.Words for Android via Java 18.10. Aspose.Words for Android via Java has full functionality of Aspose.Words for Java with few limitations, minor API changes and additional requirements. This version also includes all bug fixes and public API changes made in Aspose.Words for Java 18.10, see the following release notes for more information.
Aspose.Words for Java 18.10 release notes Aspose.Words for Android via Java 18.
Insert Horizontal Rule and Remove Empty Paragraphs in Word Documents using Java
We are pleased to announce the new monthly release of Aspose.Words for Java 18.10. The release of this month contains number of new features, enhancements and bug fixes of the issues reported by our users in previous versions. Please check the detailed release notes of Aspose.Words for Java 18.10 to get an idea about all the new features/enhancements and fixes made in this release. Furthermore, if you are planning to upgrade the API from any previous version, we strongly recommend you to check the Public API Changes section of current release and other intermediate releases from release notes folder, to know what has been changed since your current revision of the API.