Aspose.Words for Java 18.8 Release Notes

Major Features

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

• Java 10 tested and supported now
• New and updated Samples and Examples
• Change SHA-1 to SHA-256 and public asymmetric key from 1024 to 2048 for the license mechanism
• Implemented support for “underline trailing spaces” compatibility option
• Implemented support for paragraph alignment in Omath when inserted using EQ fields
• Enhanced computation of interscript spacing values based on TTF properties
• Improved wrapping of text around floating objects
• Improved calculation of position of floating tables and shapes
• Improved floater overlapping logic
• Improved computing of pages numbers in continuous sections which have restart attribute and conflicting oddity
• Fixed line justification issue when RTL span is at the end of the line
• Fixed issue with null dml properties
• Fixed issue with rendering of floating shapes in truncated headers/footers
• Fixed issue with rendering of lines inside of a field result when updated in truncated part of a cell
• Improved rendering of math operators in MathML objects
• Improved rendering of MathML objects with n-ary math element when n-ary character and limit location are not specified
• Fixed a bug with rendering of a math n-ary element if it is part of a fraction
• Fixed a bug when polyline with an arrow and a very small line segment at the end 
• was corrupted upon rendering
• Fixed a bug when an arrow pointer is incorrectly directed while rendering Bezier curves with arrows
• Fixed a bug where the end of the line was outside the “stealth arrow” when rendering
• LINQ Reporting Engine supports nested reports

Full List of Issues Covering all Changes in this Release

Public API and Backward Incompatible Changes

This section lists public API changes that were introduced in Aspose.Words 18.8. 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 a regression and modifies existing behavior is especially important and is documented here.

Nested Reports are Supported by LINQ Reporting Engine

WORDSNET-16817 has now been resolved.

The “Inserting Documents Dynamically” section of the engine’s documentation was updated to describe the change.

Added Feature to Create Snip Corner Rectangle

WORDSNET-13967 has been resolved:

The following shapes types were added to the “ShapeType” enum:

/// Snip single corner rectangle object.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
SingleCornerSnipped = 203,
/// <summary>
/// Snip same side corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
TopCornersSnipped = 204,
/// <summary>
/// Snip diagonal corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
DiagonalCornersSnipped = 205,
/// <summary>
/// Snip and round single corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
TopCornersOneRoundedOneSnipped = 206,
/// <summary>
/// Round single corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
SingleCornerRounded = 207,
/// <summary>
/// Round same side corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
TopCornersRounded = 208,
/// <summary>
/// Round diagonal corner rectangle.
/// </summary>
/// <remarks>
/// Applicable only for DML shapes.
/// </remarks>
DiagonalCornersRounded = 209

These shape types can not be used to create VML shapes. Attempt to create shape  by using public constructor of the “Shape” class raises the “NotSupportedException” exception. DML shape with one of specified above type can be created with “InsertShape” method of the document builder:

Document doc = new Document();
DocumentBuilder builder = new DocumentBuilder(doc);
Shape shape = builder.insertShape(ShapeType.TOP_CORNERS_SNIPPED, 50, 50);
OoxmlSaveOptions so = new OoxmlSaveOptions(SaveFormat.DOCX);
so.setCompliance(OoxmlCompliance.ISO_29500_2008_TRANSITIONAL);
doc.save("TopCornersSnipped.docx", so);

Reference Resources in MHTML Documents using the “Content-Id” URL Scheme.

WORDSNET-16985 has been resolved.

By default, resources in MHTML documents are referenced by file name (for example, “image.png”), which are matched against “Content-Location” headers of MIME parts. Now was added a new option to HtmlSaveOptions. This option enables an alternative method, where references to resource files are written as CID (Content-ID) URLs (for example, “cid:image.png”) and are matched against “Content-ID” headers.

public boolean ExportCidUrlsForMhtmlResources { get; set; }

Added Public Property ShowComments in LayoutOptions

WORDSNET-16986 has been resolved.

The following property has been added to the LayoutOptions class:

/// <summary>
/// Gets or sets indication of whether comments are rendered.
/// Default is True.
/// </summary>
public boolean ShowComments
{
   get; set;
}

