Skip to end of metadata
Go to start of metadata

This page contains release notes for Aspose.Words for .NET 17.2.0

Major Features

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

  • Export fonts to HTML in Base64 encoding
  • Added HtmlSaveOptions.ResourceFolder and HtmlSaveOptions.ResourceFolderAlias public properties
  • Exposed access to Height/Width of Text Frames
  • Improved control over BiDi text direction elements
  • Non-bidi fields that contain hided bidi whitespaces are properly resolved

Full List of Issues Covering all Changes in this Release

Key

Summary

Category

WORDSNET-12975

Math equation's alignment is changed in output Pdf

Bug

WORDSNET-13516

Document.Compare returns incorrect revisions

Bug

WORDSNET-13568

Left indentation of list items is incorrect in generated ODT

Bug

WORDSNET-13719

pic:pic element is not written during RTF to DOCX conversion

Bug

WORDSNET-13993

Cell's background-colors is not correct in output Html/Docx/Pdf

Bug

WORDSNET-14008

Footnote line renders higher in PDF

Bug

WORDSNET-14076

/hidden cell break/ When Converted To PDF, text in output file is not on same page like in original Word document.

Bug

WORDSNET-14393

Page break is lost after re-saving WordML document

Bug

WORDSNET-14464

Attributes related to FitText are improperly read into the model of the .DOC document.

Bug

WORDSNET-14481

Docx to Pdf conversion issue with TOC item rendering

Bug

WORDSNET-14537

Single Solid-line in word document converts double border for the images in HTML

Bug

WORDSNET-14553

Docx to HtmlFixed conversion issue with table's borders

Bug

WORDSNET-14595

StyleCollection.addCopy - Breaking the Multi Level List numbering for Heading styles

Bug

WORDSNET-14606

A text overlaps on top left logo image in PDF

Bug

WORDSNET-14654

Extra TOC entry is rendered in output Pdf

Bug

WORDSNET-14670

Bookmark missing after open and resave document using Aspose.Words

Bug

WORDSNET-14674

Header contents are lost after conversion from Docx to Pdf

Bug

WORDSNET-14676

Docx to Pdf conversion issue with hyperlinks

Bug

WORDSNET-14678

When DOCX is saved as PDF by using a FileStream or MemoryStream, then the output document is missing some elements.

Bug

WORDSNET-14684

Position of SmartArt elements are changed in output Pdf

Bug

WORDSNET-14685

Docx to Pdf conversion issue with hyperlinks

Bug

WORDSNET-14686

Document.Compare increases the Table's cells

Bug

WORDSNET-14689

List numberings changes from alphabets to numbers during rendering

Bug

WORDSNET-14698

UpdateFields truncates text in bookmark cross-reference

Bug

WORDSNET-14703

A formula errors to "divide by zero" when calling UpdateFields

Bug

WORDSNET-14717

Charts become invisible in output HtmlFixed

Bug

WORDSNET-14728

Word to PDF conversion create "double encodes" hyperlinks

Bug

WORDSNET-14732

Some text content is repeated in rendered document

Bug

WORDSNET-14749

Rtf to Doc conversion issue with page numbers of TOC field.

Bug

WORDSNET-14752

When open document, a Aspose.Words.FileCorruptedException occurs.

Bug

WORDSNET-14761

HTML document has no <link> to external CSS file when callback is used

Bug

WORDSNET-14768

Horizontal Axis of chart does not render correctly in output PNG

Bug

WORDSNET-14792

Document.Compare does not work for CheckBox (FormField)

Bug

WORDSNET-11771

Support the dir and the bdo elements

Enhancement

WORDSNET-14579

Date Field with mixed bidi/non-bidi formatting.

Enhancement

WORDSNET-14589

Add CssFolder property to HtmlSaveOptions

Enhancement

WORDSNET-14590

Discrepancy between HtmlSaveOptions and HtmlFixedSaveOptions regarding ImagesFolder and FontsFolder properties.

Enhancement

WORDSNET-14713

More horizontal spacing between paragraphs of the same style when exporting to HTML

Enhancement

WORDSNET-14741

Review when Word ignores strokes with weight less that 1 pt

Enhancement

WORDSNET-14636

Aspose.Words.FileCorruptedException occurs upon loading a DOCX

Exception

WORDSNET-14642

Document.Save method throws System.InvalidOperationException whend document is re-saved

Exception

WORDSNET-14702

FileCorruptedException caused by charts

Exception

WORDSNET-14746

NullReferenceException while mailmerge

Exception

WORDSNET-14762

Export fonts to HTML in Base64 encoding

Feature

WORDSNET-5645

Expose (Height/Width) access to Text Frames

Feature

WORDSNET-6833

OutOfMemoryException occurs during rendering DOCX to PDF

Performance

Public API and Backward Incompatible Changes

This section lists public API changes that were introduced in Aspose.Words 17.2.0. 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.

WORDSNET-14589 and WORDSNET-14590 - Added public properties HtmlSaveOptions.ResourceFolder and HtmlSaveOptions.ResourceFolderAlias

Check the detailed article on Working with HtmlSaveOptions Properties

New public properties ResourceFolder and ResourceFolderAlias are added into the HtmlSaveOptions class:

Behavior of properties FontsFolder, FontsFolderAlias, ImagesFolder, ImagesFolderAlias and CssStyleSheetFileName are not changed.

Note that CssStyleSheetFileName properties is used both for specifying folder name and file name.

Order of priority in which Aspose.Words decides into what folder to write external CSS style sheet:
1. Folder specified in CssStyleSheetFileName property.
2. Folder specified in ResourceFolder property.
3. Output folder where HTML document is saved.

Order of priority in which Aspose.Words decides what name external CSS style sheet has:
1. File name specified in CssStyleSheetFileName property.
2. Output HTML file name with ".css" extension.

Order of priority in which Aspose.Words decides into what folder to write fonts:
1. Folder specified in FontsFolder property.
2. Folder specified in ResourceFolder property.
3. Folder where code assembly is located.

Order of priority in which Aspose.Words decides into what folder to write images:
1. Folder specified in ImagesFolder property.
2. Folder specified in ResourceFolder property.
3. Folder where code assembly is located.

Note that when relative path is specified, FontsFolder and ImagesFolder are relative to folder where code assembly is located, ResourceFolder and CssStyleSheetFileName are relative to output folder where HTML document is located.

Here are some use cases. In examples below input test document has name Test.docx, output HTML document has name Test.html. Input document has one image Test.001.png and one font Test.calibril.ttf. By default external CSS style sheet has name Test.css.

1. Simplest scenario. Use it if you want to save all external resources in one folder.

Output

2.

Output

Fonts and CSS style sheet are not written as external resources.

3.

Output

When ResourceFolder specifies relative path this path is relative to output folder, where HTML document is saved.

4.

Output

In this scenario "http://example.com/resources" alias is used to construct URIs of all resources.

5.

Output

In this scenario "http://example.com/resources" alias is used to construct URIs of all resources.

6.

Output

7.

Output

8.

Output

9.

Output

WORDSNET-14762 - Added Public Property HtmlSaveOptions.ExportFontsAsBase64.

Check the detailed article on Export fonts to HTML in Base64 encoding

New public property ExportFontsAsBase64 is added into the HtmlSaveOptions class:

The property affects only HTML format and doesn't affect EPUB and MHTML. This is an extension to HtmlSaveOptions.ExportFontResources option and ExportFontsAsBase64 will work only if this property set to true.

UC
Labels
  • No labels