Aspose.Words for Java 19.3 Release Notes

Major Features

• Release JAR is upgraded to JDK 7.
• Added feature to preserve the representation of legacy control characters while converting to OOXML formats.
• Added new public properties to the ChartAxis class.
• Added predefined font fallback settings for Google Noto fonts.
• Hyphenation logic improved.
• Fixed trailing spaces underlines in RTL paragraphs.
• Fixed issue with automatic frame width updates when the field is changed.
• Implemented invalid parameters filtering for shadow effect rendering.
• Improved rendering of the dashed compound lines for polygon shapes (except Bezier curves).
• Fixed rendering of EMF metafiles with unknow EmfPlusUnitType record.
• Fixed a bug preventing the VML line shapes to be rendered from bottom to top.
• Fixed a bug causing an exception while rendering the DML shape reflection effect.
• Fixed a bug that caused the image to be incorrectly positioned due to a bounding box calculation error while rendering.
• Fixed a bug with rendering DML Charts markers and data labels if the number of X-values is not equal to the number of Y-values.
• Fixed a bug with rendering of DML charts series with empty XValues.

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 19.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 existing behavior is especially important and is documented here.

Added feature to preserve the representation of legacy control characters while converting to OOXML formats

Related issue:WORDSNET-18081 has now been resolved.

New public property was added to the OoxmlSaveOptions class:

/// <summary>
/// Keeps original representation of legacy control characters.
/// </summary>
public bool KeepLegacyControlChars
{
    get { return mKeepLegacyControlChars; }
    set { mKeepLegacyControlChars = value; }
}

Some formats support legacy control characters. Word does not save these symbols to DOCX format (more accurately in OOXML formats). However, there is a customer request to preserve such control characters. Therefore the setting above was introduced. So far only one legacy character (ShortDateTime) is supported which declared in the “DOC” format.

Use Case:

Document doc = new Document("document.doc");
OoxmlSaveOptions so = new OoxmlSaveOptions(SaveFormat.FlatOpc);
so.KeepLegacyControlChars = true;
doc.Save("document.docx", so);

Added predefined font fallback settings for Google Noto fonts

Related issue:WORDSNET-17329 has now been resolved:

Added predefined font fallback settings for Google Noto fonts. These are free fonts licensed under SIL OFL. They can be downloaded from here.

public class FontFallbackSetting
{
    /// <summary>
    /// Loads predefined fallback settings which uses Google Noto fonts.
    /// </summary>
    public void LoadNotoFallbackSettings();
}

Note: Only Sans style Noto fonts with regular weight are used in the predefined settings.

Note: Some of the Noto fonts uses advanced typography features. Advanced typography is currently not supported by AW and these fonts may be rendered inaccurately.

Changed default value for TxtSaveOptions.AddBidiMarks property from ’true’ to ‘false’

Related issue:WORDSNET-17853 has now been resolved.

The default value for public property TxtSaveOptions.AddBidiMarks was changed from true to false:

/// <summary>
/// <para>Specifies whether to add bi-directional marks before each BiDi run when exporting in plain text format.</para>
/// <para>The default value is <b>false</b>.</para>
/// </summary>
public bool AddBidiMarks

This is now the same as the corresponding option in Word.

TxtSaveOptions.ListIndentation option is introduced that allows specifying how list levels are indented when exporting to a plain text format

Related issue:WORDSNET-17778 has now been resolved.

The following public class is introduced that allows to specify how list levels are indented when exporting to a plain text format:

/// <summary>
/// Specifies how list levels are indented when document is exporting to SaveFormat.Text format.
/// </summary>
public class TxtListIndentation

It has two public properties for specifying how many and which character to use for indentation of list levels:

/// <summary>
/// Gets or sets how many <see cref="Character"/> to use as indentation per one list level.
/// The default value is 0, that means no indentation.
/// </summary>
public int Count
/// <summary>
/// Gets or sets which character to use for indenting list levels.
/// The default value is '\0', that means there is no indentation.
/// </summary>
public char Character

At last, a new option is added to the TxtSaveOptions class:

/// <summary>
/// Gets a ListIndentation object that specifies how many and which character to use for indentation of list levels.
/// By default it is zero count of character '\0', that means no indentation.
/// </summary>
public TxtListIndentation ListIndentation

UseCase1: Use one tab character per level for list indentation:

Document doc = new Document("input_document");
TxtSaveOptions options = new TxtSaveOptions();
options.ListIndentation.Count = 1;
options.ListIndentation.Character = '\t';
doc.Save("output.txt", options);

UseCase2: Use three spaces indentation level for list indentation:

Document doc = new Document("input_document");
TxtSaveOptions options = new TxtSaveOptions();
options.ListIndentation.Count = 3;
options.ListIndentation.Character = ' ';
doc.Save("output.txt", options);

UseCase3: Do not use any list level indentation (default behavior):

Document doc1 = new Document("input_document");
doc1.Save("output1.txt");
Document doc2 = new Document("input_document");
TxtSaveOptions options = new TxtSaveOptions();
doc2.Save("output2.txt", options);

Provide API to change how text is vertically aligned within the Text Box

Related issue:WORDSNET-17996 has now been resolved.

Added new property for specifying vertical anchor of shape’s textbox.

/// <summary>
/// Specifies the vertical alignment of the text within a shape.
/// </summary>
/// <remarks>
/// <p>The default value is <see cref="TextBoxAnchor.Top"/>.</p>
/// </remarks>
public TextBoxAnchor VerticalAnchor
{
    get;
    set;
}

The property allows to specify text anchor within the shape(Top, Middle, Bottom).

Document doc = new Document(fileName);
Shape shape = doc.FirstSection.Body.Shapes[0];
shape.TextBox.VerticalAnchor = TextBoxAnchor.Middle;

Saving warnings will be thrown for unsupported formats (WordML) and for incompatible Word versions above 2007 (DOC, DOT).

Added public property ChartAxis.TickLabelAlignment

Related issue:WORDSNET-18146 has now been resolved.

The following new property has been added into the ChartAxis class:

/// <summary>
/// Gets or sets text alignment of axis tick labels.
/// </summary>
/// <remarks>
/// <para>This property has effect only for multi-line labels.</para>
/// <para>Default value is <see cref="ParagraphAlignment.Center"/>.</para>.
/// </remarks>
public ParagraphAlignment TickLabelAlignment
{
    get;
    set;
}

When axis tick labels are multi-line, MS Word aligns them to the center by default. The property allows for changing this behaviour.

UseCase:

Document doc = new Document(fileName);
Shape shape = (Shape)doc.GetChild(NodeType.Shape, 0, true);
ChartAxis axis = shape.Chart.AxisX;
axis.TickLabelAlignment = ParagraphAlignment.Right;