This property is used to show\hide comments in the output document. By default, the comments are always shown.

Usage

Document doc = new Document(myDir + "Input.docx");
doc.getLayoutOptions().setShowComments(false);
doc.save(myDir + "Output.pdf");

Added Public Property ShowInBalloons in RevisionOptions

WORDSNET-16986 has been resolved.

The following property has been added to the RevisionOptions class:

/// <summary>
/// Allows to specify whether the revisions are rendered in the balloons.
/// Default value for this property is <see cref="Layout.ShowInBalloons.None"/>
/// </summary>
public ShowInBalloons ShowInBalloons
{
      get; set;
}

/// <summary>
/// Specifies which revisions are rendered in balloons.
/// </summary>
/// <remarks>
/// Note that these values do not affect rendering of comments, which are controlled by <see cref="LayoutOptions.ShowComments"/>.
/// </remarks>
public enum ShowInBalloons
{
     /// <summary>
     /// Renders insert, delete and format revisions inline.
     /// </summary>
     None,
     /// <summary>
     /// Renders insert and delete revisions inline, format revisions in balloons.
     /// </summary>
     Format,
     /// <summary>
     /// Renders insert revisions inline, delete and format revisions in balloons.
     /// </summary>
     FormatAndDelete,
}

This property is used to show revisions in the balloons. By default, the revisions in balloons are not shown.

Usage:

Document doc = new Document(myDir + "Input.docx");

// Renders insert and delete revisions inline, format revisions in balloons.
doc.getLayoutOptions().getRevisionOptions().setShowInBalloons(ShowInBalloons.FORMAT);
doc.save(myDir + "Output.pdf");

Or

Document doc = new Document(myDir + "Input.docx");

// Renders insert revisions inline, delete and format revisions in balloons.
doc.getLayoutOptions().getRevisionOptions().setShowInBalloons(ShowInBalloons.FORMAT_AND_DELETE);
doc.save(myDir + "Output.pdf");

Write all CSS Declarations of HtmlFixed Documents into Single File

WORDSNET-17089 has been resolved.

Previously, Aspose.Words saved “@font-face” rules of HtmlFixed documents into a separate file “fontFaces.css” while other CSS declarations were written to “styles.css”. We have changed this behavior and now Aspose.Words saves all CSS rules and declarations into the same file “styles.css”. In case the old behavior is required for compatibility with legacy code, it can be restored by using the new public property that we have added to the HtmlFixedSaveOptions class:

boolean SaveFontFaceCssSeparately { get; set; }

RtfLoadOptions class was extended

WORDSNET-17184 has been resolved.

A new LoadOptions class for dealing with RTF files was introduced : RtfLoadOptions.

New public property RecognizeUtf8Text was added into the RtfLoadOptions class:

/// <summary>
/// <para> When set to true, <see cref="CharsetDetector"/> will try to detect UTF8 characters,
/// they will be preserved during import.
/// </para>
/// Default value is false.
/// </summary>
public boolean RecognizeUtf8Text

This property allows to detect UTF-8 encoded characters and preserve them during import.

UC:

RtfLoadOptions loadOptions = new RtfLoadOptions();
loadOptions.setRecognizeUtf8Text(true);
Document doc = new Document(fileName, loadOptions);

Obsolete Member NumInDash was Removed from NumberStyle Enum

Obsolete value NumInDash was removed from NumberStyle enum. Please, use NumberStyle.NumberInDash value instead.

Obsolete Method ToTxt() was Removed from Node Class

Obsolete method ToTxt() was removed from Node class. Please, use ToString(SaveFormat.Text) instead.

Obsolete Property Location was Removed from FootnoteOptions and EndnoteOptions Classes

The obsolete property Location has been removed from the FootnoteOptions and EndnoteOptions classes. Please use the Position property. Also, the FootnoteLocation emum type has been removed.

Obsolete Property WarningCallback  was Removed from SaveOptions Class

Obsolete property WarningCallback  was removed from SaveOptions class. Please, use the Document.WarningCallback property instead.