EMF Metafiles Creation & Exporting Text as Shape While Converting EMF to SVG in .NET Apps

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Imaging for .NET 3.9.0. The major development in this release is support for creating EMF metafile image. This release supports PSD file created/updated using SAI and GIMP2 tools. Exporting text as shapes while converting EMF metafile to SVG format has also been incorporated in this release. Aspose.Imaging for .NET now supports creating EMF metafile image. It provides the EmfRecorderGraphics2D class to create EMF metafile. Developers can get text as shapes while converting EMF to SVG format using this release. This release also provides the TextAsShapes property to get text as shape while converting EMF metafile. There are some important enhancement also part of this release, such as Support to load PSD file created/updated using SAI software/editing tool has been incorporated, support to load PSD file created/updated using GIMP2 software/editing tool has been incorporated, converting Djvu to PDF has been improved, Process of converting Djvu image pages to PNG has been improved, updating text in PSD text layers has been improved, ICC profiles for Jpeg2000 images have been implemented, Process of rotate operation on raster image has been improved, Process of converting TIFF to JPEG has been improved and Process of extracting frames from a TIFF file has been improved. The main new and improved features added in this release are listed below

• Support for SAI format
• Support for GIMP2 format
• Implement ability for adding both vector graphics and bitmap components to Metafile
• Converting Djvu to Pdf file contains black pages only instead of image in it
• Djvu extracted pages does not contain colors
• Djvu converted to PDF successfully but unable to open the PDF using Adobe PDF reader
• Emf image export error
• Support for TEXT_AS_SHAPES while converting EMF to SVG format
• Updating text in text layers of a PSD file is not generating expected output and also throwing exception
• Investigate emf/emf+ renderer performance
• Implement support of Icc profiles for Jpeg2000 images
• PSD file has 6 layers while Aspose.Imaging shows 0 layers
• Rotate operation causes color lose
• Converting TIFF to JPEG shows exception: Image export failed, cannot parse file
• Multiple exports or saving of EmfImage throws an exception.
• Transparency issue while Extracting TIFF Frame

Overview:Aspose.Imaging for .NET

Aspose.Imaging for .NET is an image processing & manipulation component that allows developers to create, edit, draw or convert images in their .NET application. It allows developers to convert image files to PSD, BMP, JPEG, PNG, TIFF and GIF formats. Moreover a set of pens, brushes and fonts can be used to draw images or add new elements & text to existing images. Aspose.Imaging for .NET works well with both web & windows applications. Moreover, it adds the support for Silverlight platform.

• Homepage of Aspose.Imaging for .NET
• Download Aspose.Imaging for .NET

Configure Fonts for Rendering Spreadsheets & Control Chart’s Data Source in .NET Apps

What’s new in this release?

We are pleased to announce the new release of Aspose.Cells for .NET 8.9.2. This release includes several new features and other enhancements with critical bug fixes. Aspose.Cells API has exposed a number of new classes as well as an enumeration to configure font sources for rendering spreadsheets to image formats and PDF. Most important class is the FontConfigs which has many useful factory methods to either set the font sources or set the font substitution along with some inspection APIs to retrieve the list of specified font sources as well as font substitutions. Aspose.Cells APIs search the operating system’s default font directory for the required fonts. In case the required fonts are not available in the system’s font directory then the APIs search through the custom (user defined) directories. It also provides the ability to set user defined font substitutions for rendering purposes. This mechanism is helpful when a required font is not available on the machine where conversion has to take place. You can provide a list of font names as alternative to the originally required font. In order to achieve this, the APIs have exposed a new method which accepts 2 parameters. The first parameter is of type string, which should be the name of font which needs to be substituted. The second parameter is an array of type string. Developers can provide a list of font names as substitution to original font (specified in the first parameter). The Aspose.Cells APIs has also provided means to gather information on what sources and substitutions have been set. Aspose.Cells for .NET API has exposed the Boolean type property along with the an overload of Cells.CopyRows method in order to facilitate the copy rows operation when rows to be copied also contains a chart and its data source. You can make use of these new APIs to point the chart’s data source to the source or destination worksheets. This release  allows to get/set the IFilePathProvider for exporting worksheets to separate HTML files. These new APIs are helpful in scenarios where hyperlinks in one worksheet points to a location in another worksheet, where application requirement is to render each worksheet to separate HTML file. Implementing the IFilePathProvider allows to keep the aforementioned hyperlinks intact regardless of the fact that they are pointing to a location in a separate resultant HTML file. It has made a few changes to the publicly exposed APIs in order to keep the API usage simple. This release has includes some important fixes and enhancements. such as enter Cell Data of GridWeb Worksheet in Percentage Format, enhanced HTML rendering engine,   Improved PDF rendering engine for charts, shapes as well as style/formatting including cell’s text alignment and Tweaked Aspose.Cells’ formula calculation engine to match the results with Excel application. It has handled a few exceptions regarding reading and writing Excel and HTML file formats. In this release, several important issues have been addressed. For example, issues around reading and writing Microsoft Excel file formats, rendering images from Excel worksheets, rendering images files from charts and exporting Excel workbooks to PDF format have been resolved.  This release includes several enhanced features and bug fixes as listed below

• Support TTE font type while rendering spreadsheets to PDF
• Use private characters in PDF rendering
• Numbers formatting (DateTime) lost when importing data from DataGrid (.NET)
• Chart copied with CopyRows still reference the source worksheet in Chart Data Range
• Convert Date String to Date Format
• Colspan as 2 increases the HTML loading and conversion time drastically
• Performance degradation while rendering spreadsheets to PDF
• Bold attribute is lost while converting HTML to XLSX
• Direction of contents is changed while converting HTML to XLSX
• Borders are missing while converting HTML to XLSX
• Cell shading is missing while converting HTML to XLSX
• Contents are missing while converting HTML to XLSX
• Improper conversion of HTML to XLSX
• MHTML to XLS/XLSX is coming back as blank document
• Issue with hyperlinks referencing a worksheet in the same document
• SumProduct formula is not calculated correctly
• Missed text after XLS to Pdf/A conversion
• Vertical alignment issue with cell content touching the top border while rendering spreadsheets to PDF
• Horizontal alignment issue with values preceded by $ sign while rendering spreadsheets to PDF
• Lost fonts in the PDF
• Result of CalculateTextSize is always the default height if text in a TextBox contains new lines
• Chart is not correct in the sample2.xlsx (Excel to PDF conversion)
• Data Tables are not correct in the sample2.xlsx (Excel to PDF conversion)
• Data Tables are not correct in the sample1.xlsx (Excel to PDF conversion)
• Modified radar chart marker does not convert to PDF properly
• Horizontal axis labels are missing in Chart to image rendering
• Issue with WordArt shape's formatting in the rendered PDF file
• Alignment is not working inside a TextBox
• File is corrupted (with hyperlink becomes normal text) after processed by Aspose.Cells APIs
• Re-embedding the presentation slide in XLS results in presentation view upon double clicking
• Excel error "Cannot start the source application for this object" after reinserting the OleObject of Bitmap type
• Formula results in #REF error after copying the rows and calculating formulas
• Date format not retained when saving as SpeadsheetML file
• Inserting range of cells causes background for some cells disappeared
• Path issue with external data links for XLS spreadsheets
• Resaving spreadsheet with custom theme causes error in Open XML SDK
• Custom Calculation Engine causes the calculation happen only once
• Error during opening an XLSB file
• Conversion from HTML to XLSX in the resultant spreadsheet
• Contents are missing while converting HTML to XLSX
• Style is missing while converting HTML to XLSX
• Impossible to make a TextBox fully transparent
• Chart.Calculate() method messes up the chart
• Series is missing while rendering chart to image
• Ambiguous comments for the depreciated Shape.LineFormat & FillFormat properties
• Default behaviour of adding TextBox to Worksheet has changed
• OLELink changed (Word table imported in Excel) document still shows old values after Update Links
• Colors are changed after loading and saving an XLS file
• Issue when using Percentage2 Number Format
• Vertical scroll bar appears for the container when height of the GridWeb is set to 100%
• Cursor is not moving when ShowCellEditBox is set true
• Merging cells second time is not working
• Problem setting the value of a cell with percentage format
• GridDesktop does not have evaluation limitations when used in WPF application
• Implement or add comment inside the acwmain.js file to know its version number
• Extra empty cell is inserted to the right of the first empty cell on pasting row

Other most recent bug fixes are also included in this release

Overview: Aspose.Cells for .NET

