Browse our Products

Aspose.Words for Java 26.5 Release Notes

Major Features

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

  • Digital Signing: Added the ability to configure various additional signing options.
  • Document Importing: Added support for importing nodes with expanded formatting options.
  • HTML Rendering: Added support for Far East vertical orientation in HTML within EQ fields.
  • Font Rendering: Improved the handling of AAT-enabled fonts when rendering to fixed-page formats.
  • Field Rendering: Improved the visual rendering of the EQ field’s frame.
  • Clear Caches: Added the ability to clear caches to prevent memory leak.
  • Update BouncyCastle Library: Update bc-fips library to 2.1.2 version.

Full List of Issues Covering all Changes in this Release

Expand to view the full list of issues, reported by Java Users.
KeySummaryCategory
WORDSJAVA-3346Added ability to clear cashesNew Feature
WORDSJAVA-3330Update bc-fips libraryNew Feature
WORDSJAVA-3304Document save internally throws java.lang.NumberFormatExceptionBug
WORDSJAVA-3167Increasing memory capacity when working with a documentBug
Expand to view the full list of issues, reported by .NET Users.
KeySummaryCategory
WORDSNET-24826Support MSO properties during import bordersNew Feature
WORDSNET-29146Added ability to import nodes with additional formatting optionsNew Feature
WORDSNET-29081Added ability to set various additional signing optionsNew Feature
WORDSNET-29177Structured document tags around table cells are not editable in PDFBug
WORDSNET-28385Incorrect page number in TOC after updating fieldsBug
WORDSNET-29241Table is not detectedBug
WORDSNET-29237Font formatting is imported incorrectly from MsoHtmlBug
WORDSNET-29222Radial SVG gradient is rendered incorrectlyBug
WORDSNET-29210InvalidOperationException is thrown when comparing documentsBug
WORDSNET-29209FileCorruptedException is thrown upon loading HTML when EncoderFallback.ExceptionFallback and DecoderFallback.ExceptionFallback are specifiedBug
WORDSNET-29206Content is moved to next page after renderingBug
WORDSNET-29205Part of content is moved to next page after renderingBug
WORDSNET-29204Part of content is moved to next pageBug
WORDSNET-29199Text in table cell is cropped after renderingBug
WORDSNET-29195Chinese text is wrapped improperly in table cellBug
WORDSNET-29193Bold Lato-Light text looks incorrectly after renderingBug
WORDSNET-29186The 9th page is rendered as completely blackBug
WORDSNET-29184Provide a property to check whether shape has any effects appliedBug
WORDSNET-29183Shape effects are lost when HtmlSaveOptions.ScaleImageToShapeSize is set to falseBug
WORDSNET-29173SVG image is not scaled properly upon exporting to HTMLBug
WORDSNET-29168Numbering is added to the paragraph after open/save ODTBug
WORDSNET-29157DOCX to PDF: images rendered as small fragments instead of full sizeBug
WORDSNET-29154ArgumentOutOfRangeException is thrown upon extracting pageBug
WORDSNET-29148Update plugin documentation on docs.aspose.net/wordsBug
WORDSNET-29112ExtractPages method improperly splits the pageBug
WORDSNET-28984Shape is lost after inserting document using with InsertDocumentInlineBug
WORDSNET-28977EQ field orientation is incorrect after converging to HTMLBug
WORDSNET-28958EQ field is rendered improperlyBug
WORDSNET-28911TOC child-level numbering mismatch after UpdateFields()Bug
WORDSNET-28881Memory leak upon cloning documentBug
WORDSNET-28692Documents compare result does not patch MS WordBug
WORDSNET-28397Missed page numbers upon PDF to DOCX conversionBug
WORDSNET-28386Text-level formatting changes after XML mapping with Track Changes enabledBug
WORDSNET-28328Attributes are not regenerated when absent during DOCX re-saveBug
WORDSNET-25539Compare documents produce different output than MS Word in listsBug
WORDSNET-25231Document comparison shows changes in unchanged documentsBug
WORDSNET-29203Line spacing of text formatted with Cambria math font is incorrect after renderingBug
WORDSNET-28817Table width is too thin after inserting from html into existing tableBug
WORDSNET-28558Merge field value is not expectedBug
WORDSNET-29181Part of content is moved to next pageBug

Public API and Backward Incompatible Changes

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

