Aspose.Words for C++ 20.2 Release Notes

Major Features

We have added the following features from Aspose.Words for .NET on this regular monthly release:

  • Elliptic Curve Digital Signature Algorithm (ECDSA) is supported now
  • Encrypted documents are supported now

Limitations and API Differences

Aspose.Words for C++ has some differences as compared to its equivalent .NET version of the API. This section contains information about all such functionality that is not available in the current release. The missing features will be added in future releases.

  • The current release does not support some cryptography features - it cannot verify and sign documents.
  • The current release does not support downloading remote resources from the Internet.
  • The current release does not support the Metered license.
  • The current release does not support a multipage TIFF format.
  • The current release does not support LINQ and Reporting features.
  • The current release has limited support for database features - C++ does not have a common API for DB like .NET System.Data.
  • The current release only supports Microsoft Visual C++ version 2015 or higher and only for the x64 platform.

Full List of Issues Covering all Changes in this Release

Key Summary Category
WORDSCPP-904 Add support for ECDSA signatures New Feature
WORDSNET-19750 Add features to support field formats when FieldMergingArgs.Text is used New Feature
WORDSNET-19556 Add feature to append VBA from one document to another using Document.AppendDocument New Feature
WORDSNET-18694 Add feature to export w:colFirst and w:colLast properties of bookmarkStart New Feature
WORDSCPP-737 Add support for encrypted documents Bug
WORDSCPP-920 Blank Page shows after Splitting the Page Bug
WORDSCPP-931 Loading DOC file throws FileCorruptedException exception Bug
WORDSNET-19773 Horizontal Line not Shown in Rendered Document Bug
WORDSNET-18592 After conversion to PDF, the content is not in the right place Bug
WORDSNET-11069 Shape’s strikethrough issues Bug
WORDSNET-18733 Chart Diagram rendered incorrectly in PDF Bug
WORDSNET-19783 System.NullReferenceException is thrown while saving the first page of the document to image Bug
WORDSNET-19800 System.NullReferenceException is thrown while saving DOC to PDF/PNG Bug
WORDSNET-19244 Different table width between DOCX and ODT Bug
WORDSNET-19461 Gridlines and images are missing when saving into HTML with HtmlFixedSaveOptions Bug
WORDSNET-14251 Table’s cells are lost after re-saving ODT Bug
WORDSNET-19710 Infinite loop during the call of Document.UpdatePageLayout Bug
WORDSNET-19712 Footer Banner Repeats Multiple Times on all Pages in PDF Bug
WORDSNET-19563 Lettered Bullet Points aren’t preserved when converting from ODT to DOCX Bug
WORDSNET-19257 DOCX to PDF conversion issue with watermark rendering Bug
WORDSNET-19900 Unable to load shared library ‘libSkiaSharp’ or one of its dependencies Bug
WORDSNET-19813 System.NullReferenceException occurs upon calling UpdateFields after UpdatePageLayout Bug
WORDSNET-19814 System.NullReferenceException occurs upon saving DOCX to PDF after calling UpdatePageLayout method Bug
WORDSNET-19129 Document.Compare throws System.ArgumentOutOfRangeException Bug
WORDSNET-19600 Order of fonts in the Font Substitution Table is incorrect Bug
WORDSNET-19819 System.NullReferenceException occurs upon calling UpdateFields after UpdatePageLayout Bug
WORDSNET-8967 Clipping inline shapes by line Bug
WORDSNET-19227 Table and Frame format is changed after saving .DOT as .ODT Bug
WORDSNET-19727 Footnote elements out of margins when saved to PDF Bug
WORDSNET-19734 Word to PDF tab alignment not working Bug
WORDSNET-19801 Aspose.Words.FileCorruptedException is thrown while loading DOC Bug
WORDSNET-19832 FileCorruptedException is thrown while loading RTF Bug
WORDSNET-19834 Content shifted when saved to PDF Bug
WORDSNET-19903 Incorrect naming of Document.AutomaticallyUpdateSyles param Bug
WORDSNET-19414 Inline image rendering order Bug
WORDSNET-19744 System.IndexOutOfRangeException occurs upon DOCX to PDF Conversion Bug
WORDSNET-19748 Table Cell Shading Lost during RTF to PDF Conversion Bug
WORDSNET-19749 Watermark angle changes during DOCX conversion Bug
WORDSNET-19803 System.ArgumentOutOfRangeException is thrown while saving document’s pages to PNG Bug
WORDSNET-19743 System.NullReferenceException occurs upon saving DOCX to PDF Bug
WORDSNET-19418 Memory is not released upon conversion document with EMF Bug
WORDSNET-19399 Setting PreserveFormFields to true cancels the effect of UpdateSdtContent Bug
WORDSNET-19916 Reset StructureDocumentTag content formatting on comparison Bug
WORDSNET-19534 Content in RTF is distorted Bug
WORDSNET-19533 Content in RTF is distorted Bug
WORDSNET-19779 Data labels are not rendered in PDF Bug
WORDSNET-19782 DOCX to PDF - hyphenation not same Bug
WORDSNET-19781 System.InvalidCastException is thrown while comparing documents Bug
WORDSNET-19785 Word to PDF dotted line problem Bug
WORDSNET-19789 Content pushed down from original position causing blank page at the end in PDF Bug
WORDSNET-19795 System.ArgumentOutOfRangeException occurs upon invoking Document.PageCount Bug
WORDSNET-14708 The content position is changed in output PDF Bug
WORDSNET-14961 Text is incorrectly positioned in RTL paragraphs inside auto-sized shapes Bug
WORDSNET-15064 DOCX  to PDF conversion issue with paragraph and shape position Bug
WORDSNET-14843 DOCX to PDF conversion issue with image’s position Bug
WORDSNET-14826 TextBox Shapes moved to next page during rendering to PDF Bug
WORDSNET-18880 The issue with table position and UpdateTableLayout method Bug

Public API and Backward Incompatible Changes

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

FieldMergingArgsBase.FieldValue made settable

Related issue: WORDSNET-19750

The customer was using the FieldMergingArgs.Text property and wanted the provided value to be formatted according to the format specified in the field being merged. We have made the FieldMergingArgsBase.FieldValue property settable so that instead of setting Text the user can set FieldValue which takes formatting into account instead of simply replacing the field.

/// <summary>
/// Gets or sets the value of the field from the data source.
/// </summary>
/// <remarks>
/// This property contains a value that has just been selected from your data source
/// for this field by the mail merge engine. You can also replace the value by setting the property.
/// </remarks>
public object FieldValue
    get { return mFieldValue; }
    set { mFieldValue = value; }

Word 2019 version set by default

Ref: WORDSNET-19908

Due to the fact that submissions to the support service regarding different default spacing values for the paragraph have become more frequent, it was decided to change the default version of MS Word. Now, this version is MSWordVersion.Word2019. In most cases, the issue appeared when the customers created documents in WPS Office that do not write default spacing values for the paragraph in a document to be saved. When opening such documents in Aspose.Words, the values actual for MSWord 2007 were substituted because it was the default version before this release.

Now the code:

Document doc = new Document("document.docx");

will be identical to:

LoadOptions lo = new LoadOptions();
lo.MswVersion = MsWordVersion.Word2019;
Document doc = new Document("document.docx", lo);

To achieve the previous behavior, it is necessary to explicitly specify the version:

LoadOptions lo = new LoadOptions();
lo.MswVersion = MsWordVersion.Word2007;
Document doc = new Document("document.docx", lo);