Aspose.Words for .NET 18.12 Release Notes

Major Features

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

• Implemented WMF fonts scaling, according to metafile size on the page, and public option to control it (MetafileRenderingOptions.ScaleWmfFontsToMetafileSize).
• Improved the default font fallback mechanism to better fit the MW behavior.
• Optimized metafile from SVG rendering to skip redundant line segments.
• Fixed a bug that caused an exception when rendering metafiles filled with gradient.
• Fixed a bug with the order of legend items of the stacked DrawingML chart when rendering.
• Fixed a bug with text clipping when rendering the DrawingML charts.
• Fixed a bug with rendering of minor tick marks and clipping the rightmost bar of DrawingML charts.
• Fixed a bug with rendering data labels for points, located on the border of the DrawingML chart plot area.
• Implemented support for RTL comments rendering, e.g. Arabic.
• Improved hyphenation logic for multiple cases.
• Improved page numbering for sections starting in new columns.
• Improved table row alignment.
• Improved tab stop calculations with paragraph indents.
• Improved table breaking logic for numerous complex cases.
• Improved handling of character compression within mixed ltr/rtl text.
• Fixed exception in rare case when field update causes line to contain only zero length spans.
• Fixed exception in rare case when floating object is pushed beyond empty column.
• Fixed layout when tables merge over the hidden paragraph.

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.12. 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.

hideMark Handling Changed to Match MS Word 2016 Behavior When Converting to Fixed-Page Formats

WORDSNET-17619 has been resolved.

A customer complained about differences between Aspose.Words pdf output and MS Word layout.

Upon analysis it turned out that Aspose.Words output matches MS Word behavior for older versions (up to MS Word 2013).

The customer expected the behavior to match MS Word 2016.

The difference is in handling how hideMark element in a table cell influences the cell height. In fact, the behavior that the customer complains about was introduced intentionally per several other JIRA issues submitted for other customers earlier.

Because of different hideMark handling, the cell height is different for a number of cases when invisible contents are present in the cell.

As the current policy is to emulate MS Word 2016 behavior, the changes will essentially roll back some special handling of the above cases when calculating table cell height in presence of hideMark.

The changes may be perceived as a breakage by customers still using MS Word versions before MS Word 2016.

MS Word 2016 Behavior Imitated for Some Special Cases with Continuous and “new column” Section Breaks

.WORDSNET-17760 has been resolved.

Aspose.Words behavior was changed to match MS Word 2016 for some situations with continuous and “new column” section breaks. The changes affect conversion to fixed-page formats. The behavior changed for computing page numbers and for providing of an empty facing page when adjacent pages have the same oddity.

It turned out that some of the implemented logic is different between MS Word 2016 and MS Word 2013. Because of that, the changes may look like a breakage if a user expects Aspose.Words behavior to match MS Word 2013 or an earlier version.

Added WMF Fonts Scaling According to Metafile Size on the Page and Public Option to Control it

New public property was added to MetafileRenderingOptions class:

/// <summary>
/// Gets or sets a value determining whether or not to scale fonts in WMF metafile according to metafile size on the page.
/// </summary>
/// <remarks>
/// When WMF metafiles are displayed in MS Word, fonts may be scaled according to actual metafile size on the page.
///
/// When this value is set to <c>true</c>, Aspose.Words emulates font scaling according to metafile size on the page.
///
/// When this value is set to <c>false</c>, Aspose.Words displays the fonts as metafile is rendered to its default size.
///
/// This option is used only when metafile is rendered as vector graphics.
///
/// The default value is <c>true</c>.
/// </remarks>
public bool ScaleWmfFontsToMetafileSize
{
    get;
    set;
}

Removed Obsolete Public API Method ‘SetAsDefault’ from LoadOptions.LanguagePreferences

WORDSNET-17294 has been resolved.

Removed obsolete public API method ‘SetAsDefault’ from LoadOptions.LanguagePreferences:

// Sets default editing language.
[Obsolete("Please use LanguagePreferences.DefaultEditingLanguage property instead.")]
public void SetAsDefault(EditingLanguage language)

Please use LanguagePreferences.DefaultEditingLanguage property instead: https://docs.aspose.com/words/net/aspose-words-for-net-18-6-release-notes/

Added a Public Property HtmlSaveOptions.ResolveFontNames

WORDSNET-17577 has been resolved.

A new option HtmlSaveOptions.ResolveFontNames has been added that affects writing of font names to HTML-based formats. By default this option is set to false and, as before, Aspose.Words writes font names as specified in the source document, ignoring Document.FontSettings. If this option is set to true, Aspose.Words resolves all font names before writing them to HTML. That is, it checks availability of each font using Document.FontSettings and substitutes unavailable fonts if needed.

Obsolete Property AllowTrailingWhitespaceForListItems was Removed from LoadOptions Class

Obsolete property AllowTrailingWhitespaceForListItems was removed from LoadOptions class.

Please, use TxtLoadOptions.DetectNumberingWithWhitespaces instead.