Mimic MS Word 2016 Behavior for Fixed-Page Formats & WMF Fonts Scaling using .NET APIs

What's New in this Release?

Aspose development team is happy to announce the monthly release of Aspose.Words for .NET 18.12. In old versions of Aspose.Words, handling of hide mark element in a table cell for rendering document to fixed page format is according to MS Word 2013 behavior. Starting from Aspose.Words 18.12, Aspose team has changed this behaviour to mimic MS Word 2016 behavior. In some situations, for continuous and “new column” section breaks, the behavior of MS Word 2016 is different from MS Word 2013 or an earlier version when document is converted to fixed file formats e.g. PDF, XPS. It has changed the behavior of Aspose.Words to mimic MS Word 2016. The behavior has changed for computing page numbers and for providing an empty facing page when adjacent pages have the same oddity. It has added new property ScaleWmfFontsToMetafileSize in MetafileRenderingOptions class to control the scaling of fonts in WMF meta-file according to meta-file size on the page when redering document to fixed file format. This property is used only when meta-file is rendered as vector graphics. By default, Aspose.Words uses font family names from source document and writes to HTML. Starting from Aspose.Words 18.12, Users can resolve and substitute fonts according to FontSettings. Here is a look at just a few of the biggest features and API changes in this month’s release, Implemented WMF fonts scaling, according to metafile size on the page, and public option to control it. 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 columnm, Fixed layout when tables merge over the hidden paragraph andn many more. The list of new and improved features added in this release are given below

• There is no rotation when open the document in the below version of 2003
• Create a demo which allows the user to upload a document and convert it to any supported format
• Release Aspose.Words for C++
• Difficulties when accessing field names returned by MailMerge.GetFieldNames
• Support page number field formatting in Model
• Removing colon between empty MERGEFIELDs
• Render Comments in Arabic Language mode
• Allow insertion of Custom Fields using DocumentBuilder.InsertField method
• Analyze what it takes to make Aspose.Words for Windows Universal 10 App (UWP)
• Add members to LoadFormat and SaveFormat enumerations for Strict Open XML Document (.docx) format
• Support Windows Store App (Windows Runtime/WinRT)
• Provide an API to read and update SDT to CustomXML properties
• Tables rendered one over the another after conversion doc to pdf
• Make it possible to insert section or document at merge field or bookmark
• Negative font spacing is not preserved after HTML round-trip
• Table rows not aligned
• Converting DOC to PDF moves some Table Rows to right
• Word to PDF Table Alignment Issue
• Remove public API method 'SetAsDefault' from LoadOptions.LanguagePreferences
• DOCX to PDF - invalid page count in the header
• Page numbers in footer not correct in rendered PDF
• Font size depend on metafile bbox aspect ratio
• DOCX to PDF - tables split across two pages
• DefaultFontName setting is not working for saving into HTML
• Floating table overlaps text when anchor is pushed to the next column
• Position of floating table is incorrect.
• Legends stretched on diagram when converted to PDF.
• Font of text is changed after conversion from DOCX to HTML
• Table's cell is lost after conversion from DOCX to HTML
• DOCX to PDF conversion issue with chart rendering
• Header not rendered
• Hyphenation in Aspose.Words pdf output is different from MS Word
• Position of hyphen is different when converting Docx to Pdf
• Content is moved beyond the page
• INCLUDEPICTURE is lost during DOC to DOCX, WML and RTF conversion
• Invalid license signature error on calling License.SetLicense method
• Docx to Pdf conversion issue rotated text of Shape
• Table widths are not correct in PDF
• Part of content is moved to previous page upon rendering.
• Size of image inserted using INCLUDEPICTURE field is changed after converting to DOC
• Image CSS style is ignored and the image is rendered full size in the word
• Content controls linked to custom xml properties filled from SharePoint metadata are empty on conversion to pdf and doc (sdt)
• Different Foreign Language texts rendering as square boxes in PDF
• When converting DOC to PDF, bookmarks for TOT (Table Of Tables) & TOF (Table Of Figures) are not created
• Incorrect shape width when word wrap is OFF in text box properties
• Aspose.Words v18.3.0: NullReferenceExeption when saving table
• Invalid order of chart legend items after conversion to PDF
• The picture rendered incorrectly in PDF output
• Specifying MsWordVersion.Word2016 of OptimizeFor does not respect ResourceLoadingAction.Skip during saving to DOCX
• NullReferenceException while saving to mhtml
• Arabic text is rendered as reversed in output PDF
• Docx to Pdf conversion issue with table's width
• DOCX to PDF - content moved
• DOCX to PDF - content on page 2 is hidden
• MHTML to PDF - indented email text becomes single column
• Text of the chart user shape is clipped after converting to PDF
• The last data label is not rendered after converting to PDF
• DOCX to PDF/Jpeg conversion issue with Hindi font
• Content overlaps in generated PDF
• Chart.Title.Text returns incorrect value
• Header hight with dynamically growing content is incorrerct in Pdf
• Problem with image alignment while converting to mhtml or html file

Other most recent bug fixes are also included in this release

Overview: Aspose.Words

Aspose.Words is a word processing component that enables .NET applications to read, write and modify Word documents without using Microsoft Word. Other useful features include document creation, content and formatting manipulation, mail merge abilities, reporting features, TOC updated/rebuilt, Embedded OOXML, Footnotes rendering and support of DOCX, DOC, WordprocessingML, HTML, XHTML, TXT and PDF formats (requires Aspose.Pdf). It supports both 32-bit and 64-bit operating systems. You can even use Aspose.Words for .NET to build applications with Mono.

More about Aspose.Words

- Homepage of Aspose.Words for .NET: https://products.aspose.com/words/net

- Download Aspose.Words for .NET: https://downloads.aspose.com/words/net

- Online documentation of Aspose.Words : https://docs.aspose.com/display/wordsnet/Home

Aspose Pty Ltd was founded in March 2002 in Sydney, Australia. The corporate portal was firstly launched in October 2002. Aspose strives to provide the richest component choices for global .NET programmers. Thousands of organizations from tens of countries have acquired Aspose products, including Microsoft, IBM, PricewaterhouseCoopers, Ernst & Young, DuPont, Hilton Hotels, Reader's Digest, Bank of America, Boeing, Siemens, etc.

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Phone: 888.277.6734
Fax: 866.810.9465

This release was published on openPR.