Browse our Products

Aspose.Words for Java 26.2 Release Notes

Major Features

There are 64 improvements and fixes in this regular monthly release. The most notable are:

  • Charts: Added the ability to set the orientation and rotation for both chart titles and axis titles.
  • Mathematical Equations: Improved the rendering of EQ-matrix (MathML) elements for higher visual fidelity.
  • Table Layout: Implemented the updated MS Word logic regarding the merging (or separation) of adjacent tables.
  • Metered Licensing: Updated Metered Billing Code for Java.

Full List of Issues Covering all Changes in this Release

Expand to view the full list of issues, reported by Java Users.
KeySummaryCategory
WORDSJAVA-3285Abort document save on image rendering failureNew Feature
WORDSJAVA-3266JAR signing mechanism refactoringNew Feature
WORDSJAVA-2930Update Java Metered CodeNew Feature
WORDSJAVA-3288Url to EULA is incorrect in POM fileBug
WORDSJAVA-3270New Gemini does not work with Aspose.Words.AIBug
WORDSJAVA-3268Change the exception thrown when using LoadFormat.PDFBug
WORDSJAVA-3263FipsUnapprovedOperationException is thrown upon conversion to MarkdownBug
WORDSJAVA-3250Aspose.Words for Java 25.12 lost images in the converted pdfBug
WORDSJAVA-3138Missed image with OpenJDK upon DOCX to PDFBug
Expand to view the full list of issues, reported by .NET Users.
KeySummaryCategory
WORDSNET-28864Provide a property to get/set secondary axis title rotation of chartNew Feature
WORDSNET-28146Imitate the new MS Word behavior when (not) merging adjacent tables with different tblLayout valueNew Feature
WORDSNET-6654HTML to Pdf conversion issue with the width of table’s cellNew Feature
WORDSNET-28980Consider downgrading Microsoft.Extensions.DependencyInjection dependency to 8.x version in .NET8 version of Aspose.WordsEnhancement
WORDSNET-28887Document table layout is wrong after renderingEnhancement
WORDSNET-28721Table layout is changed after renderingEnhancement
WORDSNET-25667Bar chart is rendered improperlyEnhancement
WORDSNET-28521MS Word detects 2 tables, while Aspose.Words detects only 1Bug
WORDSNET-28147DOCX to PDF: Incorrect table layout without UpdateTableLayout()Bug
WORDSNET-25902Part of text in table is truncated at right after rendering HTML documentBug
WORDSNET-25202Table width in landscape section header is incorrect after renderingBug
WORDSNET-24192DOCX to PDF: Table column width not re-calculatedBug
WORDSNET-23849Incorrect document layout upon renderingBug
WORDSNET-21885Incorrect table width on mhtml to PDF conversionBug
WORDSNET-21458Layout of the document is wrongBug
WORDSNET-20037Incorrect line break in the header of a saved PDFBug
WORDSNET-18462Content position is changed after conversion from HTML to PDFBug
WORDSNET-14250Cell’s text is rendered behind the image in output PDFBug
WORDSNET-10132Shapes are overlapped after conversion from Doc to PNGBug
WORDSNET-29036Line is incorrectly wrapped and justified when WordWrap is disabledBug
WORDSNET-29012Track changes are lost in dropdown content controls mapped to Custom XML when saving DOCXBug
WORDSNET-29008AW incorrectly calculates a space width if the space is adjacent to a tabBug
WORDSNET-28998FileCorruptedException is thrown upon loading DOCX documentBug
WORDSNET-28995Text is mixed up upon PDF to DOCX importBug
WORDSNET-28991Umlauts are lost after converting PDF to DOCXBug
WORDSNET-28986Header content representation changed after conversionBug
WORDSNET-28978NullReferenceException is thrown upon comparing documentsBug
WORDSNET-28965Misleading title of the “Open a Document Read-Only” articleBug
WORDSNET-28957Aspose.Words.LowCode.Merger.Merge: Object reference not set to an instance of an objectBug
WORDSNET-28954Numeral format is changed after rendering documentBug
WORDSNET-28945Table border is shown after renderingBug
WORDSNET-28928Hyphenation does not work for SerbianBug
WORDSNET-28921Line ends with ‘opposite’ trailing spaces wraps incorrectlyBug
WORDSNET-28917Setting the cursor before SDT raises an exceptionBug
WORDSNET-28874MathML is incorrectly imported from HTMLBug
WORDSNET-28870Corrupted document when exporting to Doc a cloned document in a multi-threaded modeBug
WORDSNET-28862ArgumentException is thrown upon rendering documentBug
WORDSNET-28823EQ field is rendered improperlyBug
WORDSNET-28787Text “General” appears insted values after converting to PDFBug
WORDSNET-28688EQ field is rendered improperlyBug
WORDSNET-24509The scale of cached XObject is not taken into account for PdfImageBug
WORDSNET-29026Document is truncated upon renderingBug
WORDSNET-28990Part of content moved to the next page after renderingBug
WORDSNET-28989Incorrect llayout when render to DOCXBug
WORDSNET-28985Artifacts upon rendering shapeBug
WORDSNET-28890Deffect in Windows 11 after renderingBug
WORDSNET-28660FontSubstitution adds a different font than expectedBug
WORDSNET-28390Incorrect table size after mergin the documentsBug
WORDSNET-24450Fill pattern shifted for DML shapes in comparison with MS WordBug
WORDSNET-24449The pattern fill is squeezed for VML shapesBug
WORDSNET-28967ArgumentException is thrown upon inserting mathmlBug
WORDSNET-28960EQ field is rendered improperly, enclosure character is not renderedBug
WORDSNET-28959EQ field is rendered improperly, overlayed content position is slightly incorrectBug
WORDSNET-28843EQ field is not rendered as expectedBug
WORDSNET-28842EQ field is rendered incorrectlyBug