Added ability to import nodes with additional formatting options

Related issue: WORDSNET-29146

A new public overload has been added into Aspose.Words.DocumentBase class:

/// <summary>
/// <p>Imports a node from another document to the current document with an option to control formatting.</p>
/// </summary>
/// <remarks>
/// <p>This overload is useful to control how styles and list formatting are imported.</p>
/// </remarks>
/// <param name="srcNode">The node to imported.</param>
/// <param name="isImportChildren"><c>true</c> to import all child nodes recursively; otherwise, <c>false</c>.</param>
/// <param name="importFormatMode">Specifies how to merge style formatting that clashes.</param>
/// <param name="importFormatOptions">Allows to specify various additional formating options.</param>
public Node ImportNode(Node srcNode, bool isImportChildren, ImportFormatMode importFormatMode, ImportFormatOptions importFormatOptions)

Also added a new public option into Aspose.Words.ImportFormatOptions class:

/// <summary>
/// Gets or sets a boolean value that specifies whether to resolve theme colors of the shapes forcibly.
/// The default value is <c>false</c>.
/// </summary>
/// <remarks>
/// <para>
/// Please note that this option is only relevant for the <see cref="ImportFormatMode.KeepSourceFormatting"/> mode.
/// </para>
/// <para>
/// Normally, Aspose.Words doesn't resolve source theme colors when importing styles can be preserved
/// without expanding formatting attributes into direct ones. However, in this case the actual colors
/// of the imported shapes can differ from the ones they had in the original document. The reason for
/// this is the different theme colors in the source and destination documents. Setting this option
/// to <c>true</c> forces to resolve source shape theme colors and hence to preserve the actual
/// color of the shapes they have in the source document.
/// </para>
/// </remarks>
public bool ResolveThemeColors { get; set; }

This use case explains how to import nodes with expanding theme colors in shapes:

Added ability to set various additional signing options

Related issue: WORDSNET-29081

The new public properties have been added into Aspose.Words.DigitalSignatures.SignOptions class:

/// <summary>
/// Gets or sets the Windows version for the digital signature.
/// Default value is "6.1".
/// </summary>
public string WindowsVersion {get; set;}
/// <summary>
/// Gets or sets the application version for the digital signature.
/// Default value is "12.0".
/// </summary>
public string ApplicationVersion {get; set;}
/// <summary>
/// Gets or sets the Office version for the digital signature.
/// Default value is "12.0".
/// </summary>
public string OfficeVersion {get; set;}
/// <summary>
/// Gets or sets the horizontal resolution for the digital signature.
/// Default value is 1920.
/// </summary>
public int HorizontalResolution {get; set;}
/// <summary>
/// Gets or sets the vertical resolution for the digital signature.
/// Default value is 1200.
/// </summary>
public int VerticalResolution {get; set;}
/// <summary>
/// Gets or sets the color depth for the digital signature.
/// Default value is 32.
/// </summary>
public int ColorDepth {get; set;}

Also added new public options into Aspose.Words.DigitalSignatures.DigitalSignature class:

/// <summary>
/// Gets the Windows version for the digital signature.
/// </summary>
public string WindowsVersion {get;}
/// <summary>
/// Gets the application version for the digital signature.
/// </summary>
public string ApplicationVersion {get;}
/// <summary>
/// Gets the Office version for the digital signature.
/// </summary>
public string OfficeVersion {get;}
/// <summary>
/// Gets the horizontal resolution for the digital signature.
/// </summary>
public int HorizontalResolution {get;}
/// <summary>
/// Gets the vertical resolution for the digital signature.
/// </summary>
public int VerticalResolution {get;}
/// <summary>
/// Gets the color depth for the digital signature.
/// </summary>
public int ColorDepth {get;}

This use case explains how to set additional signing options:

Added ability to clear cashes

Related issue: WORDSJAVA-3346, WORDSJAVA-3167

A new public method has been added into Aspose.Words.Document class:

/// <summary>
/// Clears all cached variables and releases memory.
/// </summary>
/// <remarks>
/// <p>This method resets all lazily-initialized caches and facade objects to null,
/// allowing their memory to be reclaimed by the garbage collector.</p>
/// <p>After calling this method, cached objects will be recreated on next access as needed.</p>
/// </remarks>
public void ClearCaches()