Browse our Products
Aspose.Words for C++ 25.5 Release Notes
Major Features
There are 79 improvements and fixes in this regular monthly release. The most notable are:
- Chart Styling: Added the ability to set chart style.
- Markdown Export: Added the possibility to control how empty paragraphs are exported into Markdown.
Full List of Issues Covering all Changes in this Release
Expand to view the full list of reported issues.
- Consider providing an option to insert line break after every 76 characters in the base64 image representation
- Add an ability to set chart style
- Consider marking text box content with textbox tag
- Support of rendering Waterfall ChartEx
- Support MSO properties during import paragraphs
- Remove Microsoft.Win32.Registry dependency for .NET 6 and latter
- Default setting for ChartEx
- Support MSO properties during import text
- Allow using images as an input in LowCode classes
- Provide PdfSaveOptions.EnableHTTPCompression in API
- Linearization Property in PdfSaveOptions Class
- Page numbers in INDEX are incorrect if call update field once
- Page numbers in INDEX field are incorrect
- REF field value is not shown after updating fields
- Aspose.Words doesn’t write w:clear on page break w:br elements in DOCX documents
- MS Word doesn’t write w:equa Width attribute for w:cols element
- The output SVG document contains double id attribute in g element
- Improve text block detection upon importing PDF
- DOC to MD: Redundant empty lines in the output
- Background in WMF is rendered improperly
- Redundant font cloning
- Number of revision returned by Aspose.Words does not match MS Word
- Revision number returned by Aspose.Words does not match MS Word output
- Number of revision is incorrect
- Revision returned by Aspose.Words not match Word
- Aspose.Words returns number of revision which does not match MS Word
- Looks like revision count does not match the count provided by MS Word
- Wrong layout when converting particular RTF to PDF
- ArgumentOutOfRangeException when using regex replacing inside Run
- Text wrapping around floaters is incorrect when text contains NoBreakHyphen
- Line break differs between DOCX and PDF
- References are missing in TOC page reference when export to Markdown
- Multi-level category labels are rendered improperly
- NullReferenceException when converting 2nd page of input DOCS to fixed-HTML
- Implement better support for br HTML element
- Implement import of page breaks
- Trailing br elements are imported incorrectly from MsoHtml
- Implement import of breaks into correct paragraph
- Break elements are imported incorrectly from MsoHtml
- Add support for loading of native lists with more than 9 levels
- Text position is incorrect after rendering
- List numbering differs from MS Word’s result
- Importing of the lists differs from MS Word’s result
- Aspose.Words imports lists not like MS Word does
- List item importing looks different then from MS Word’s result
- List importing differs from MS Word’s result
- List item formatting differs from MS Word’s result
- When rendering a cloned APS tree, glyphs with the same font are not merged
- Add support for the “mso-outline-level” property of MsoHtml documents
- Apply ‘w:hint=“default”’ when loading ‘font-family’ into a character style formatting from MsoHtml
- Add support for the “mso-no-proof” property when loading MsoHtml
- Add support for the “supportLineBreakNewLine” HTML contitional expression feature when loading MsoHtml
- Font formatting is not applied to BR elements with the “page-break-before:always” style loaded from MsoHtml
- Aliases of built-in styles are imported incorrectly from MsoHtml
- Linked built-in styles are imported incorrectly from MsoHtml
- Justification is incorrect after rendering
- RTL text position is incorrect after rendering
- Number of revision returned by Aspose.Words does not match MS Word
- Wrapping in OfficeMath is incorrect after rendering
- Compare result does not match MS Word output
- Bookmark is lost after comparing documents
- Excessive rotations are caused by rendering textboxes inside table cells with rotated content
- br element with “clear” attribute is not imported as a text wrapping line break from MsoHtml
- Field code is rendered in the output
- Processing floater table before stretcher line in 2013 mode
- Page with Picture missing after Aspose.Words convert to PDF
- Image is lost in output
- Suppress extra line spacing the way WordPerfect 5.x does - incorrect line heights on conversion to PDF
- Content is invisible after rendering
- Hide properties for ImageWatermarkOptions and TextWatermarkOptions for WatermarkerContext
- DOCX to PDF: Charts description is not rendered correctly
- Missed comments for Processor.To(List
, SaveOptions) - FileCorruptedException is thrown upon loading DOCX document
- Content in SVG is lost
- InvalidOperationException is thrown when json value contains decimal dot
- HTML to PDF row height increased
- NullReferenceException is thrown upon calling UpdateFields
- Improve loading of style formatting when ‘mso-style-name’ references a built-in style
- NullReferenceException is thrown upon updating field in the document
Public API and Backward Incompatible Changes
This section lists public API changes that were introduced in Aspose.Words 25.5. 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 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 64-bit Intel Mac platform.