Public API and Backward Incompatible Changes

This section lists public API changes that were introduced in Aspose.Words 26.2. 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.

Added ability to set orientation and rotation of chart title and axis title

Related issue: WORDSNET-28864

The properties Orientation and Rotation have been added to the ChartTitle and ChartAxisTitle classes:

public class ChartTitle
{
    ...

    /// <summary>
    /// Gets or sets the orientation of the chart title text.
    /// </summary>
    /// <remarks>
    /// The default value is <see cref="ShapeTextOrientation.Horizontal"/>.
    /// </remarks>
    public ShapeTextOrientation Orientation { get; set; }

    /// <summary>
    /// Gets or sets the rotation of the chart title in degrees.
    /// </summary>
    /// <remarks>
    /// The range of acceptable values is from -180 to 180 inclusive. The default value is 0.
    /// </remarks>
    public int Rotation { get; set; }
}

public class ChartAxisTitle
{
    ...

    /// <summary>
    /// Gets or sets the orientation of the axis title text.
    /// </summary>
    /// <remarks>
    /// The default value is <see cref="ShapeTextOrientation.Horizontal"/>.
    /// </remarks>
    public ShapeTextOrientation Orientation { get; set; }

    /// <summary>
    /// Gets or sets the rotation of the axis title in degrees.
    /// </summary>
    /// <remarks>
    /// The range of acceptable values is from -180 to 180 inclusive.
    /// </remarks>
    public int Rotation { get; set; }
}

This use case explains how to set orientation and rotation of chart title and axis title:

Consecutive tables with different tblLayout values are no longer merged

Per WORSNET-28521, Aspose.Words behavior was changed so that consecutive tables with different tblLayout property values are no longer merged into a single table.

In MS Word, there is some logic that merges consecutive tables with similar properties into a single table. This might significantly affect table layout. For a long time, MS Word had been merging consecutive tables with different tblLayout values into a single table. The behavior was changed fairly recently at some time around March or April 2025. Since then, MS Word does not merge consecutive tables with different tblLayout values. There were several customer requests to imitate the new behavior. AW behavior now matches the current MS Word behavior in this respect.

The change actually breaks the expected layout for a some of older customer requests, specifically WORDSNET-13434, WORDSNET-20814 and some others. But that should not be a problem since the same change had already happened with MS Word layout for documents in those requests.