Set Horizontal/Vertical Resolution for Output Image & Advanced Documents Comparison Options

What's New in this Release?

Aspose development team is happy to announce the monthly release of Aspose.Words for Java & .NET 17.4.0. This month’s release contains over 80 useful new features, enhancements and bug fixes. Here is a look at just a few of the biggest features and API changes in this month’s release; CompareOptions class introduced to allow customer specify comparison settings, Custom Xml Data Properties is now supported for RTF format, Implemented support for baseline alignment in Asian text, Improved table split for vertically merged cells in combination with at-least height, Improved table grid calculation for horizontally merged cells, Improved BalanceSingleByteDoubleByteWidth handling, The horizontal and vertical resolution of output images can now be specified separately (through ImageSaveOptions.VerticalResolution and ImageSaveOptions.HorizontalResolution), Underline, strikethrough, text borders and effects are now taken into account wile rendering OfficeMath equation text, A substitution of fonts with the same name but with different suffixes now generates a proper warning, Textboxes with automatic fit is now rendered correctly inside the group shapes, Corrupted texture images do not stop the rendering procedure with an exception, a warning is sent instead now and DrawingML Charts rendering improved (rotated and scaled horizontal axis labels). It has implemented a more generic and flexible solution to format field result. It has added an interface IFieldResultFormatter in Aspose.Words 17.4 allowing to implement custom formatting of field’s result. Now, users can apply formatting to numeric and date/time field result. Previously it was one property ImageSaveOptions.Resolution that set both vertical and horizontal resolution to the same values. It has added new public properties HorizontalResolution and VerticalResolution in ImageSaveOptions class to set horizontal and vertical resolution of output image. It has introduced new class CompareOptions in Aspose.Words 17.4 to compare two documents with advanced options. Now, users can ignore document formatting and header footer content during document comparison. The list of new and improved features added in this release are given below

• Compare documents with comparison setting
• Convert Vml shapes to Dml upon saving to Strict Open XML Document format.
• Add feature to remove spaces between sign and digits during mail merge
• Add feature to set Horizontal and Vertical Resolution of output image
• Consider support of conditional and browser-dependent comments
• Document.Save removes {*datastore ...} tag from Rtf
• Make sure CssIdentifierValue.ToCss escapes identifier.
• Import custom list markers from ::before pseudo-elements when converting from HTML to Words
• x-none language is not supported for DOCX
• Cell's border become visible after modifying style of Div tag in HtmlFixed
• Table width is not calculated correctly during rendering to PDF
• ROOT Inline Shape position is changed after conversion from Docx to Pdf
• Docx to Pdf conversion issue with AltChunk (HTML file)
• Restricted and Hidden styles appearing in styles pane and Quick style gallary
• The font size of altChunk contents is changed after re-saving Docx
• The font name of altChunk contents is changed after re-saving Docx
• TextAlignment property does not take effect and leads to different output from MS Word when converting to xps
• PDF Conversion Issue with Docx containing customxml
• Unknown ListTrailingCharacter enum member.
• Image is rendered on next page after conversion from Docx to Pdf
• Document.Compare generates incorrect format revisions
• Incorrect export of equation in MathML
• Incorrect order of tags if they are inside of MS Word's table during Replace operation
• Shape's text does not render correctly in output Pdf
• Docx to Pdf conversion issue with shape's rendering
• Docx to Pdf conversion issue with shape's rendering/position
• Strikethrough in Equation not preserved during rendering
• Textbox positions are not preserved during open/save a DOCX
• Roundtrip of the DOCX document has wrong output
• Word to HTML then back to Word, table has extra space between rows
• PageRef is converted to hyperlink in output Pdf
• Showing bullets and font substitution problems
• Document's contents are lost after re-saving Docx
• Saving Embedded Spreadsheet produces a different file every time
• MHTML to PDF, Hebrew content in Subject is changed.
• When DOCX is saved as PDF, some content overlaps the footer.
• Document.UpdateFields does not update Ref field in output Docx/Pdf
• Extra div elements are exported in HtmlFixed
• While transforming a specific Word document to PDF, the table appears mixed up.
• Word drawing diagrams are overlapped after conversion from Docx to Doc/Pdf
• When DOCX is saved as PDF, the line of graph is different.
• The embedded xlsm is changed to xlsx after re-saving Docx
• DOCX save inserts invalid tblPrEx element to style
• Different number of lines in AW pdf output because of SBCS/DBCS balancing
• Stylesheet problem when saving DOC to DOC
• When DOCX is saved as PDF, gradient fill is lost
• Horizontal Axis of chart does not render correctly
• ShapeRenderer.Save renders extra number on chart's image
• Corrupted word file after save
• DocumentBuilder.MoveToHeaderFooter does not move the cursor to the header of document
• Trendline of chart is changed in output Pdf
• Part of header image is truncated in output HtmlFixed
• Docx to Pdf conversion issue with OfficeMath equations
• Range.Replace finds and replaces text in the incorrect order
• The Image is lost When Convert docx to docx (pdf)
• Old incorrect value is rendered inside a SDT in PDF
• When DOCX is saved as PDF, the comma in chart has been replaced by semi-colon in all labels.
• The chart's legend entries are reversed in HtmlFixed
• SEQ Ordinal not translated in Dutch
• Pictures not shown or rendered incorrectly in HtmlFixed
• Custom document properties are lost after conversion from Doc to Docx
• Spanish labels become english
• Style of text in header is changed during rendering.
• Composite nodes inside paragraph not handled during TOC update.
• Font name is corrupted when converting RTF to DOC

Other most recent bug fixes are also included in this release

Overview: Aspose.Words

Aspose.Words is a word processing component that enables .NET, Java & Android 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. Developers can even use Aspose.Words for .NET to build applications with Mono.

More about Aspose.Words

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

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

- Online documentation of Aspose.Words : http://www.aspose.com/docs/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.