Browse our Products
Aspose.Words for C++ 25.7 Release Notes
Major Features
There are 68 improvements and fixes in this regular monthly release. The most notable are:
- AI Features: Added the ability to use self-hosted LLM implementations, allowing for greater privacy and control over AI-driven features.
- Replacing: Introduced the ReplacingArgs.MatchEndNode public property to provide developers with more precise control during text replacement operations.
- Table Management: Added the Row.Hidden public property, enabling the ability to programmatically show or hide specific rows within a table.
- Font Rendering: Implemented initial support for OpenType Font Variations, allowing for richer and more flexible typographic display.
Full List of Issues Covering all Changes in this Release
Expand to view the full list of reported issues.
- Add public API to mark row as hidden
- Support XLSX header/footers in XLSX export
- Allow to use self-hosted LLM implementation in Aspose.Words
- Consider providing a property in ReplacingArgs that will return the node that contains the end of the match
- Table left indent is incorrect after rendering
- Consider Dropping Client Profile Support for Aspose.Words .NET 3.5 and 4.0
- MS Word doesn’t write ‘w:space’ attribute for last ‘w:col’ element
- System.NullReferenceException when comparing documents
- StackOverflowException during DOCX to PDF conversion when PreserveFormFields is enabled
- StackOverflowException is thrown upon rendering document to PDF with PdfSaveOptions.PreserveFormFields enabled
- Stack overflow when converting DOCX to PDF
- List item formatting is changed after open/save ODT
- Setting TableStyle.Bidi makes the table LTR
- Unexpected Bookmark Creation When Mapping Identical Content Controls to the Same Custom XML Part
- Fix warnings during conversion
- Aspose.Words hangs during rendering to PDF
- Infinite loop upon conversion to PDF
- Rendering process hangs upon converting document
- Aspose.Words hangs upon rendering document with hyphenation
- Aspose.Words hangs upon rendering document when hyphenation dictionary is specified
- UpdatePageLayout hangs upon conversion
- Hangs upon rendering document
- Aspose.Words hangs upon rendering document
- Rendering hangs upon conversion
- EmbeddedFontCache throws ArgumentNullException in AOT config
- Changing the “SelectedValue” on ListItems collection does not create a revision
- Incorrect date header rendering in PDF output
- Chart is rendered as not filled with data
- Text wrapped incorrectly due to inaccurate shrinking of Courier New spaces
- “Asian typography/Allow Latin text to wrap in the middle of a word” option is ignored upon rendering
- MS Excel raises an error when opening output XLSX
- Incorrect content area width for non-rectangular DML shapes
- Text misalignment upon SVG rendering
- Investigation: InsertHtml to SDT: Content not inserted
- Aspose.Words.LowCode.Merger throws an XmlException
- Track changes are lost in dropdown content controls mapped to Custom XML when saving DOCX
- Building document layout of document with batch of inline images is slow
- List levels formatting in the document produced by MS Word differs from what AW generates
- Formatting of list levels in the document produced by MS Word differs
- Import of MsoHtml columns differs from MS Word’s result
- Mismatch in Column Import from MsoHtml vs. MS Word
- Inconsistent Column Rendering: MsoHtml Import vs. Word
- MsoHtml Column Import Produces Different Results than Word
- Discrepancy in Column Layout Between MsoHtml and MS Word Import
- Line break between text and shape is lost after extracting page
- DOCX to EPUB: Image not rendered correctly
- DOCX to MD: Links not working in output
- Code example for WarningInfoCollection is incorrect
- Import of MsoHtml lists differs from MS Word’s result
- Discrepancy in Column Layout Between MsoHtml and MS Word Import
- MsoHtml Column Import Produces Different Results than Word
- Inconsistent Column Rendering: MsoHtml Import vs. Word
- Mismatch in Column Import from MsoHtml vs. MS Word
- Add support for loading of lists from headers/footers
- Shaped text isn’t rendered correctly if text has borders
- Table row on a different page on conversion to PDF
- Part of content is moved to next page
- Size of single line legend
- Exception when saving a document in another thread after ExtractPages
- Layout of legend entries
- Y-axis labels are shifter and partially cut off
- Table layout is broken after removing SDTs
- Aspose.Words converting vs and MS Word converting
- Image is inserted upside-down when setting fill image
- Duplicated table content upon DOCX to PDF conversion
- Paragraph alignment is changed after appending document
- LST to DOC: Incorrect indentation and Blank pages added
- Words count in the document with custom list labels is incorrect
Public API and Backward Incompatible Changes
This section lists public API changes introduced in Aspose.Words 25.7. It includes not only new and obsoleted public methods, but also a description of any changes in the behavior behind the scenes in Aspose.Words which may affect existing code. Any behavior introduced that could be seen as regression and modifies the existing behavior is especially important and is documented here.
Limitations and API Differences
Aspose.Words for C++ has some differences as compared to its equivalent .NET version of the API. This section contains information about all such functionality that is not available in the current release. The missing features will be added in future releases.
- The current release does not support Metered license.
- The current release does not support LINQ and Reporting features.
- The current release does not support OpenGL 3D Shapes rendering.
- The current release does not support loading PDF documents.
- The current release has limited support for database features. C++ doesn’t have a common API for DB like .NET System.Data.
- The current release supports Microsoft Visual C++ version 2019 or higher.
- The current release supports Clang 3.9.1 or higher on Linux and only for the x86_x64 platform.
- The current release supports macOS Monterey or later (12.0+) for the 64-bit Intel Mac platform.