Aspose.Cells is a .NET component for spreadsheet reporting without using Microsoft Excel. It supports robust formula calculation engine, pivot tables, VBA, workbook encryption, named ranges, spreadsheet formatting, drawing objects like images, OLE objects and importing or creating charts. You can also create Excel file using designer spreadsheet, smart marker or API and apply formulae and functions. It supports CSV, SpreadsheetML, PDF and all file formats from Excel 97 to Excel 2007.

• Homepage of Aspose.Cells for .NET C#
• Download Aspose.Cells for .NET

Get Last Modified Date of Raster Image, WMF to PDF & Webp Conversion using Java

What’s new in this release?

Aspose development team is pleased to announce the new release Aspose.Imaging for Java 3.8.0. The major development in this release is support for WMF metafile. This release allows you to get last modified date of a raster image.  Aspose.Imaging for Java now supports the WMF metafile image format. WMF stands for Windows Media Format (Microsoft). There are are some important operations that can be performed on a WMF image using Aspose.Imaging,such as converting WMF To PDF, Converting WMF To Raster Format, Converting WMF To Webp, cropping WMF File While Converting To Raster Format and resize WMF File While Converting To Raster Format. Using Aspose.Imaging for Java, developers can get last modified date of a raster format. This release also include some important enhancements, such as SVG to Raster Image conversion process has been improved, Diacom to Raster Image conversion process has been improved, Process of loading TIFF image has been improved, process of loading PNG image has been improved, process of loading JPG image has been improved and exporting process of image in multi-threaded environment has been improved. The main new and improved features added in this release are listed below

• Support for SVG to Raster Image Conversion
• Support for WMF for possible conversion to raster images
• Conversion of SVG to JPG
• Conversion of SVG to PNG
• Support for Diacom DCM image format
• Support Wmf file format
• Unable to load a JPG image - Image loading failed exception
• Exporting images in multi-threaded environment is not working
• Support to get the last modified day information on images
• Exception while loading a PNG image: Could not read data
• Unable to read file. Exception: The method or operation is not implemented: Exception while loading a TIFF file
• Unable to read file. Exception: The method or operation is not implemented: Exception while loading a TIFF file
• Aspose.Metafiles rendered pattern brush with minor differences
• Aspose.Metafiles ignore pattern brushes specified by DIB (EMR_CREATEDIBPATTERNBRUSHPT record)
• Aspose.Metafiles ignores the text weight value (EMR_EXTCREATEFONTINDIRECTW record)
• Unable to load a JPG image - Image loading failed exception

