Aspose.Words for Java 25.11 Release Notes

Public API and Backward Incompatible Changes

This section lists public API changes that were introduced in Aspose.Words 25.11. 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 change default URL of the AI models

Related issue: WORDSNET-28735

A new public option has been added into Aspose.Words.AI.AiModel class:

/// <summary>
/// Gets or sets a URL of the model.
/// The default value is specific for the model.
/// </summary>
public abstract string Url { get; set; }

This use case explains how to change the default URL for AI model:

Added option to control timeout when requesting AI model

Related issue: WORDSNET-28726

A new public option has been added into Aspose.Words.AI.AiModel class:

/// <summary>
/// Gets or sets the number of milliseconds to wait before the request to AI model times out.
/// The default value is 100,000 milliseconds (100 seconds).
/// </summary>
public int Timeout { get; set; }

This use case explains how to change the default timeout for AI model:

Added ability to export OfficeMath into Markdown as LaTeX that is compatible with MarkItDown

Related issue: WORDSNET-28766

A new value has been added into Aspose.Words.Saving.MarkdownOfficeMathExportMode enumeration:

/// <summary>
/// Export OfficeMath as LaTeX that is compatible with MarkItDown.
/// </summary>
/// <remarks>Please see https://github.com/microsoft/markitdown for details on MarkItDown.</remarks>
MarkItDown = 4

This use case explains how to export OfficeMath into Markdown as LaTeX that is compatible with MarkItDown:

Added a callback interface to control page skipping when printing

Related issue: WORDSNET-28736

Introduced a new public property in Aspose.Words.Rendering.AsposeWordsPrintDocument class:

/// <summary>
/// Gets or sets the zero-based index filter used to determine which pages to skip during printing.
/// </summary>
/// <remarks>
/// Please note that if some pages are skipped, the actual total number of pages to print
/// will not be known until the printing process is complete.
/// This may impact print process tracking if the initial expected number of pages is greater
/// than the number actually printed.
/// </remarks>
public IIndexFilter PageIndexFilter { get; set; }

and a new public interface in Aspose.Words namespace:

/// <summary>
/// Defines a filter for skipping items based on their indices.
/// </summary>
public interface IIndexFilter
{
    /// <summary>
    /// Determines whether the item with the specified index should be skipped.
    /// </summary>
    /// <param name="index">The index of the item.</param>
    /// <returns><c>true</c> if the item should be skipped; otherwise, <c>false</c>.</returns>
    bool ShouldSkipIndex(int index);
}

AsposeWordsPrintDocument uses the standard .NET print manager through the PrinterSettings class, which only allows specifying a continuous page range for printing. However, there are scenarios where you need to skip specific pages based on their characteristics. This approach was developed to address such requirements.

The example below demonstrates simple filtering using a page number list, but in real-world applications, you can implement more specific filtering criteria - such as page size, orientation, or other page properties.

This use case shows sample filter implementation and usage:

Added public property to get the actual number of printed pages

Related issue: WORDSNET-28757

Introduced a new public property in [AsposeWordsPrintDocument](https://reference.aspose.com/words/net/aspose.words.rendering/asposewordsprintdocument/asposewordsprintdocument/ class:

/// <summary>
/// Gets the total number of pages actually printed during the print session.
/// </summary>
/// <remarks>
/// Updated after printing completes. Returns 0 before printing starts.
/// </remarks>
public int TotalPagesPrinted { get; }

This addresses scenarios where pages may be skipped during printing.

This use case shows printing with page filter:

Provided the ability to specify different printers to be used for color and black&white pages

Related issue: WORDSNET-24708

It is now possible to print color and black and white pages of a single document separately on different printers. This may be accomplished using a custom page index filter.

An example of printing color and black-and-white pages separately on different printers: