Aspose.Words for Java 18.11 Release Notes

Major Features

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

• Aspose.Words for Java release jar is tested on Java 11.
• Compatibility with GroupDocs Total License is improved.
• GraphicsQualityOptions is better mapped to Java.
• We did yet another step to shrink (already small) pixel difference between .NET and Java generated images, borders, etc.
• JavaDoc for obsolette members become more clear.
• Fixed hang with autosized tables when cell has right aligned floaters.
• Fixed wrong visual order of text in specific cases.
• Fixed non-breaking space widths calculation.
• Implemented support for floating table metrics when calculating grid.
• ROP (raster operations) emulation code was improved, resulting in a significant performance boost (up to 5 times) when rendering the corresponding metafiles.
• Improved legacy vertical writing support in EMF rendering. Fonts with the ‘@’ prefix additionally rotate the Japanese glyphs.
• Improved calculation of the shape boundaries, more accurately mimicking the MS Word output.
• Improved the rendering of DrawingML charts canvases overlay. Markers of the “nofill” series are rendered on the foreground.
• Improved rendering of DrawingML chart axes for documents created using MS Word 2007.
• Fixed a bug with incorrect resolution of the system “window” color when rendering of VML shapes.
• Fixed an issue with underline/strikeout text effects in EMF/WMF rendering.
• Fixed a document rendering issue when font with English name could not be found in the system with a different locale.
• Fixed bug with rendering of DrawingML chart markers, if series data are not sorted in ascending order.
• Fixed a bug causing shifts of rotated shapes in DrawingML chart while rendering.
• Provided TxtSaveOptions.ExportHeadersFootersMode property.

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

Removing Colon between Empty MERGEFIELDs

WORDSNET-17386 has now been resolved.

A customer requested a feature supported by Word where you can surround a colon with two merge fields and if both fields are empty then it will also remove the colon. In fact, Aspose.Words removes a paragraph with merge fields if it becomes empty or contains only white-spaces after mail merge, which is controlled by the MailMergeCleanupOptions.RemoveEmptyParagraphs option. However, MS Word considers paragraphs with some non-white-space symbols (including colon) empty, while Aspose.Words did not prior to the fix.

We could just hard-code the new Aspose.Words behavior but did not want to introduce something that could be treated as a regression. Given that, we have added another option:

/// <summary>
/// Gets or sets a value indicating whether paragraphs with punctuation marks are considered as empty
/// and should be removed if the <see cref="MailMergeCleanupOptions.RemoveEmptyParagraphs"/> option is specified.
/// </summary>
/// <remarks>
/// The default value is <c>true</c>.
/// </remarks>
/// <remarks>
/// Here is the complete list of cleanable punctuation marks:
/// <list type="bullet">
/// <item><description>!</description></item>
/// <item><description>,</description></item>
/// <item><description>.</description></item>
/// <item><description>:</description></item>
/// <item><description>;</description></item>
/// <item><description>?</description></item>
/// <item><description>¡</description></item>
/// <item><description>¿</description></item>
/// </list>
/// </remarks>
public bool CleanupParagraphsWithPunctuationMarks
{
    get { return mCleanupParagraphsWithPunctuationMarks; }
    set { mCleanupParagraphsWithPunctuationMarks = value; }
}

The default value of the option is true which means that the behavior was changed to mimic MS Word; however, the customers who rely on the old behavior are able to revert it by setting the option to false.

The following sample demonstrates this case:

document.MailMerge.CleanupOptions = MailMergeCleanupOptions.RemoveEmptyParagraphs;
document.MailMerge.CleanupParagraphsWithPunctuationMarks = false;
document.MailMerge.Execute(new string[] {"field"}, new object[] {null});

Provide TxtSaveOptions.ExportHeadersFootersMode Property

 New public enum type was added:

// Specifies the way headers and footers are exported to plain text format.
public enum TxtExportHeadersFootersMode
{
    // No headers and footers are exported.
    None,

    // Only primary headers and footers are exported at the beginning and end of each section.
    PrimaryOnly,

    // All headers and footers are placed after all section bodies at the very end of a document.
    AllAtEnd
}

New public property was added to TxtSaveOptions class:

// Specifies the way headers and footers are exported to the plain text format.
public TxtExportHeadersFootersMode ExportHeadersFootersMode

The main advantage of new property over the old TxtSaveOptions.ExportHeadersFooters property is that it has new headers and footers export mode: ‘AllAtEnd’. In this mode Aspose.Words acts the way similar to MS Word: all headers and footers are placed after all section bodies at the very end of a document.

UC

Document doc = new Document ("inputFileName");
TxtSaveOptions options = new TxtSaveOptions();
options.SaveFormat = SaveFormat.Text;

// All headers and footers are placed at the very end of the output document.
options.ExportHeadersFootersMode = TxtExportHeadersFootersMode.AllAtEnd;
doc.Save("outputFileNameA.txt", options);

// Only primary headers and footers are exported at the beginning and end of each section.
options.ExportHeadersFootersMode = TxtExportHeadersFootersMode.PrimaryOnly;
doc.Save("outputFileNameB.txt", options);

// No headers and footers are exported.
options.ExportHeadersFootersMode = TxtExportHeadersFootersMode.None;
doc.Save("outputFileNameC.txt", options);

Obsolete Property ShowRevisionBalloons was Removed from RevisionOptions Class

Obsolete property ShowRevisionBalloons was removed from RevisionOptions class. Please use ShowInBalloons property instead.

Obsolete Property IsShowParagraphMarks was Removed from LayoutOptions Class

Obsolete property IsShowParagraphMarks was removed from LayoutOptions class. Please use ShowParagraphMarks property instead.

Obsolete Property IsShowHiddenText was Removed from LayoutOptions Class

Obsolete property IsShowHiddenText was removed from LayoutOptions class. Please use ShowHiddenText property instead.