Overview:Aspose.Imaging for Java`

Aspose.Imaging for Java is an image processing & manipulation component that allows developers to create, edit, draw or convert images in their Java application. It allows developers to convert images to BMP, JPEG, TIFF, GIF, PNG & PSD formats. It draws images using advanced features like Graphics & GraphicsPath. The drawing feature is useful for adding shapes, building up new images or adding watermarks to images. It works well with both web & windows applications. It supports JDK 1.5 & above.

• Homepage of Aspose.Imaging for Java
• Download Aspose.Imaging for Java

Split PST File with Defined Criterion & Retrieve Message Summary using Unique Id in Java Apps

What’s new in this release?

We are pleased to announce the new release of Aspose.Email for Java 6.8.0. Ported from its equivalent .NET version, this month’s release includes the same new features, enhancements and bug fixes. Specifically, it allows splitting a PST based on defined criterion using the PersonalStorageQueryBuilder, option to detect if a loaded message is TNEF, and getting message’s summary information using its unique id with Pop3Client of the API. This month’s release introduces a new feature of splitting a PST file into multiple PST files by specifying a combination of criterion. The PersonalStorageQueryBuilder class can be used to define criteria that meet user requirements. The new method, splitInto, introduced by the PersonalStorage class, provides the capability to split the PST file using these input criteria. This month’s release also provides the capability to detect if the message loaded using MailMessage was originally TNEF or not. The getOriginalIsTnef method exposed by MailMessage class can be used to identify the format of message for this. This month’s release also introduces a new feature where the API’s POP3 client provides the capability to retrieve message summary information using its Unique Id. The getMessageInfo method lets you obtain the Pop3MessageInfo object for a message by specifying its unique Id. This month’s release also fixes a number of bugs that were reported with the earlier version of the API. This further aids to the overall improvement and stability of the API functionality. The main improved features & bug fixes added in this release are listed below

• Option to split PST based on time and other criterion
• Move Folder and Sub-folders to some other folder using ImapClient
• Provide IsTnefMessage flag in MailMessage
• Retrieving Pop3MessageInfo using UniqueId
• Different information in MailMessage and MapiMessage "To" header field - Java
• ImapClient hangs on request with special characters like double quote
• Inconsistency in adding and searching sub folder in PST
• MailMessage.Body for calendar items does not return calendar Description
• ImapClient.GetCapabilities() returns empty array
• Regular attachment identified as Linked Resource by MailMessage
• Longfilename in nested attchments
• Recurrence Generation Performance Degradation
• Calendar cancellation information lost while MSG -> EML conversion
• Table formatting and document icons lost while MSG to Mhtml conversion
• MSG to EML conversion issues
• Wrong password causes long time to raise exception using Imapclient
• Exception "Item has already been added. Key in dictionary" while loading MSG to MapiMessage
• Exceptions while fetching messages from Office 365

Other most recent bug fixes are also included in this release.

Overview:Aspose.Email for Java 

Aspose.Email for Java is a Non-Graphical Java component that enables Java applications to read and write Microsoft Outlook documents without utilizing Microsoft Outlook. It enables developers to create new MSG file from scratch, update an existing MSG file, read Outlook MSG file & get it's properties like subject, body, recipients in to, cc and bcc, Adding or removing attachment, sender information and MAPI properties.  Aspose.Email for Java can be used with Web as well asDesktop Application.

• Homepage of Oulook component Aspose.Email for Java
• Download Aspose.Email for Java

Search Text in AutoCAD DWG File & Convert AutoCAD DGN Format to PDF in .NET Apps

What’s new in this release?

Aspose development team is pleased to announce the release of Aspose.CAD for .NET 1.1.0. The major developments in this release are support for searching text in DWG AutoCAD file and get external references of block attributes. Support to convert DGN AutoCAD format to PDF and convert DGN AutoCAD format to raster image format have also been incorporated in this release. Aspose.CAD for .Net now supports searching text in DWG file. Aspose.CAD API exposes CadText class that represents text entities in the DWG AutoCAD file. Aspose.CAD for .NET allows users to get block attribute value of external reference. Aspose.CAD for .Net now supports searching text in DWG file. Aspose.CAD API exposes XRefPathName property to get the external reference of a block attribute in a CadBlockDictionary collection. Aspose.CAD for .NET allows users to convert DGN AutoCAD format to PDF. Aspose.CAD.Image.Load method can be used to load DGN file, Aspose.CAD.ImageOptions.CadRasterizationOptions can be used to set vector rasterization options, Aspose.CAD.ImageOptionsBase can be used to set image options and Aspose.CAD.Image.Save method can be used to save output image. Aspose.CAD for .NET allows users to convert DGN AutoCAD format to raster images. This release also includes important enhancements such as EULA link has been introduced in MSI file, Memory management process while exporting CAD to BMP has been improved and Process of accessing Face3D objects has been improved. The main new features added in this release are listed below

• Find or search text in the DWG file
• Support to retrieve block attribute values from within a dwg and its external references
• Support for DGN file format for possible conversion to PDF & raster image formats
• Msi misses End User Agreement link
• Cad export to Bmp fails with out of memory exception
• Unable to access Face3D Objects in DXF file

Overview:Aspose.CAD for .NET

Aspose.CAD for .NET enables developers to convert AutoCAD DWG and DXF files to PDF, JPG, PNG, BMP, TIFF and GIF image formats. It is a native API and does not require AutoCAD or any other software to be installed. Developers can also convert the selected layers and layouts from the AutoCAD files. The conversion to PDF and Raster images is of very high quality. Developers can also remove entities from DWG and DXF documents. It also adds support for leader’s entity for DWG format.

• Homepage of Aspose.CAD for .NET
• Download Aspose.CAD for .NET

JasperReports Server 6.3.0 Support & Enhanced Compatibility Mode in Word 2010/2013

What’s new in this release?

The long awaited version of Aspose.Words for JasperReports 2.8.0 has been released. This release also includes support for JasperReports Server 6.3.0 and bug fixes to the Aspose.Words for JasperReports product. This release also includes some important enhancements, such as compatibility Mode in Word 2010/2013, background band (table) does not exported correctly in output Docx and LastPageFooter band does not export as Word document’s footer.  The list of new & improved features in this release are listed below

• Support JasperServer 6.3.0
• Compatibility Mode in Word 2010/2013
• Background band (table) does not exported correctly in output Docx
• LastPageFooter band does not export as Word document's footer

Starting from release 1.9.0 there are now several versions of the JAR library (this is necessary for better support of older versions of JasperReports):

• for JasperReports 5.6.0 … 6.2.0 (aspose.words.jasperreports-6.2.0.jar)
• for JasperReports 4.7.0 … 5.5.0 (aspose.words.jasperreports-5.5.0.jar)
• for JasperReports 3.7.2 … 4.5.0 (aspose.words.jasperreports-4.5.0.jar)
• for JasperReports 3.7.1 and lower (aspose.words.jasperreports-3.7.1.jar)

Please copy only one jar library according to the version of installed JasperReports.

Overview: Aspose.Words for JasperReports

Aspose.Words for JasperReports makes it possible exporting reports from JasperReports and JasperServer to Microsoft Word document (DOC), Office Open XML (OOXML, DOCX), Web page (HTML) and plain text (TXT) formats. It is written purely in Java and is provided as a single JAR file that can easily be deployed on the machines running JasperReports or JasperServer. Aspose.Words for JasperReports exports flow layout documents that are easy to further edit in Microsoft Word, if necessary.

More about Aspose.Words for JasperReports

• Homepage of Aspose.Words for JasperReports
• Download Aspose.Words for JasperReports

Convert Collada Scene to Other 3D Formats & Apply Visual Effects on 3D View using .NET

What’s new in this release?

Aspose team is pleased to announce the release of Aspose.3D for .NET 2.0.0. The new version allows developers to automatically set up one or multiple viewports in a single screenshot. Using multiple viewports technique can help in visualizing some large sized 3D scenes.  This release will enable developers to customize the post-processing algorithms in the future versions. Aspose.3D API has added support to import the Collada scenes. Collada is an open XML file format for 3D assets, supported by various 3D software packages. Developers would be able to import 3D scene elements like material, light, camera, texture and geometries (polygon, polylist, triangles, triangle fans and triangle strips). Developers may also import an existing Collada scene, and then save in other supported 3D file formats. It has plans to enhance the import operations of Collada files as well as incorporate the export feature in the upcoming releases. Using Aspose.3D API, developers can now capture various new viewports to present complex areas of a 3D scene in better presentable form. They can also save multiple viewports in a single screenshot. Aspose.3D API performs OpenGL rendering. It creates a hardware OpenGL-backend renderer. An initialization error will occur, if the machine has no hardware support of OpenGL 4.0. Aspose team will extend rendering in the future releases. Aspose.3D API has added support of four built in effects like grayscale, pixelated, edge detection and blur. These visual effects help in enhancing a 3D view. In the future,  Aspose team have plans to customize the algorithms. This release includes plenty of new features as listed below

• Import support for Collada
• Post-processing effects
• Use Vector4 to represent UV coordinates.
• Render may crash the application on 64bit platform

Overview: Aspose.3D for .NET

Aspose.3D for .NET is a feature-rich component and class library for .NET that empowers Mono and .NET application including ASP.NET, Windows Forms and Web Services to connect with prevalent 3D document formats automatically without the 3D modeling and rendering software being installed on the server. It supports FBX (ASCII, Binary) and STL (ASCII, Binary) file formats and developers can easily create, read, convert, modify and control the substance of these 3D document formats using Aspose.3D API.

More about Aspose.OCR for .NET

• Homepage of Aspose.3D for .NET
• Download Aspose.3D for .NET

Add/Remove Embedded Fonts in Word Files & Save Document Page in GIF inside Java/.NET Apps

What's New in this Release?
 
Aspose development team is happy to announce the monthly release of Aspose.Words for Java & .NET 16.7.0. This month’s release contains over 132 useful new features, enhancements and bug fixes to the Aspose.Words product. Here is a look at just a few of the biggest features and API changes in this month’s release, Save Document Page in GIF Format, Exposed more String and Number Formats for Expression Results in LINQ Reporting Engine, SKIPIF field supported, Support for MathML in HTML Export, support of Add and Remove Embedded Fonts, Improved Font Substitution Rules, MsWordVersion Enum Moved to Aspose.Words.Settings,  added Advanced Range.Replace methods and added Overload of DigitalSignatureUtil.Sign to Specify a Password for Decrypting Document. It has introduced new feature for saving a Document page to GIF format. A new ‘Gif’ member is added into ‘SaveFormat’ enum. Aspose.Words for .Net uses standard GIF codec provided by GDI+ & uses standard GIF codec provided by ImageIO. More String and Number formats for expression results are introduced in LINQ Reporting Engine. It has introduced new feature to support SKIPIF field. This field is now updated during mail merge. It adds Support for MathML in HTML Export and implemented APIs to add embedded fonts in a document when it is saved. Similarly, embedded fonts can be removed from the document when it is saved. It has improved font substitution rules in this release. When specific font is not installed but is embedded into the document and a substitute for this font is assigned. In this case, Aspose.Words will use the fonts embedded in the document. Aspose team has added new methods in Range class to support advanced find/replace operations. It has added new static methods for signing encrypted documents in this new release. In the last parameter of these methods, specify a password for decrypting source document. Also, this is meaningful only if source document has DOCX format. The list of new and improved features added in this release are given below

• Save Document Page in GIF Format.
• Exposed more String and Number Formats for Expression Results in LINQ Reporting Engine.
• SKIPIF field supported.
• Support for MathML in HTML Export.
• Support of Add and Remove Embedded Fonts.
• Improved Font Substitution Rules.
• Added Advanced Range.Replace methods.
• Added Overload of DigitalSignatureUtil.Sign to Specify a Password for Decrypting Document.
• /Show revisions in balloons/ Support rendering of revisions inside of balloons rather than inline
• /Show revisions in balloons/ Images from Markup Area are rendered in the middle of main content area in PDF
• /format revision/ Add feature to show format revision in pdf
• /format revision/ Add feature to show format revision in pdf
• Convert OfficeMath nodes into MathML
• Provide ability to create mathematical equation from MathML string
• Add feature to format string values in Linq Reporting Engine
• Import html image tag with height only (or width only) proportionally
• Add new save format in ImageSaveOptions as SaveFormat.GIF
• Non ECMA-367 documents with CustomXML issue with Microsoft Word Online
• Allow embedding fonts into DOCX documents.
• Support the SKIPIF mailmerge field
• Export W3C MathML formulas to HTML
• Ruby (Equation) field does not import in Aspose.Words DOM
• Improve Range.Replace to support breaks
• Assertion for unknown shape property when opening a document
• Improve font substitution in case when embedded font and substitute available
• Layout issues with Kinosku and AsianHangingPunctuation.
• Size of images changed during open/save a HTML   Bug
• List label is lost when list item is first in comment.
• CSS is lost after re-saving Html
• Doc to Pdf conversion issue with contents position
• InsertHtml reuses imported styles even if their CSS don't match
• /format revision/ Preserve Revision details in Balloons in PDF
• Content Control is not rendering in output Pdf
• Table layout is corrupted after saving a DOCX to DOCX
• ParagraphFormat.StyleName returns incorrect value for custom styles
• AppendDocument does not preserve table's cell width
• Text direction of cell's text is changed in output Html
• Mixed Numbers, English and non-English content is incorectly encoded
• Cell's position is changed after re-saving Rtf
• Font size of text is changed after re-saving Rtf
• Numeric formatting does not take effect in Linq Reporting Engine
• Font size of Hebrew text is changed after conversion from Docx to Html
• Tables do not merge correctly after removing paragraph between them
• /para rules/ Paragraphs are rendered on next page in output Pdf
• Parts of chart lost when converted to png with aspose words
• Alignment of a list item imported from HTML gets incorrect after Indent+Outdent or Remove+Insert
• Text font's color is lost after re-saving RTF
• Images are inverted after conversion from Doc to Pdf
• /format revision/ Formatting markup changes are not rendered in PDF
• Two empty pages appear in output document after re-saving RTF
• Docx to Pdf conversion issue with ListLabel
• Corrupted document is generated on saving as DOCX
• Doc to Pdf conversion issue with textbox's text rendering
• Chart x-Axis is rendered incorrectly in output Pdf when DataTable is visible
• NumPages field value in PDF is not according to the culture/language
• NumPages field value in PDF is not according to the culture/language
• SECTIONPAGES field value in PDF is not according to the culture/language
• Docx to Pdf conversion issue with SmartArt rendering
• Document.UpdateFields does not update Formula field inside Table
• /footnote balancing/ Footnote separator is overlapped with body text in output Pdf
• Images in GroupShape become inverted when saving to PDF
• Document's footer and some text elements will be rendered with the Error! No text of specified style in document
• Table's merged cells are repeated after re-saving Rtf
• FileFormatInfo.LoadFormat : Text document format detected as Unknown
• A picture in HtmlFixed repeats
• Text font's color is lost after re-saving RTF
• Shape's text color is lost after conversion from Docx to Pdf
• Exception occured while saving MathML to DOC document
• DocumentBuilder.InsertHtml renders a blank Math equation
• Contents render on previous page in output Pdf        Bug
• Docx to Pdf conversion issue with table's rendering in HtmlFixed/Pd
• Local document link incorrect when inside a shape (PDF)

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. You can even use Aspose.Words for .NET to build applications with Mono.

More about Aspose.Words

• Homepage Aspose.Words for .NET
• Homepage of Aspose.Words for Java

Detect Visio File Type from Input Stream & Modify Event Cells of Visio Shape using Java

What’s new in this release?

We are pleased to announce the new release of Aspose.Diagram for Java 6.7.0.  This release comes with a new feature, enhancements, and bug fixes. It gives a way to detect a Visio file format from an input stream. Developers would also be able to modify event cells of a Visio shape. Besides this, it covers many other regular bug fixes reported by our clients. Aspose.Diagram API allows developers to determine the type of a Visio file from an input stream. Developers can already detect the type of a Visio file by passing a complete local file path which also includes the filename and extension. The detectFileFormat method of FileFormatInfo class now gives both options to pass a complete filename or an input stream of the Visio diagram. In short, there are two overloads of this method, the first one accepts a complete file name, while the second one accepts an input stream. The ShapeSheet of a Visio shape has an Event section. The event section has event cells (TheText, EventDblCick, EventXFMod, EventDrop, EventMultiDrop, and TheDrop) in which formulas can be placed. These cells are being evaluated whenever an event occurs. We have enhanced the way of retrieving and updating the event cells in macro-enabled Visio file formats. We auto port Aspose.Diagram for .NET to Java to give developers perfectly same features on both platforms, so this version also incorporates the bug fixes and enhancements from its equivalent .NET version. This release includes several enhanced features and bug fixes as listed below

• Add support of detecting the file format using a stream object.
• VSD to PDF conversion - the red cross image appears instead of the shape.
• The endpoints of connectors are not connected when saving in the VDX format.
• Load and save routine of a VSDM diagram shows a cross in place of the button.
• Can't set an event cell of the shape in VSDM.
• Junk reading of the angle property in a VSDX diagram.
• Incorrect readings of incoming nodes in a VSD diagram.

Overview: Aspose.Diagram for Java 

Aspose.Diagram is a class library for working with MS Visio files & is a pure Java alternate for MS Visio Object Model. It is a standalone Visio Java library and does not depend on Microsoft Office Visio. It enables developers to work with VSD & VDX files and they can open files & Add   & manipulate the elements of the diagram, export Visio files to PDF, XML, HTML, images format, SVG & several other formats,  Rotate a shape, Add a hyperlink to a Visio shape, protect diagram shape and many more.  Aspose.Diagram can be used with any kind of application, whether it’s a Web Application or a Windows Desktop Application.

• Homepage of Aspose.Diagram for Java
• Download Aspose.Diagram forJava

Split PST File Based on Search Criterion & Detection of Message as TNEF in .NET Apps

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Email for .NET 6.8.0. This month’s release a new feature of splitting a PST based on specific search criterion. It also provides enhancement to the API’s IMAP client that is now able to move folders to other folders of a mailbox. This month’s release also fixes a number of bugs that further add to the overall stability of the API. Aspose.Email API already provides the capability of splitting a single large PST file into multiple small PST files. This month’s release further enhances this feature by providing the capability to split PST based on defined criterion. The API now provides support for specifying multiple criterion using PersonalStorageQueryBuilder. This allows including multiple search criterion such as time and subject simultaneously for splitting the PST. This month’s release also provides the capability of detecting whether the loaded email message was originally TNEF. The MailMessage API now provides the OriginalIsTnef property that detects the message as TNEF. A message’s unique id is always its representation and can be used to store a reference of the message as meta-data.  Retrieving of the same message from the email server can be obtained through the same. This month’s release further enhances the POP3 Client of the API to retrieve message summary information from the server using this unique id of the message. This provides quick access to the message’s short information without first retrieving the complete message from the server. In addition to new features and enhancements, this month’s release also fixes a number of bugs that were reported with the previous version of the API. It further enhances the stability and reliability of the API functionality. The main bug fixes & improved features added in this release are listed below

• Option to split PST based on time and other criteria
• Move Folder and Sub-folders to some other folder using ImapClient
• Provide IsTnefMessage flag
• Retrieving Pop3MessageInfo
• Different informaiton in MailMessage and MapiMessage "To" header field
• EEML to XPS: Formatting issues
• ImapClient hangs on request with special characters like double quote
• Inconsistency in adding and searching sub folder in PST
• MailMessage.Body for calendar items does not return calendar Description
• ImapClient.GetCapabilities() returns empty array
• Regular attachment identified as Linked Resource by MailMessage
• NULL Longfilename in nested attchments
• Recurrence Generation Performance Degradation
• Calendar cancellation information lost while MSG -> EML conversion
• Table formatting and document icons lost while MSG to Mhtml conversion
• MSG to XPS fails
• MSG to EML conversion issues

Other most recent bug fixes are also included in this release.

Overview:Aspose.Email for .NET

Aspose.Email for .NET is a set of .net email components allowing developers to easily implement email functionality within their ASP.NET web applications, web services & Windows applications. It Supports Outlook PST, EML, MSG & MHT formats. It allows developers to work with SMTP, POP3, FTP & MS Exchange servers. It supports mail merge, iCalendar, customized header & body, header information, embedded files, Twitter & many more. It makes it easy to work with HTML or plain text emails & their attachments.

More about Aspose.Email for .NET

• Homepage of Aspose.Email for .NET C#
• Download Aspose.Email for .NET

Aspose Launces New Java API for Working with AutoCAD DWG & DXF Files in Java Apps

What’s new in this release?

Aspose is proud to expand its Java APIs family with the addition of a new product known as Aspose.CAD for Java. This is a new addition to Aspose for Java APIs and allows users to work with CAD formats including DWG and DXF formats. Aspose.Imaging for Java also supports CAD formats but these formats will be removed from Aspose.Imaging for Java in next three months and all features related to CAD formats will be the part of Aspose.CAD only. This release of Aspose.CAD for Java supports converting DWG and DXF formats to PDF and raster image formats. Converting CAD layers and layouts to PDF and raster image formats has also been supported by this release. You can also remove entities from DWG and DXF documents. Aspose.CAD for Java allows you to convert CAD drawings to PDF format. Aspose.CAD for Java allows you to convert CAD drawings to raster image formats. Image.load method can be used to load CAD drawings, CadRasterizationOptions can be used to set vector rasterization options, ImageOptionsBase can be used to set image options and com.aspose.cad.Image.save method can be used to save output image. Aspose.CAD for Java allows you to remove specific entities from CAD drawings. Image.load method can be used to load CAD drawings, CadImage.getEntities() can be used to loop through each entity and CadImage. removeEntity can be used to remove any entity. There are some important new features included in this release, such as converting CAD layers to PDF, Convert CAD layouts to PDF, Converting CAD layers to raster image formats and Converting CAD layouts to raster image formats. The main new features added in this release are listed below

• Add support for removing entities
• Support CAD file formats for FileFormat enumeration and properly update Image.GetFileFormat method
• Support DXF 2007 format
• Add support for leaders entity for DWG format
• Add support for solid entity for DWG
• Add support for solid entity for DXF
• Converting DWG to PDF is producing PDF of zero size
• Exceptions namespace should be removed or renamed since it conflicts with Microsoft guidelines
• Fix reading DimensionStyle entity for 2004 DWG format
• Improve dashed polylines drawing

Overview:Aspose.CAD for Java

Aspose.CAD for Java enables developers to convert AutoCAD DWG and DXF files to PDF, JPG, PNG, BMP, TIFF and GIF image formats. It is a native API and does not require AutoCAD or any other software to be installed. Developers can also convert the selected layers and layouts from the AutoCAD files. The conversion to PDF and Raster images is of very high quality. Developers can also remove entities from DWG and DXF documents. It also adds support for leader’s entity for DWG format.

• Homepage of Aspose.CAD for Java
• Download Aspose.CAD for Java

Filter Data Type while Loading Spreadsheets & ActiveX Controls Support in Android Apps

What’s new in this release?

Aspose development team is pleased to announce the new release of Aspose.Cells for Android v8.9.0. Aspose.Cells APIs have provided the ability to add & manipulate the ActiveX Controls in spreadsheets. Aspose.Cells for Android API has exposed a number of useful classes, enumerations and methods to fully support the ActiveX Controls. The most worth mentioning addition to the public API is the ShapeCollection.addActiveXControl method which allows adding an ActiveX Control to the collection of shapes by accepting 7 parameters to specify the control type, location to place the control and size of the control. As per default behavior, the APIs load everything from the template file into its own object model, providing access to every aspect of the spreadsheet. There could be scenarios where the user does not want to load everything but specific objects, such as charts or shapes. The APIs have added the enumeration which can be used to make the selection of data type to be loaded from the template file. Filtering data at the time of loading can improve the performance tremendously, especially when used with LightCells APIs. As per default behaviour, Aspose.Cells APIs delete the blank rows & columns without updating the cell references that may have been effected from the delete process. This could lead to undesired results in certain cases, especially when spreadsheet contains formulas or charts. Aspose.Cells APIs have tried to overcome the aforementioned situation by exposing the overloaded versions of the Cells.deleteBlankRows & Cells.deleteBlankColumns methods with the release of Aspose.Cells for Android. It has now provide the ability to export spreadsheet contents in HTML format as per the standards opted by Excel application. If a spreadsheet is converted to HTML using Excel application, it does not render the grid lines. Aspose.Cells APIs behave in the same way using its default settings, however, with this release of the API, the developers can now choose to render the grid lines as well. It has exposed the OleObject.AutoLoad property which allows refreshing the OleObject’s image if the contents/data of the underlying object has been changed. Aspose.Cells APIs now allow to get and set the comments for an instance of ListObject. It has provided the ability to specify the default font name for rendering the spreadsheets in image formats. The DefaultFont property is of type System.string with default value as null. The said property can be used when Unicode characters in the spreadsheet have not been formatted with appropriate font in the cell’s style, consequently such characters may appear as blocks in the resultant images. It is advised to set the DefaultFont property to MingLiu or MS Gothic to properly show the Unicode characters in the resultant images. If the DefaultFont property is not set, Aspose.Cells for Android API will use the system’s default font to show the Unicode characters. This release has exposed the DefaultFontName property for the HtmlSaveOptions class that allows specifying the default font name while rendering spreadsheets to HTML format. The default font will be used only when a particular font used to style some contents in the spreadsheet does not exist on the machine where conversion process has to take place. The default value of HtmlSaveOptions.DefaultFontName property is null that means, Aspose.Cells for Android API will use the universal font which has the same family with the original font. spose.Cells for Android API has exposed the Boolean type IsExcel2003Compatible property for the PivotTable class which allows to impose or remove the Excel 2003 restrictions for refreshing Pivot Tables. The default value of IsExcel2003Compatible property is true, that means a string must be less than or equal to 255 characters. If the string is greater than 255 characters, it will be truncated. If false, the aforementioned restriction will not be imposed. Aspose.Cells APIs have already provided the facility to render charts to PDF. With this release, the API has exposed another overloaded version of the said method that could accept an instance of OutputStream, allowing the users to save the chart’s PDF in an instance of ByteArrayOutputStream. It  also adds the ability to set the shadow as text effects for any shape such as TextBox. This release includes plenty of improved features and bug fixes as listed below

• Exporting DataBars based on Conditional Formatting to HTML
• Support ColorScale, DataBar, IconSet while exporting XLSX to HTML
• Worksheet has no method calcualteFormula(String formula, CalculationOptions options)
• Performance bottleneck on Workbook.calculateFormula
• Setting ShowAllItems for PivotField does not seem to take effect
• Text is getting congested and overlapping in the EMF image
• Text labels are overlapping in the EMF image
• Exception is thrown on copying workbook
• Spreadsheet to HTML: Alignment of Text in a Shape is wrong after copying theme from source spreadsheet
• Graph is not rendered in the output PDF
• X-axis labels missing in Chart's PDF
• Incorrect number-format of X-axis labels in Chart's PDF
• Long hyphens don't display appropriately in the output PDF/Image for the chart
• Horizontal Grid-Lines of chart are not appearing properly in PDF
• Few chart bars are missing while rendering worksheet to image
• A named range is created when Cells.copyRow() method is used within a named range
• When applying autoSizeColumns on the sheet, the column is not widened properly
• CellsException while saving spreadsheet to PDF
• Certain data labels are missing while rendering chart to image
• CellsException: Cell has been removed: D9 with
• Exception: "Shape to image Error !" when rendering a worksheet to image
• How to set Legend Entry Properties for Text Options
• Create TextBox in which each line is having different Horizontal Alignment
• Conversion to HTML renders redundant empty rows
• Text alignment is changed after re-saving a template XLS file
• Excel file with DataBars not converted to HTML properly
• Pivot Chart created with Aspose.Cells does not display in Excel 2016 for MAC
• Aspose.Cells appends null at the end of the path for resources HTML
• LightCells APIs only generates events for the first column of the row
• Cell borders appear after resaving XLS
• Logo image is lost while converting XLS to PDF
• Character position is different in the rendered PDF from an XLS file
• Text overlapping when worksheet is converted to EMF on Linux
• Text density and line breaks are different as compared to Excel generated PDF
• Text is getting trimmed and overlapped while rendering spreadsheet to PDF
• Problems rendering chart to PDF
• Opening and saving the Excel file changes the trend lines
• Workbook save twice, the content saved second time will be different from the first time
• Issue with PageBreaks which are not sorted before saving to Excel file
• File corrupt if opened, saved, re-opened and saved by Aspose.Cells APIs
• Chart axis values changed after re-saving an XLS file
• Not getting accurate information about WordArt shape formatting from Aspose.Cells APIs
• Issue with embedded icon - not printing
• Specifying Custom Number Decimal and Group Separators for Workbook doesn't work
• Formula calculation result differs from Excel native calculation
• Checkboxes are not rendering correctly when using SheetRender.toImage() method
• Character orientation is different while rendering to PDF
• Some characters are missing or not pasted right in Excel to PDF conversion
• Some of the DataBar images are blank
• Bars of the graph not aligned properly with cells in PDF
• Misaligned bars after rendering spreadsheet to EMF
• Character spaces problem while rendering spreadsheet to PDF
• Background image is distorted or blurry in the output PDF
• Background image is stretched in output PDF
• Broken external formula references while using Cells.copyColumns
• Corrupted XLSX file after text replace
• Loss of text block in frenchCommonWords.xlsx
• Text Overflow check

Other most recent bug fixes are also included in this release.

Overview: Aspose.Cells for Android

Aspose.Cells for Android is a MS Excel spreadsheet component that allows programmer to develop android applications for reading, writing & manipulate Excel spreadsheets (XLS, XLSX, XLSM, SpreadsheetML, CSV, tab delimited) and HTML file formats without needing to rely on Microsoft Excel. It supports robust formula calculation engine, pivot tables, VBA, workbook encryption, named ranges, custom charts, spreadsheet formatting, drawing objects like images, OLE objects & importing or creating charts.
More about Aspose.Cells for .NET

• Homepage of Aspose.Cells for Android
• Download Aspose.Cells for Android

Set Default Font for Rendering Spreadsheets to Image & HTML Format inside .NET Apps

What’s new in this release?

We are pleased to announce the new release of Aspose.Cells for .NET 8.9.0. Aspose.Cells for .NET API has provided the ability to specify the default font name for rendering spreadsheets to image formats. The DefaultFont property is of type System.String with default value as null. The said property can be used when Unicode characters in the spreadsheet have not been formatted with appropriate font in the cell’s style, consequently such characters may appear as blocks in the resultant images. It is advised to set the DefaultFont property to MingLiu or MS Gothic to show Unicode characters. If the DefaultFont property is not set, Aspose.Cells for .NET API will use the system’s default font to show the Unicode characters. It has exposed the a new property for the HtmlSaveOptions class that allows to specify the default font name while rendering spreadsheets to HTML format. The default font will be used only when a particular font used to format some contents in the spreadsheet does not exist on the machine where conversion process has to take place. The default value of the property is null that means, the API will use the universal font which has the same family with the original font. Aspose.Cells for .NET API has exposed the Boolean type IsExcel2003Compatible property for the PivotTable class which allows to specify if a given PivotTable is Excel 2003 compatible for refreshing purposes. The default value of IsExcel2003Compatible property is true, that means a string must be less than or equal to 255 characters. If the string is greater than 255 characters, it will be truncated. If false, the aforementioned restriction will not be imposed. There are some important enhancements in this release, such as  expanding text from right to left while exporting spreadsheets to HTML, get the Release or Running Version of Aspose.Cells.GridWeb and add or Remove Context Menu Items in Aspose.Cells.GridWeb. We have handled a few exceptions regarding reading and writing Excel and HTML file formats. We have also handled an exception when calling Autofit operation on a worksheet. In this release, several important issues have been addressed. For example, issues around reading and writing Microsoft Excel file formats, copying worksheets, manipulating PivotTables, adding List Objects/Tables, converting spreadsheets to HTML files and vice versa, manipulating and rendering charts and shapes, rendering images from Excel worksheets, rendering images files from charts and exporting Excel workbooks to PDF format have been resolved. We have also enhanced the Aspose.Cells’ formula calculation engine and fixed a few issues in this regard. This release includes several enhanced features and bug fixes as listed below

• Support expanding text from right to left when exporting file to HTML
• Ability to set Default Font while rendering spreadsheet to HTML
• Ability to set Default Font while rendering spreadsheet to images
• Refreshing Pivot Table throws exception
• Excel file is not properly rendering into HTML file format
• Contents overlap while converting spreadsheet to HTML
• Pivot Field's dropdown is missing after re-saving XLSX as XLSB
• Spreadsheet becomes corrupted after re-saving XLSX as XLSB
• Refreshing and Calculating Data on existing Pivot Table generates corrupt Excel file
• Chart.ToImage is generating incorrect image
• Some text items are slightly truncated in the output HTML
• Problem exporting Excel to PDF with special characters in the header and footer
• Vertical alignment wrong when generating range to image using SheetRender.ToImage
• Aspose.Cells generated EMF shows incorrect axis labels when inserted into Word document and converted to PDF
• Less than single spacing doesn't export to PDF properly
• Chart's EMF generated under Session 0 does not display all the contents
• Chart.HasAxis is showing wrong value
• Empty PNG 0KB file generated while converting XLSX to HTML
• Cells.ClearContents removes the formula for the cells below the specified range
• Issue with Worksheet.Copy() - All comments after IV column are missing in the copied sheet
• Pictures in worksheets copied from an external XLSX are not sized the same as originals
• Copying workbook into new workbook produced unreadable content error
• TextBox in the chart is lost while copying Workbooks
• Chart colors are lost while copying workbook
• Formula results in "#NAME" error after copying the rows and calculating formulas
• Formula is replaced by 0 after copying the rows and calculating formulas
• The fill format of shape is lost when converting the file to HTML
• Printing zone is moved a bit using latest versions of the product
• Showing total for list object with only 1 record corrupts the workbook
• Incorrect ListObject size after ShowTotals set to false

Other most recent bug fixes are also included in this release

Overview: Aspose.Cells for .NET

Aspose.Cells is a .NET component for spreadsheet reporting without using Microsoft Excel. It supports robust formula calculation engine, pivot tables, VBA, workbook encryption, named ranges, spreadsheet formatting, drawing objects like images, OLE objects and importing or creating charts. You can also create Excel file using designer spreadsheet, smart marker or API and apply formulae and functions. It supports CSV, SpreadsheetML, PDF and all file formats from Excel 97 to Excel 2007.

More about Aspose.Cells for .NET

• Homepage of Aspose.Cells for .NET C#
• Download Aspose.Cells for .NET

Notebook to PDF Conversion, Adding & Removing Child Nodes from Notebook in Java Apps

What’s new in this release?

Aspose development team is very excited to announce the new release of Aspose.Note for Java 2.4.0. This month’s release of the API introduces new feature of read/write support for Microsoft OneNote Notebook file formats (.onetoc2). It also provides the enhancement of determining Microsoft OneNote document format for differentiating between OneNote and OneNote online file format. This month’s release now provides the capability to create OneNote notebook and save it to disc. The Notebook class provides the functionality of creating new Notebook and save it to disc or memory stream using the save method. Not only Users can create and save OneNote notebook files, users can also add and remove child nodes from a Notebook using the appendChild and removeChild methods. The API also introduces new feature of loading OneNote notebook files and export them to PDF format. In addition, a notebook can be exported to PDF with additional options as well for specifying page splitting algorithm. In addition to exporting document data to PDF, this month’s release also provides the capability of exporting document to image format. It also allows to set output image resolution and flattening parameters. The flattening option, if used, lets you export Notebook children to a single output directory. Aspose.Note supports Microsoft OneNote and OneNote online file formats; with the lateral having certain limitations such as lack of support for images and attachments in the document. With the provision of this new enhancement, user can pre-determine the document’s file format in order to be aware of these limitations. We are already working hard to implement the non-supported features for OneNote online file format. This month’s release also fixes a number of bugs that were either reported with the Java version of the API or were auto-fixed after auto-porting from the .NET version of the API. This further aid to the stability of the API. Bellows is the list of new and enhanced features included in this new release.

• Provide option for excluding document header name during Project conversion to HTML
• Performance is too slow with large number of tasks ~10K+
• PhysicalPercentComplete not saved in MPP file
• Predecessors information changed while loading and saving MPP (.NET)
• Custom Field marked as Loopkup while adding extended attribute to MPP file
• All tasks in Primavera XML file cannot be read
• Reading Project file raises Project Reading Exception
• Cropped image when converting project document to image with Vertical\Horizontal Resolution settings
• Setting Task Notes to Chinese not working

Overview: Aspose.Note for Java

Aspose.Note is a feature-rich Java class library that enables java applications to programmatically interact with OneNote documents without requiring MS Office OneNote having installed on the server. This Java API empowers developers to Create, Read, Export and Manipulate the contents of the Microsoft OneNote file format by working with attachments, text, hyperlinks, tables, tags and text styles. Easily extract images from OneNote documents and convert them to PDF, BMP, JPG, GIF and TIFF image formats.

More about Aspose.Note for Java

• Homepage of Aspose.Note for Java
• Download Aspose.Note for Java

Project Data Export to HTML & Performance Improvement While Creating Tasks using .NET

What’s new in this release?

We are proud to announce the new release of Aspose.Tasks for .NET 9.5.0. This month’s release includes minor enhancements related to API functionality of exporting project data. It also includes performance improvement while creating large number of tasks. In addition, a number of reported bugs have been fixed in this month’s release that further improves the overall stability and functionality of the API. Exporting project data to HTML included document header in output Title as well as page header. This month’s release provides control to avoid exporting this information to output HTML file if not required. The IncludeProjectNameInTitle and IncludeProjectNameInPageHeader properties can be used to achieve this.  These properties are set to true by default. This month’s release brings performance improvement while creating large number of tasks using the API. The automatic calculation mode of the API calculates each and every field of a task upon adding new tasks. This can be taken care of by using the Manual Calculation mode of the API. We have further improved the manual calculation mode so that it takes less time while creating large number of tasks such as up to 10,000. This month’s release also fixes a number of bugs reported by our valued customers. These include issues related to loading Primavera project files, change in predecessor’s information while loading and saving MPP file, and setting task notes to Chinese language. This release includes plenty of new features as listed below

• Provide option for excluding document header name during Project conversion to HTML
• Performance is too slow with large number of tasks ~10K+
• PhysicalPercentComplete not saved in MPP file
• Predecessors information changed while loading and saving MPP (.NET)
• Custom Field marked as Loopkup while adding extended attribute to MPP file
• All tasks in Primavera XML file cannot be read
• Reading Project file raises Project Reading Exception
• Cropped image when converting project document to image with Vertical\Horizontal Resolution settings
• Setting Task Notes to Chinese not working

Other most recent bug fixes are also included in this release

Overview: Aspose.Tasks for .NET

Aspose.Tasks is a non-graphical .NET Project management component that enables .NET applications to read, write and manage Project documents without utilizing Microsoft Project. With Aspose.Tasks you can read and change tasks, recurring tasks, resources, resource assignments, relations and calendars. Aspose.Tasks is a very mature product that offers stability and flexibility. As with all of the Aspose file management components, Aspose.Tasks works well with both WinForm and WebForm applications.

More about Aspose.Tasks for .NET

• Homepage of Aspose.Tasks for .NET
• Download Aspose.Tasks for .NET

Render PDF Document Layers Separately in PDF to HTML & PDF to PNG Conversion using Java

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Pdf for Java 11.7.0. This version includes PDF to PNG conversion performance enhancement in addition to the improvements/enhancements made in its equivalent .NET version.  We have also fixed number of issues in this release, reported by our customers in previous releases. Some of these are PDF to HTML, HTML to PDF, SVG to PDF, PDF to PDF/A, PDF to DOC(X), PDF to Image and some others. A PDF document can contain different data layers and can have requirement to render each layer separately as HTML Layer element. We have introduced this feature in current release, we need to set ConvertMarkedContentToLayers property to control the layers rendering in PDF to HTML conversion as following. We have introduced a new value AutoFitToWindows in ColumnAdjustment Type Enum in current release. It will adjust table columns to fit to windows. Sometimes we have requirement to create a Graph Object with dashed line. Now, we can easily achieve the requirement with GraphInfo object. There are some important improvements included in this release, such as XPS to PDF conversion performance & PDF to PNG conversion performance are Improved. Some important improved features included in this release are given below

• PDF to PNG - conversion process takes too much time
• PDF to HTML - Lines width issues
• HTML to PDF results into incorrect output
• PDF to PDF/A_3a - Resultant file is not PDFA compliant
• PDF to PDF/A - Resultant file is not PDFA compliant
• HTML to PDF - Formatting issues in resultant file
• PDF to HTML - Exception during conversion process
• API throws NullPointerException upon page copy   Bug
• PDF to DOC - Blank page being appended and contents in footer are missing
• PDF to PDFA conversion throws internal Exception
• SVG to PDF - SVG image is not appearing in PDF file
• PDF to DOCX - Field value appears in subsequent line
• HTMl to PDF - Exception during conversion
• HTML to PDF: formatting issue
• PDF to DOCX - Contents are not appearing properly
• PDF to HTML: extra white lines on background - regression
• Exception while loading PDF file in multiple threads
• PDF to PDFA2a - compliance failure
• PDF to PDFA3a - conversion fails compliance
• HTML to PDF - Page contents are overlapping eachother
• PDF to PDF/A - Header in Resultant file gets corrupted
• Redaction throws NullPointer Exception
• HTML to PDF is not working in multithreading
• Exception during PDF printing
• PDF to HTML: some text is missing in resultant HTML
• PDF to PDFA2b: Text overlapping and spacing issue
• PDF to PDFA1b: resultant PDFA document failing the compliance
• HTML to PDF: incorrect text position
• PDF to DOCX - Tab indent is being ignored

Overview: Aspose.Pdf for Java

Aspose.Pdf is a Java PDF component to create PDF documents without using Adobe Acrobat. It supports Floating box, PDF form field, PDF attachments, security, Foot note & end note, Multiple columns document, Table of Contents, List of Tables, Nested tables, Rich text format, images, hyperlinks, JavaScript, annotation, bookmarks, headers, footers and many more. Now you can create PDF by API, XML and XSL-FO files. It also enables you to converting HTML, XSL-FO and Excel files into PDF.

More about Aspose.Pdf for Java

• Homepage of Aspose.Pdf for Java
• Download Aspose.Pdf for Java

Apply Font Settings for Metafiles (EMF) & Convert SVG to Raster Image using Java

What’s new in this release?

Aspose development team is pleased to announce the new release Aspose.Imaging for Java 3.7.0. The major development in this release is support for Scalable Vector Graphics image. Support to apply font setting for metafiles (EMF) has also been incorporated in this release. Aspose.Imaging for Java now supports the SVG image format (.svg). SVG stands for Scalable Vector Graphics. Aspose.Imaging for Java provides the SvgImage class to load SVG files and same can be used to convert the SVG to raster formats. Using Aspose.Imaging for Java API, developers can apply font settings for metafiles (EMF). Following is the code demonstrates how to specify font folder settings for EMF image while converting it to PNG image. Some important enhancements have been introduced in this release, such as, Process of loading WMF files and Aspose.Imaging drawing engine has been improved. Calculation process of Horizontal and Vertical resolution values has been improved. The main new and improved features added in this release are listed below

• MetafileComments class disappears in the latest release. This class was present in the old versions
• loading WMF file using Aspose.Imaging is showing incorrect results with compare to a 3rd party image viewer
• Ability to add / import image to PSD layer
• Implement support for Scalable Vector Graphics (SVG) 1.1 format support
• Cropping for emf files
• Support FontSettings for CAD and Emf formats
• Aspose.Imaging drawing engine stage by stage introduction
• Implement Dicom loader
• Aspose.Imaging is rounding up the Horizontal and Vertical resolution values

Overview:Aspose.Imaging for Java`

