Specifying Metafile Format When Exporting Word Document to HTML in Android Apps

Aspose's picture

It contains over 100 useful new features, enhancements and bug fixes. Here are some of the big features & enhancements, support to insert Style Separator to put different Paragraph styles, KeepSourceFormatting logic improved, rendering of SVG graphics elements embedded into DrawingML, added option to disable the internal font substitution mechanism and use the default font instead while rendering to PDF, auto-size calculation of rotated VML text boxes with vertical layout fixed

Lane Cove, NSW, 2066 Australia., February 25, 2018 - (PressReleasePoint) -

What's New in this Release?

Aspose development team is happy to announce the monthly release of Aspose.Words for Android via Java 18.2.0.  This month’s release contains 100+ useful new features, enhancements and bug fixes. Aspose.Words for Android via Java has full functionality of Aspose.Words for Java with few limitations, minor API changes and additional requirements.  In this version of Aspose.Words, it has added the support of style separator to put different paragraph styles in the same printed paragraph. Style Separator can be added to the end of a paragraph using the Ctrl+Alt+Enter Keyboard Shortcut into MS Word. This feature allows for two different paragraph styles used in one logical printed paragraph. It has added HtmlSaveOptions.MetafileFormat property to specify in what format metafiles are saved when exporting to HTML, MHTML, or EPUB. By default metafiles are rendered to raster PNG images. HtmlMetafileFormat enumeration has added to indicate the format in which metafiles are saved to HTML document. It has added new property FontSettings.EnableFontSubstitution in this version of Aspose.Words to specify whether to enable or disable font substitution. There are some important enhnacements and bug fixes also part of this release, such as support to insert Style Separator to put different Paragraph styles, HtmlSaveOptions.MetafileFormat property added, KeepSourceFormatting logic improved, rendering of SVG graphics elements embedded into DrawingML objects (svgBlip) implemented, added option to disable the internal font substitution mechanism and use the default font instead while rendering to PDF, Fixed “Compound lines are not supported” warning generation, fixed problem with path gradient brush scaling while rendering metafiles, spacing  between legend items in DrawingML Charts rendering fixed, the data series line with “Round” cap type is rendered properly when exporting DrawingML Charts into PDF now, rotated VML text boxes with non-default alignment rendering fixed, auto-size calculation of rotated VML text boxes with vertical layout fixed, Implemented none wrapping for text frames, improved paragraph spacing computation with hidden paragraphs, improved custom tab stops handling around hidden paragraphs, improved line wrapping around dashes, improved character spacing control for complex code point sequences, improved processing of out-of-order footnotes, implemented mirror margins and gutter position handling when page orientation changes, improved performance of reflow when document is large and has fields in headers/footers and fixed text box width issue with left-aligned RTL text. Aspose.Words for Android via Java’ is an advanced Word document processing API to perform a wide range of document processing tasks directly within users native Android applications. Aspose.Words for Android via Java API supports DOC, OOXML, RTF, HTML, OpenDocument, PDF, XPS, EPUB and other formats.  The list of new and improved features added in this release are given below

  • FontSettings.EnableFontSubstitution option added
  • Support to insert Style Separator to put different Paragraph styles
  • HtmlSaveOptions.MetafileFormat property added
  • KeepSourceFormatting logic improved
  • Rendering of SVG graphics elements embedded into DrawingML objects (svgBlip) implemented
  • Added option to disable the internal font substitution mechanism and use the default font instead while rendering to PDF. (FontSettings.EnableFontSubstitution)
  • Fixed "Compound lines are not supported" warning generation
  • Fixed problem with path gradient brush scaling while rendering metafiles
  • Spacing  between legend items in DrawingML Charts rendering fixed
  • The data series line with "Round" cap type is rendered properly when exporting DrawingML Charts into PDF now
  • Rotated VML text boxes with non-default alignment rendering fixed
  • Auto-size calculation of rotated VML text boxes with vertical layout fixed
  • Implemented none wrapping for text frames
  • Improved paragraph spacing computation with hidden paragraphs
  • Improved custom tab stops handling around hidden paragraphs
  • Improved line wrapping around dashes
  • Improved character spacing control for complex code point sequences
  • Improved processing of out-of-order footnotes
  • Implemented mirror margins and gutter position handling when page orientation changes
  • Improved performance of reflow when document is large and has fields in headers/footers
  • Fixed text box width issue with left-aligned RTL text
  • WordArt objects are rendered incorrectly
  • List numbers are changed after re-saving Docx
  • Top/Bottom margins are not correct in a 2 pages per sheet layout
  • Content is misplaced after DOCX to HtmlFixed
  • Tables touch left page edge in generated PDF
  • Table is not rendered correctly in the output PDF
  • Consider removing script suffix from font name on RTF import
  • Docx to Pdf conversion issue with SVG rendering
  • Too many styles in resultant merged document
  • DOC to PDF Number of Pages Increased
  • DOC to PDF Issue with Art Fonts and Image Shading
  • FontSettings.DefaultFontName priority over FontInfo
  • The paragraph format has been lost in PDF output
  • Shape is not resized properly
  • SonarQube issues
  • More improvements need in WORDSNET-8414
  • File paths get saved incorrectly in content.xml
  • Background is incorrect when WrapMode.CLAMP is used
  • PathGradient disappeared
  • Incorrect result while calculation in FieldFormText
  • HtmlReader can't find installed font by its font's family
  • The string with the French (Switzerland) currency symbol cannot be parsed
  • Some fields containing functions returns '!Syntax Error'
  • Incorrect Russian months names
  • Incorrect PathGradient's pattern

Other most recent bug fixes are also included in this release

Newly added documentation pages and articles

 

Some new tips and articles have now been added into Aspose.Words for Android documentation that may guide users briefly how to use Aspose.Words for performing different tasks like the followings.

 

Overview: Aspose.Words

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

More about Aspose.Words

Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - The File Format Experts
sales@aspose.com
Phone: 888.277 6734
Fax: 866.810 9465


Press Contact:
David
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
888.277.6734
*********.*****@*s**s*.com
Email partially hidden to block spam. Please use the contact form here.
Contact David
Email the contact person for this press release. Do not send spam or irrelevant message.
4 + 7 =


Copy this html code to your website/blog to embed this press release.

Comments

Post new comment

7 + 1 =

To prevent automated spam submissions leave this field empty.