Aspose.Imaging for Java is an image processing & manipulation component that allows developers to create, edit, draw or convert images in their Java application. It allows developers to convert images to BMP, JPEG, TIFF, GIF, PNG & PSD formats. It draws images using advanced features like Graphics & GraphicsPath. The drawing feature is useful for adding shapes, building up new images or adding watermarks to images. It works well with both web & windows applications. It supports JDK 1.5 & above.

• Homepage of Aspose.Imaging for Java
• Download Aspose.Imaging for Java

Add Videos from YouTube & Improved Presentation Document Properties using .NET

What's New in this Release?

We are happy to share the announcement of Aspose.Slides for .NET 16.6.0.  This release has come up with some new features along with resolution of pending issues incurring in API. We have improved the presentation Documentation properties management in this product release. Now you may work with document properties in a better way. For more about how to interact with document properties, please refer to documentation article, Working with Advanced Document Properties for further reference. Now, you can also add the video from web source like YouTube inside your presentation. Please refer to documentation article, Adding Video Frame with Video from Web Source for further reference. We have improved the text management in this product release and have resolved certain pending issue like improper fonts, wrong alignment, improper and wrong bullets, wrong slide numbering and improper bordering. We have also rectified issues related to shapes like Trapezoid and oval that were getting improperly rendered in saved presentations. We have also addressed the issues related to shape gradient effects and fill overlay effects. The issues related to charts and their elements rendering have been taken care of in this release. Moreover, working with tables and SmartArt shapes have been improved as well after resolution of certain incurring issues. The support for generating of slide images, PDF and Tiff has also been improved in this release for different shape elements inside presentation decks. The presentation access and saving issues have been rectified for many presentation decks that resulted in exceptions. This list of new, improved and bug fixes in this release are given below

• Restoring support for read only document properties to make changes
• Inserting video from web in presentation
• Implement FillOverlay effect             Feature
• Empty tiff is generated for exported Tiff
• Chart data fail to open in Edit mode on saving presentation
• Incorrect rendering of EA portions (shift to the right)
• Value cannot be null on saving PPTX presentation
• Value does not fall in range exception on loading presentation
• Extra digits are added to the page number footer after saving the PPT
• The title's font is changed after saving a PPT
• An oval shape is changed to rectangle after saving a PPT
• Shape gradient fill was changed in a saved PPT file
• Bullets are added after loading and saving a PPT
• A number list is changed to bullet list on saving PPT
• Presentation background gets changed in saved presentation
• An arrow shape becomes a triangle after loading and saving a PPT
• PPT title text order is reversed after loading and saving
• Images are missing in saved presentation
• Text Alignment gets changed in saved presentation
• Trapezoid shapes became triangle on saving presentation
• Bullets and arrow shapes are changed after Loading and Saving a PPT
• Images are mirrored in exported PDF
• Chart unable to plot on Primary X-Axis and Secondary Y-Axis
• Drawing text has wrong size in a thumbnail
• Animation getting changed on saving presenatation
• Extra border appears around metafile in generated PDF
• Effect getting changed in the design when saving presentation
• Throw proper exception when creating presentation from end-of-stream
• Index Out of Range exception on exporting presentation to SWF
• Problem with space between bullets and text
• Optimizing memory consumption while rendering PDF
• Exception while getting properties of a table
• Support for nested style tags with AddFromHtml method
• Problem with generated pdf
• Bigger image generated in svg and pdf
• Vertical setting problem after AddTextFrameForOverriding method
• Numbering indentation/space trimming issue
• Font height returned incorrectly
• Incorrect bullet points on load and save presentation
• Incorrect bullets on presentation load and save
• Loading a PPTX is slow because of SortedDictionary
• Date format is changed on PDF rendering
• Saving potx as PPTx gives repair message
• Argument exception on PdfNotes saving
• Wrong bullet type returned for the paragraph text
• Error C2686 in compiling call to aspose.slides (15.2.0.0) with C++/CLI
• Font Parsing exception on loading presentation         Bug
• Font parsing exception on accessing the presentation
• Font parsing exception on accessing the presentation
• Unexpected font parsing exception when opening a PPTX file
• Bullets are improperly rendered on slide with Arabic text
• Unexpected font parsing exception while opening a PPTX file
• Extra Bullet is added after cloning the slide
• End of Stream Exception on accessing the presentation
• Incorrect bullet information on paragraph while reading the PPT file
• Improper gradient rendering in generated PDF
• PPT to PDF: Faint images in PDF after conversion
• Bullets are lost when saving PPT as PPTX
• Numbered bullets changed to symbol in generated thumbnail
• Bullet offset changes on saving presentation
• The numbered bullet changed to symbol when slide thumbnail is created
• Bullets character is improperly rendered in generated presentation
• Bullets are improperly rendered in converted PPTX and exported PDF
• Bullet character is not rendered in generated PDF
• Custom bullets failed to render in exported PDF

Other most recent bug fixes are also included in this release

Overview: Aspose.Slides for .NET

Aspose.Slides is a .NET component to read, write and modify a PowerPoint document without using MS PowerPoint. PowerPoint versions from 97-2007 and all three PowerPoint formats: PPT, POT, PPS are also supported. Now users can create, access, copy, clone, edit and delete slides in their presentations. Other features include saving PowerPoint slides into PDF, adding & modifying audio & video frames, using shapes like rectangles or ellipses and saving presentations in SVG format, streams or images.

More about Aspose.Slides for .NET

• Homepage of Aspose.Slides for .NET
• Downlaod of Aspose.Slides for .NET

Updated Configuration Option to Control Table Position & Hyperlinks Export in Word Docs

What’s new in this release?

The long awaited version of Aspose.Words for JasperReports 2.7.3 has been released. This release also includes information from the previous versions. We are pleased to announce a new release of Aspose.Words for JasperReports that includes fix of issue related to section breaks in exported documents. We are pleased to announce a new release of Aspose.Words for JasperReports that includes fix of issues related to hyperlinks and subreports in exported documents. We have introduced a new configuration option USE_POSITIONING_TABLES to control table position. By default, its value is false. This means that Aspose Words for JasperReports will try to avoid positioning tables where possible. However, you can enable this option (set to true) if you need to force usage of positioning tables (for example, for complex reports with hierarchy of subreports, frames etc). The list of new & improved features in this release are listed below

• Position of Section break (new page) is incorrect in output Docx/Doc
• Hyperlinks are not exported in output Word document
• Subreport contents are exported incorrectly in Docx
• java.lang.NullPointerException is thrown while exporting list of .Jrprint files to Doc/Docx

Starting from release 1.9.0 there are now several versions of the JAR library (this is necessary for better support of older versions of JasperReports):

• for JasperReports 5.6.0 … 6.2.0 (aspose.words.jasperreports-6.2.0.jar)
• for JasperReports 4.7.0 … 5.5.0 (aspose.words.jasperreports-5.5.0.jar)
• for JasperReports 3.7.2 … 4.5.0 (aspose.words.jasperreports-4.5.0.jar)
• for JasperReports 3.7.1 and lower (aspose.words.jasperreports-3.7.1.jar)

Please copy only one jar library according to the version of installed JasperReports.

Overview: Aspose.Words for JasperReports

Aspose.Words for JasperReports makes it possible exporting reports from JasperReports and JasperServer to Microsoft Word document (DOC), Office Open XML (OOXML, DOCX), Web page (HTML) and plain text (TXT) formats. It is written purely in Java and is provided as a single JAR file that can easily be deployed on the machines running JasperReports or JasperServer. Aspose.Words for JasperReports exports flow layout documents that are easy to further edit in Microsoft Word, if necessary.

More about Aspose.Words for JasperReports

• Homepage of Aspose.Words for JasperReports
• Download Aspose.Words for JasperReports

Aspose.Newsletter August 2016: Manipulate OneNote Files in .NET, Java Apps & Other News

Aspose Newsletter for August 2016 has now been published that highlights all the newly supported features offered in the recent releases. It also includes information about
manipulating OneNote file without office automation, working with CAD formats like DWG and DXF, OneNote Notebook TOC Format Support, Support for Two New Barcode Formats in the Latest release of Aspose.Barcode for .NET, Convert Excel Worksheet or Workbook to XPS Formats, Manipulating Calendar Exceptions in Microsoft Project Files and much more.


Want to Manipulate OneNote file without Office Automation?

You can do that with Aspose.Note from within all types of .NET and Java applications. Render text and images from OneNote files into a variety of image formats; navigate through OneNote object model; replace and insert text and other elements inside an OneNote file. Let Aspose APIs make your work easier! Download a free Trial

Introducing Aspose.CAD for Java API to work with CAD formats like DWG and DXF

Aspose.CAD for .NET has been around for some time now. It's time for Java developers to process CAD formats like DWG and DXF in their Java applications with the same great ease and reliability as our other APIs. The first version plans to include reading CAD formats and exporting them to popular formats like BMP, JPG, GIF, PDF, and TIFF. Check out the blog post for more details OneNote Notebook TOC 

Format Support is Now Available in Aspose.Note for Java

Aspose.Note for Java now supports OneNote Notebook TOC format (.onetoc2). Along with manipulating OneNote files, you can now also work with TOC file format in your applications. There are various other new features and enhancements in the latest version as well. Check out the blog post for this new format and other features.
 
Support for Two New Barcode Formats in the Latest Aspose.Barcode for .NET

Aspose team has added two new barcode formats (DutchKix and DotCode) along with many other barcodes already available in Aspose.Barcode for .NET. User can both create and read both of these new barcode types using the latest version. Check out the blog post for details and more enhancements.

Convert Excel Worksheet or Workbook to XPS Formats using Aspose.Cells for Java
  
An XPS document consists of structured XML which is a subset of XAML. The XML helps to define layout of the document and visual appearance. This format also helps to incorporate vector graphics elements in the document. The Aspose.Cells for Java allows users to convert a single worksheet or a complete workbook to XPS format. Check out documentation to learn more and view example code

Manipulating Calendar Exceptions in Microsoft Project Files using Aspose.Tasks for .NET

When planning a project using Microsoft Project, along with defining working and non-working days, it's important to setup exceptions. This can be achieved programmatically using Aspose.Tasks for .NET. You can add, remove, or retrieve calendar exceptions from the Microsoft Project files along with defining weekdays or occurrences of exceptions. Explore these features along with code samples in the documentation.

Updates about new Product Releases

1. Aspose.Total for .NET - a compilation of our latest .NET products.
2. Aspose.Cells for .NET 8.9.0 Support setting default font while rendering spreadsheet to HTML and images
3. Aspose.Words for .NET 16.6.0- Support of ISO 29500 strict OOXML format, fast extraction, dynamic insertion using LINQ reporting engine
4. Aspose.Pdf for .NET 11.9.0 – Replace missing font with alternative font while converting from PDF to PDF/A.
5. Aspose.Slides for .NET 16.6.0 – Inserting video from web in presentation and support for FillOverlay effect
6. Aspose.Email for .NET 6.7.0 - Auto determination of SSL mode for servers supported
7. Aspose.BarCode for .NET 8.0.0 - Added new BarCode types: DutchKix and DotCode.
8. Aspose.Imaging for .NET 3.8.0 - Work with WMF metafiles and get last modified date of raster image
9. Aspose.Total for Java – a compilation of our latest Java products.
10. Aspose.Words for Java 16.6.0 - Support of ISO 29500 strict OOXML format, fast extraction, dynamic insertion using LINQ reporting engine
11. Aspose.Cells for Java 8.9.0 - Support setting default font while rendering spreadsheet to HTML and images.
12. Aspose.Pdf for Java 11.9.0 – Replace missing font with alternative font while converting from PDF to PDF/A.
13. Aspose.Slides for Java 16.5.0 - Support for rendering hidden slides in PDF and PictureBullet for PPTX format.
14. Aspose.Email for Java 6.7.0 – Auto determination of SSL mode for servers supported
15. Aspose.Total for Android – all the latest versions of our Android APIs.
16. Aspose.Total for SharePoint – a compilation of our latest SharePoint products.
17. Aspose.Total for Reporting Services – a compilation of our latest Reporting Services products
18. Aspose.Total for JasperReports – The latest versions of our JasperReports products.

Supporting User Groups and Conferences
Aspose is sponsoring a number of user groups and upcoming events, including:

• 1st Aug: Queensland ALM Meetup - Australia
• 1st to 5th Aug: NDC Sydney - Australia
• 5th Aug: Tulsa TechFest - US
• 10th Aug: Adelaide .NET User Group - Australia
• 13th Aug: DDD Melbourne - Australia
• 27th Aug: DDD Perth - Australia

Would you like us to sponsor your user group? Get in contact at user.groups@aspose.com
Collect your copy of Aspose Newsletter, August 2016 edition

• Collect the English version of this newsletter