Thursday, September 29, 2016

Identify Embedded Message Attachment & Mark Outlook PST Items using Custom Properties using Java

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Email for Java 6.9.0. This month’s release includes the same new features as were part of the equivalent .NET version of the API. Specifically, it provides the capability to mark items in-place in a PST file and detect if an attachment of a message is an embedded message. It also contains a number of bug fixes that further improve the API functionality. This release enhances the capability of updating PST Items in-place using custom properties. The API, earlier, supported updating common properties of PST items such as subject, recipients, senders, etc. With this enhancements, an item in a PST can be attached a custom property for marking it with specific information. The feature doesn’t require to extract the complete item first. Instead, the items can be marked in-place using the FolderInfo and PersonalStorage classes. This month’s release also enhances the Attachment class by providing the capability to identify attachment as embedded message. The isEmbeddedMessage method returns true if the embedded attachment is another message file. Aspose team has also fixed a number of bugs in this month’s release. This further brings stability to the API functionality and surety of the expected behavior in these cases. The main improved features & bug fixes added in this release are listed below
  • Marking Items in-place within a PST
  • EWS: Provision of synching folder own name etc
  • Provision to identify embedded (nested) messages in TNEF messages
  • Implement RTF Extension Algorithm to properly display body of message after converting from eml to msg
  • Convert inline attachments from RTF body to inline images in HTML body at MSG to EML conversion
  • Improve log methods to decrease delay which depends on log operations
  • Move all external maven dependencies to local repo
  • Empty message Id retrieved while using ImapClient.ListMessages()
  • IMAP Idle command stops receiving events after some times
  • Adding nested message to EML message in TNEF format (winmail.dat)
  • Accepting Task sent by Aspose.Email crashes MS Outlook
  • EML to MHTML: Empty output
  • MSG->MSG inserts spaces between paragraphs
  • RTF MSG to MHTML: Font styles are not retained
  • Empty Message body when Saved email using Aspose.Email API is sent using MS Outlook
  • Resaving MSG file using MapiMessage destroys Ole Object in MSG
  • Loading Large EML raises System.OutOfMemory Exception in x86 settings
  • EML to MHT raises Exception
  • Exception while using IEWSClient.CreateContact with MapiContact and Contact
  • Exception while loading EML to MailMessage
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.

More about Aspose.Email for Java

Wednesday, September 28, 2016

Read/Write Values from ActiveX ComboBox Control & Set Class Identifier for OleObjects using .NET

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Cells for .NET 9.0.0. This release includes some new features and other enhancements with critical bug fixes. Aspose.Cells for .NET API has exposed the ChartPoint.IsInSecondaryPlot property with this release. Boolean type property can be used to detect if a ChartPoint resides on secondary plot or not. The Aspose.Cells APIs can be used to insert and/or manipulate existing ActiveX controls. One such example is an ActiveX ComboBox which can now be created as well as manipulated with Aspose.Cells for .NET APIs. This release has exposed a new property which can be used to retrieve or set the class identifier for an OleObject. Please note, the class identifier decides which application is required to load the embedded resource/OleObject and how. For instance, a PPT file can be embedded in a spreadsheet with 2 different views, that is; presentation view or slide view, whereas both views have different class identifier values. The API has exposed the Shape.TextOptions property which can be used to control all aspects of the shape’s textual contents such as font style, color, font weight and so on. This release has fixed a few critical bugs as well as enhanced its core for more stability. There are some worth mentioning enhancements, such as loading the Workbook with specific System Culture Info, Use Aspose.Cells.GridDesktop control in WPF Application, enhanced the Aspose.Cells’ Calculation Engine for performance considerations, improved HTML import engine for cell borders as well as cell text alignment and handled a few exceptions such as NullPointerException and Invalid text of the defined name.” for certain scenarios. In this release, several important issues have been addressed. For example, issues around reading and writing Microsoft Excel file formats, rendering to HTML file format, 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
  • Read/write values from/to ActiveX ComboBox control
  • Using Aspose.Cells.GridDesktop in WPF application
  • Import of HTML fails when script tag uses CDATA
  • Contents are missing while converting HTML to XLSX
  • Unable to convert background or foreground colors from HTML
  • Error message is shown when double-clicking on any value of the PivotTable in the output file
  • The resultant file becomes corrupted when open and save the XLS file
  • Final XLSX file has a lack of the caption styles while these are present in the input XLSX and intermediate HTML
  • Issue with Spreadsheet to HTML conversion: STYLE tag between BODY and HTML tags
  • ICustomFunction doesn't work with [@columnName]
  • Wrong SUM displayed when calculating formulas
  • API incorrectly calculates the formula value as compared to MS Excel
  • Wrong calculation of the cell value
  • Wrong value from cell when calculating formulas
  • PDF result does not match with Excel for printing title rows
  • The data is hidden in the conversion result of PDF
  • Rendering to image file fails for a worksheet
  • Spreadsheet to XPS: Process never completes and takes too much memory
  • Sparklines are not rendered right while rendering spreadsheet to PDF/image
  • Chart.Calculate() method spoils the chart image
  • Saving to memorystream (SpreadsheetML), the process is hanged and takes lots of time
  • Unhiding the row hidden by Aspose.Cells does not work properly in Microsoft Excel
  • Picture formula is gone after removing and reinserting the picture
  • Re-embedding the presentation slide in XLS results in presentation view upon double clicking
  • Line with arrow head isn't rendered completely in XLSX & PDF formats
  • Printer settings are changed on opening and re-saving the source XLS file
  • "pane" xml within "customSheetView" xml not being replicated from designer spreadsheet
  • The Y and X Axis of the graph become bold after loading and saving an XLS file
  • The text-size of chart's vertical axis labels is changed after loading and saving XLS file
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.

Tuesday, September 27, 2016

New Config Option for Footer Optimization Distance in Aspose.Words for JasperReports 2.8.1

What’s new in this release?

The long awaited version of Aspose.Words for JasperReports 2.8.1 has been released. It includes new configuration option to optimize footer distance. By default, Aspose.Word for JasperReports tries to optimize footer contents for better fitting footer on the page. This optimization takes place when a bottom-most page element is too low on page by a) decreasing font size of last paragraph break of the footer and b) decreasing footer distance. If you do not like the view of footers, you can disable this footers optimization by setting OPTIMIZE_FOOTERS parameter to false. Users can also set explicit minimal distance between bottom-most element and bottom page margin. This is controlled by OPTIMIZE_FOOTER_DISTANCE parameter. By default, its value is 12.0. However, users can set any value between 12.0 and 36.0. Therefore, if the distance between bottom margin of the bottom-most element and page bottom margin is less or equal to this parameter value – then footer is optimized, otherwise nothing happens.  The list of new & improved features in this release are listed below
  • Introduce new config option for footer optimization distance
  • Compatibility Mode in Word 2010/2013
  • 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 6.3.0 and higher (aspose.words.jasperreports-6.3.0.jar)
  • 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.

Monday, September 26, 2016

Add ActiveX Controls into Visio Drawing & Retrieve Inherited Fill Data of a Shape using .NET

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Diagram for .NET 6.8.0. The new version of the API allows developers to insert an ActiveX control in their Visio drawings and select or clear the CheckBox in Color column of the layer. Developers can also retrieve inherited fill data of the Visio shape. The recent version also covers a number of regular bug fixes and enhancements. Developers can install an Aspose.Diagram Nuget package in their .NET applications because Aspose team publishes each version as a NuGet package on the NuGet gallery. An ActiveX control is a software component that adds functionality to an existing Visio drawing. Microsoft Visio includes several pre-built ActiveX controls on the Developer tab, including a label, textbox, command button, image, scroll bar, checkbox, combobox and listbox etc. Using Aspose.Diagram API, developers can now add ActiveX controls in their Visio drawing by specifying width, height and location. Layers in Microsoft Visio provide a way to change properties of all shapes that have been assigned to a specific layer. Developers can assign a color to the layer using Aspose.Diagram API. They may also show or hide the color of the layer by selecting or clearing the checkbox in the color column of the layer. In the Microsoft Visio, shapes can inherit StyleSheet and PageSheet elements. Using Aspose.Diagram API, developers can now retrieve inherited fill data of the Visio shape. The InheritFill property of the Shape class contains the fill formatting values for the shape inherited by the parent style and the master shape. This version also addresses the issues of missing shapes, tables and icons, the retrieval of the connections, preserve DPI in the output pictures, additional shapes, retrieve direction of the dynamic connectors and accuracy in alignment of the shapes. These enhancements and bug fixes improve performance and accuracy of Aspose.Diagram API.  Here is the list of important enhancements and bugs fixes in the new version.
  • Add support of inserting ActiveX controls in the Visio Page.
  • Add support to set color checkbox of the layer.
  • The shapes are missing from VSDX drawing.
  • The small icons of the tables are missing on saving a VSDX to PDF.
  • Incorrect retrieval of the Connects from a VSD
  • An incorrect DPI is being set on saving in the TIFF.
  • The connection of the dynamic connector is not being preserved on grouping shapes.
  • An extra square is added around the circle shape on converting a VDX to PDF.
  • Can't copy a Visio page in the VSDM
  • Can't set headers and footers of a VSDX diagram
  • Microsoft Visio 2013 viewer does not display a VSDX diagram.
  • A table is missing on converting a VSDX to PNG.
  • Incomplete rendering of a dynamic connector in the VSDM diagram
  • A null reference error occurred while inserting a picture.
  • Retrieves a reverse direction of the connector from a VSD diagram
  • The text alignment problem on converting a VSDX to PDF
  • The text alignment and formatting problems on converting a VSDX to PDF
  • The bold text formatting is not being preserved on converting a VSDX to PDF
  • Returns incorrect connections, while retrieving from a VSD
Overview: Aspose.Diagram for .NET 

Aspose.Diagram is a class library for working with MS Visio files & is a pure .NET alternate for MS Visio Object Model.It enables developers to work with VSD & VDX files on ASP.NET web applications, web services & Windows applications. It makes use of the advanced functionality of Visio's services to manipulate Visio docs on a server. Developer can open files & manipulate the elements of the diagram, from lines and fills, to more complex elements, and then export to native Visio formats or XML.

Sunday, September 25, 2016

Load Mobi (Mobipocket) Documents & Add NEXT Fields to LINQ Reporting Engine in 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.8.0. This month’s release contains over 68 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, Support Loading of Mobi (Mobipocket) Document,    Added New Base Class FixedPageSaveOptions for all Fixed Page Formats e.g. PNG, PDF, Hijri/Lunar, Hebrew Calendar Date Field option supported, The Analogue of NEXT Field is Added to LINQ Reporting Engine, Performance Optimization of UpdateFields and ExecuteWithRegions, added HtmlLoadOptions.SupportVml Public Property, added HtmlSaveOptions.ExportTextBoxAsSvg Public Property, HtmlLoadOptions Public Class is Introduced and  changes in Save Options of Fixed Page Formats. Aspose team has added the HtmlLoadOptions.SupportVml property in this release to specify HTML parser to parse conditional comments exactly like <!–[if gte vml 1]> and not to parse conditional comments exactly like <![if !vml]>. It has added the HtmlSaveOptions.ExportTextBoxAsSvg property in this release to control how textboxes represented by Shape are saved to HTML, MHTML or EPUB. It has introduced new public class HtmlLoadOptions in this release. This class is a subclass of LoadOptions and should be used instead of LoadOptions whenever specific options are needed to be set when loading HTML document. Base property LoadOptions.WebRequestTimeout is marked as obsolete and will be removed in several releases. If users need to specify web request timeout use HtmlLoadOptions.WebRequestTimeout property. Now all save option classes of fixed page formats (HtmlFixedSaveOptions, ImageSaveOptions, PdfSaveOptions, PsSaveOptions, SvgSaveOptions, SwfSaveOptions, XamlFixedSaveOptions and XpsSaveOptions) are inherited from the new public abstract class FixedPageSaveOptions. The MetafileRenderingOptions property has become available in the SwfSaveOptions class. Jpeg quality was 100 for the XAML and XPS formats in the previous version. Now its default value is 95 to unify with the other formats (except PDF). ASpose team has introduced NEXT Field in LINQ Reporting Engine to force movement to next item within Data Band. Please refer to documentation article “Forcing Movement to Next Item within Data Band”. The list of new and improved features added in this release are given below
  • Consider exporting editable TextBox Shape to HTML
  • root/ Support loading of Mobi (Mobipocket) documents
  • Add support of Next field in Linq Reporting Engine
  • Improve Inline.Font.Hidden property performance
  • Out of memory exception occurs during rendering to HTML
  • Timeout was reached upon rendering to PDF
  • Docx to Doc conversion takes much time      Performance
  • Aspose Words 16.6 UpdateFields() and ExecuteWithRegions() Performance problem
  • List items are rendered incorrectly.
  • Shape has wrong position after export to HTML
  • Incorrect generic font name is exported to EPUB for a missing font
  • Tables layout corrupted during open/save a DOC
  • Problem converting DOC to PDF with transparent image inside doc
  • List numbers are changed after re-saving RTF
  • Rotated image on Linux (Mono) during DOCX to HTML conversion
  • Space after paragraph disappears in AW pdf, docx output.
  • Problems in arabic language direction during HTML to DOCX conversion
  • Doc to Pdf conversion issue with GroupShape rendering
  • The rule "Allow hanging punctuation" is processed improperly if a line ends by several spaces.
  • Mismatch in table styles when the docx converted to pdf
  • The ROUND function works incorrectly with negative arguments
  • Unnecessary text appears after re-saving mhtml        Bug
  • Date field not transformed correctly if used Hijri/Lunar Calendar
  • Chinese words are rotated in HtmlFixed format        Bug
  • document.UpdatePageLayout throws ArgumentOutOfRangeException
  • LayoutCollector.GetEndPageIndex throws InvalidOperationException
  • Last page missing when appending document
  • Bar chart labels overlap bars in the PDF
  • WCharts Leader lines are not rendering correctly in PDF
  • Generated html has white font color and misplaced images
  • Hyperlink.Result update => lost link formatting (font size, link color)
  • Few words show as bold incorrectly in the PDF output        Bug
  • ListLabel.LabelValue is rendered incorrectly in Odt and Pdf
  • WDocx to pdf conversion issue with chart rendering
  • Document.UpdateFields does not update TOC field's number
  • Hebrew date field renders incorrectly in Pdf
  • WORDSNET-14017 '::after' pseudo-element is imported incorrectly from HTML
  • Comments numbering are changed when show revision in the balloons
  • When Chart object in Word document is converted to .jpg image, highest value in axis is different
  • Consider SpanFormField as RTL when the field start marker is RTL
  • /vml/ Shapes are laid out incorrectly in DOC on HTML import
  • RTL text of HTML Fixed Page document is reordered when copied to Clipboard
  • Formula (Equation.DSMT4) background color is lost after conversion from Docx to HTML  
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.

Thursday, September 22, 2016

Working with OneNote Page Revision Information & Enhanced Saving Page History 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.5.0. This month’s release incorporates new features working with revision and history information of a page in OneNote documents. It also addresses a number of API issues related to functionality that have been fixed now. This new feature lets developers working with the page revision information of a document. It allows developers to read as well write the revision information to a document’s page. Aspose.Note API already provides support for working with Page history in a document. This month’s release brings further enhancements to this capability by providing the facility to rolling back to previous page version, pushing current page version to page history and modifying page history. Rolling Back to Previous Page Version lets the API users to roll back to a previous version of the API by getting the last version from the page’s history. The Pushing Current Page Version to Page History facility allow the current page version of the page can be included in the history collection by using the Page.clone method.The Modifying Page History feature allows modifying the information related to a page history such as title and author. This month’s release also fixes a number of bugs that were reported with the latest version of the API. This further brings stability to the API functionality. Bellows is the list of new and enhanced features included in this new release.
  • Implement saving document history to *.one format.
  • Add revision info to the document's page type.
  • MD5 check error for OneNote 2016 format.
  • Fix bug related to possible empty NotebookManagementEntityGuid in the PageSeries node.
  • Last subpage is in incorrect position after opening and then saving document.
  • Pages with subpages which we create cannot be collapsed by MS OneNote.
  • Loading attached OneNote documents raise exception.
  • Exception "An item with the same key has already been added" raised while loading the attached one note file.
  • FileCorruptedException during parsing of sample file.
  • Failure to generate output files if path is the same as execution folder.
  • Inconsistent file names while exporting flattened notebook.
  • Notebook's structure is changed while saved with NotebookSaveOptions.Flatten.
  • Incorrect pages in Page History.
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.

Wednesday, September 21, 2016

Detect Embedded Message in MIME Message & Update Messages In-Place in PST using .NET

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Email for .NET 6.9.0. It includes new feature of marking items in-place in a PST file. It also includes enhancement for syncing Exchange server’s folder information and detecting embedded message type using the MailMessage API. In addition, it includes a number of bug fixes that brings further stability to the API functionality. This new feature provides the capability to update certain properties in a message file that could be lateral used to determine the marked messages. This can be achieved with the help of custom properties set on message files. The ChangeMessages and ChangeMessage introduced respectively by the FolderInfo and PersonalStorage classes can be used to achieve this. Aspose documentation article, Updating Custom Properties on Messages in PST file, demonstrates the usage of this new feature. It also includes a new feature of detecting an attachment for embedded message in a MIME message. The IsEmbeddedMessage property of the Attachment class provides the capability to achieve this. This release further enhances the functionality of synching folder items on Exchange server. The feature of synching folder contents was supported earlier. However, this month’s release further enhances the functionality by synching the folder name and properties as well. It also fixes a number of bugs that were reported with the earlier version of the API. Fixing of these issues further enhances the quality of API functionality. The main bug fixes & improved features added in this release are listed below
  • Marking Items in-place within a PST
  • EWS: Provision of synching folder own name etc
  • Provision to identify embedded (nested) messages in TNEF messages
  • Implement RTF Extension Algorithm to properly display body of message after converting from eml to msg
  • Convert inline attachments from RTF body to inline images in HTML body at MSG to EML conversion
  • Improve log methods to decrease delay which depends on log operations
  • Empty message Id retrieved while using ImapClient.ListMessages()
  • IMAP Idle command stops receiving events after some times
  • Adding nested message to EML message in TNEF format (winmail.dat)
  • Accepting Task sent by Aspose.Email crashes MS Outlook
  • EML to MHTML: Empty output
  • MSG->MSG inserts spaces between paragraphs
  • RTF MSG to MHTML: Font styles are not retained
  • Empty Message body when Saved email using Aspose.Email API is sent using MS Outlook
  • Resaving MSG file using MapiMessage destroys Ole Object in MSG
  • Loading Large EML raises System.OutOfMemory Exception in x86 settings
  • EML to MHT raises Exception
  • Exception while using IEWSClient.CreateContact with MapiContact and Contact
  • Exception while loading EML to MailMessage
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.

Tuesday, September 20, 2016

Skew Image Correction Process & Fast Image Rotation Algorithm are Enhanced in Java Apps

What’s new in this release?

We are pleased to announce the release of Aspose.OCR for Java 3.6.0. This release includes improved mechanism for skewed image correction. Faster image rotation algorithm has also been incorporated in this release. Skew image correction functionality was already supported in the form of getSkewDegree method. However skew image correction process has been improved further. Similarly, image can be rotated using Aspose.OCR but rotation algorithm has been improved further. Method com.aspose.omr.OmrEngine.rotateImage(com.aspose.omr.OmrImage, double) has been introduced. There are some important enhancements part of this release, such as angle of rotation calculation process has been improved, Textblock recognition deskewed image process has been improved, De-skew confirmation in OMR template editor has been improved. This release includes plenty of new & enhanced features as listed below
  • The angle of rotation is calculated inproperly
  • Improve neighbor-based skew corrector quality on small images and small angles
  • Support faster image rotation algorithm
  • Incorrect textblock calculation for deskewed image
Overview: Aspose.OCR for Java
Aspose.OCR for Java is a character recognition component that allows developers to add OCR functionality in their Java web applications, web services and Windows applications. It provides a simple set of classes for controlling character recognition tasks. It helps developers to work with image files from within their Java applications. It allows developers to extract text from images, Read font, style information quickly, saving time & effort involved in developing an OCR solution from scratch.

Monday, September 19, 2016

Export 3D Files to Collada Format & Detect Format of any Supported 3D File in .NET Apps

What’s new in this release?

Aspose team is pleased to announce the release of Aspose.3D for .NET 2.1.0. The new version allows developers to export 3D files to Collada format, detect the format of any supported 3D file, pick vertices on a polygon, and then form triangles. Developers can also program the GPU (Graphics Processing Unit) to set up the graphics hardware for rendering 3D geometry. Developers can install an Aspose.3D Nuget package in their .NET applications because Aspose team publishes each version as a NuGet package on the NuGet gallery. It’s recommended to upgrade old version of the Aspose.3D API to this latest one. Aspose.3D API has added support of converting all 3D files (Discreet 3DS, FBX, STL, Universal 3D and WavefrontOBJ) to Collada format. The Collada is an open XML file format for 3D assets, supported by various 3D software packages. Using the recent version or higher, developers may import any supported 3D scene, and then export to a Collada 3D format. The file format identification is the process of figuring out the format of a sequence of bytes. Aspose.3D API allows developers to detect the type of all supported 3D files before loading them for any manipulation purpose.  Using Aspose.3D API, developers can program the GPU (Graphics Processing Unit) and set up the graphics hardware for rendering 3D geometry instead of the fixed function pipeline. There are several approaches to program GPUs. Aspose.3D API uses graphics APIs such as OpenGL 4.0, DirectX 11, DirectX 9 and Vulkan to program the GPU. A polygonal curve is a finite chain of line segments. Line segments called edges, their endpoints called vertices. A simple polygon is a closed polygonal curve without self-intersection. Using Aspose.3D for .NET API, developers can triangulate the polygons. In short, any polygon can be divided into triangles. Developers might pick vertices from a polygon area, and then form triangles by calling algorithm of triangulation. This version also addresses an enhancement to display a proper message on 3D models if the used texture file is missing. It also exposes the low-level APIs to customize the rendering procedure. These enhancements and bug fixes improve performance and accuracy of Aspose.3D API. This release includes plenty of new features as listed below
  • Separate import options and export options for all 3D file formats.
  • Export support for Collada.
  • Allow user to access the low-level rendering API.
  • Allow node to be excluded during exporting.
  • Display texture not found on the model.
  • Allow Vector2/Vector3/Vector4/Quaternion to be editable in the property grid.
  • Polygon triangulate issue.      
  • Diffuse/Specular/Emissive won't work if no texture is used.
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.

Sunday, September 18, 2016

Remove Embedded Audios from Presentation & Manage Header Rows for Table in Java Apps

What's New in this Release?

The long awaited version of Aspose.Slides for Java 16.7.0 has been released. This is primarily a maintenance release where Aspose team has addressed many issues. It has introduced support for enabling Header rows or banned rows for tables inside slide and developers can now use this feature to add Header rows. The support for removing the embedded audio inside presentation has also been added in this release and with this feature users can now remove the embedded audios if it is intended. The presentation access and saving issues have been rectified for many presentation decks that resulted in exceptions including NullPointerException, ArgumentException, UnSupportedFormatException and OutofMemoryError in previous releases. It has also improved the slide cloning support and have resolved several incurring issues in this regard as well. It has also improved the presentation rendering support as well in this release. This includes rectification of rendering issues with charts and their elements, tables and SmartArt shapes. The support for generating of slide images, PDF and Tiff has also been improved in this release for different shape elements inside presentation decks. Some important enhancement & bug fixes included in this release are given below
  • Support for removing embedded audios from presentation
  • Support for providing option to enable Header row and Banded rows Options
  • Convert HTML with charts to PPTX by keeping charts editable in resultant file
  • Adding EMF in Aspose.Slides creates blurred image
  • Presentation not saved
  • Presentation not saving
  • NullPointerException on saving PPT presentation to ODP
  • Error: Converting Slides with charts to svg
  • Text is improperly rendered in generated thumbnail
  • Images are improperly rendered in generated thumbnail
  • Specified argument out of range exception on generating thumbnails
  • Protected view error message appearing on saving presentation
  • Gray borders observed around image in Ole frame when viewed in slide show
  • Incorrect Language Id is retrieved when using Aspose.Slides
  • The image improperly rendered in generated thumbnail
  • NullPointerException on accessing presentation
  • SLIDEUnsupported moniker type exception on loading presentation
  • LanguageId is null for text frame text
  • NullPointerException on loading presentation
  • ArgumentNullException on presentation save
  • OutofMemoryError on presentation load
  • getLoadFormat method returns 3 for pptx and ppsx files
  • Setting chart data range using Aspose.Slides
  • AutoShapeType is not correct when getting the autoshape from PPT file
  • Oleframe failed to open in PowerPoint when using Aspose.Slides
Other most recent bug fixes are also included in this release

Overview: Aspose.Slides for Java

Aspose.Slides is a Java component to create, read, write and modify a PowerPoint document without using Microsoft PowerPoint. It supports PHP applications and provides all advanced features for managing presentations, slides, shapes, tables and supports PPT, POT, POS PowerPoint formats. Now you can add, access, copy, clone, edit and delete slides in your presentations. It also supports audio & video frames, adding pictures, text frames and saving presentations as streams or SVG format.

Thursday, September 15, 2016

PDF to PDFA Conversion & Printing Issues on Non-Windows OS are Enhanced in Java Apps

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Pdf for Java 11.8.0. This version includes PDF to PDFA conversion improvement in addition to the improvements/enhancements made in its equivalent .NET version. We have fixed number of issues in this release, reported by our customers in previous releases. Some of these are PDF to PDF/A, PDF to HTML, PDF to DOC, Printing issue on iSeries and some others. This release has improved image rendering logic in PDF to PDFA conversion in this release, that fixed a lot of image related issues in PDFA. We have been reported some printing issues on non-Windows OS, in previous versions. We have fixed these issues PdfViewer class in current release and it will improve the API reliability. The basic API change in this release is removal of Interfaces namespace. It has also enhanced creating PDF by API, XML and XSL-FO files as well as converting HTML, XSL-FO and Excel files into PDF. Some important improved features included in this release are given below
  • PDF to HTML - Contents missing and wrong background color
  • PDF to PDF/A - Image starts appearing on top of page title
  • Error opening readonly PDF
  • PDF to Doc: Redundant tab character before a last bullet item
  • PDF to Doc: Redundant characters after bullet items
  • setKeptWithNext is not working as expected
  • PDF to PDF/A_3a - Resultant file is not PDF/A compliant
  • PDF to PDF/A - Text formatting is lost and contents are missing
  • PDF to PDF/A - Logo orientation is changed and background information is lost
  • PDF to PDF/A - Background becomes black
  • PDF to PDFA conversion duplicates background image
  • PDF to PDF/A - Issue with images
  • PdfPrinterSettings crash on iSeries (Java)
  • Concatenation: Bookmarks are not being copied to Merged Document
  • PDF to PDF/A - Resultant file is not Tagged
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.

Wednesday, September 14, 2016

Generate Aztec Coded Barcode & Adding Silverlight Barcode Reader Control in .NET Apps

What's New in this Release?

The latest version of Aspose.BarCode for .NET 8.2.0 has been released. This release supports generating and reading Aztec barcode type. This release supports checksum validation for OneCode and AustraliaPost coded barcodes. Support for Silverlight barcode reader & generator control and support for setting graphics unit in compact framework have also been incorporated in this release. It allows developers to generate Aztec barcode. A property AztecSymbolMode has been introduced to allow only numbers from 0 to 255 while using Aztec barcode. When AztecSymbolMode property is set, reader automatically detects Runes. Following is the code demonstration. Aspose.Barcode for .NET also supports checksum validation for OneCode and AustraliaPost barcodes. Property ChecksumValidation has been introduced to perform validation on OneCode and AustraliaPost barcodes. Following is the sample code demonstrating how ChecksumValidation can be set to off and on to perform validation. Using Aspose.Barcode for .NET, developers can set the graphics unit of the bars in the barcode while they are working with compact framework. Following is the sample code snippet to set the graphics unit to millimeter in compact framework. There are some important improvements included in this release, such as Process of reading Postnet barcode has been improved, process of reading DataMatix barcode has been improved, Functionality to set resolution in compact framework has been incorporated, processing of Dutch KIX barcodes has been improved, functionality to process the Aztec barcode with long code text has been improved, functionality to read barcode from a PDF file has been improved, functionality to read EAN13 barcode along with supplement code text has been improved and functionality to read DataMatrix barcode has been improved.. Below is the list of new and improved features supported in this version.
  • Support to generate Code128C coded barcode
  • Add Silverlight barcode reader control
  • BSupport for setting graphics unit in Compact Framework
  • Add Silverlight barcode generator control
  • Add new BarCode type: Aztec Runes
  • Implement Aztec Runes generator
  • Add checksum validation for OneCode and AustraliaPost
  • Implement Aztec Runes decoder
  • Dynabic.Metered Integration
  • The empty hexes for MaxiCode (barcode builder)
  • Reading Postnet barcode from image is not producing correct results
  • Aspose.BarCode is not recognizing correct DataMatix coded barcode
  • Support for setting resolution in Compact Framework
  • Recognize DataMatrix with the irregular black/white proportions
  • Exclude unwanted dutch KIX barcodes
  • Generate empty picture with incorrect codetext for Aztec
  • Update AustraliaPost generator
  • Override platform depending functions
  • Improve Aztec encoder speed for long codetext
  • Update API for generating CMYK files
  • Converting PDF to Image stream and then reading barcode is not working
  • Unable to get the supplement code text from EAN13 coded barcode
  • DataMatrix barcode can be decoded by using 3rd party online whereas Aspose.BarCode is unable to decode
  • Incorrect rotated Postnet barcode recognition
  • Detects only first Postnet
Other most recent bug fixes are also included in this release.


Overview: Aspose.BarCode for .NET
Aspose.BarCode is a .NET component for generation and recognition of Linear and 2D barcodes on all kinds of .NET applications. It supports WPF with 29+ Barcode symbologies like OneCode, QR, Aztec, MSI, EAN128, EAN14, SSCC18, Code128, Code39, Postnet, MarcoPDF417, Datamatrix, UPCA etc. Other features include barcode insertion in PDF, Word and Excel documents. Also take image output in BMP, GIF, JPEG, PNG and WMF formats. You can also control image styles such as background color, bar color etc.

Thursday, September 8, 2016

Control Document Header Information While Exporting Project Data to HTML inside Java Apps

What’s new in this release?

Aspose team is pleased to announce the release of Aspose.Tasks for Java 9.5.0. Ported from its equivalent .NET version, this release includes enhancement to the project data conversion to HTML functionality for controlling document header information to output. It also fixes a number of issues that were part of the equivalent .NET version as well as reported with the Java API. Aspose.Tasks API already supported conversion of project data to HTML. This release further enhances the functionality by providing the capability to control exporting of document header’s information to output HTML. 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. In addition to the functional and performance enhancements mentioned earlier, this month’s release also includes a number of bug fixes that further brings stability to the API functionality. Below is the complete list of bug fixes and enhanced features included in this release.            
  • Provide option for excluding document header name during Project->HTML
  • Performance is too slow with large number of tasks ~10K+
  • 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
  • Notes not updated in MPP file
Overview: Aspose.Tasks for Java

Aspose.Tasks is a non-graphical Java Project management component that enables Java applications to read, write & manage Project documents without utilizing MS Project. It supports reading MS Project Template (MPT) files as well as allows exporting project data to HTML, BMP, PNG, JPEG, PDF, TIFF, XPS, XAML and SVG formats. It reads & writes MS Project documents in both MPP & XML formats.  Developers can read & change tasks, recurring tasks, resources, resource assignments, relations & calendars.

Wednesday, September 7, 2016

Manage Embedded Audios in Presentation & Enable/Disable Header Rows for Table using .NET

What's New in this Release?

We are happy to share the announcement of Aspose.Slides for .NET 16.7.0.  This is primarily a maintenance release whereby we have resolved many issues incurring in API. This release has introduced the support for removing the embedded audio inside presentation in this release and with this feature you can now remove the embedded audios if it is intended. We have also introduced the support for enabling Header rows or banned rows for tables inside slide and you can now use this feature to add Header rows. Aspose team has improved the mechanism for Fonts Substitute rules in this API for better font replacements and has also rectified issue while setting DefaultRegularFont for text. We have also resolved certain pending issue like improper fonts, wrong arrow directions, wrong background colors, improper and wrong bullets and improper border for generated PDF or slide thumbnails. The issues of wrong shape colors and missing elements during slide cloning have also been addressed. Moreover, issues related to charts and their elements rendering have been taken care of in this release. 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 including KeyNotFoundException, IndexOutOfRangeException, ArgumentException, UnSupportedFormatException and PptReadException in previous releases.  This list of new, improved and bug fixes in this release are given below
  • Setting Color Scheme on Presentation
  • Support for removing embedded audios from presentation
  • Support for providing option to enable Header row and Banded rows Options
  • Borders around table appears on saving presentation
  • InvalidCastException on saving presentation
  • After loading presentation chart x axis changes
  • Updating chart data does not update the chart thumbnails
  • Using FontSubstRule causes incorrect rendering / exception
  • Time required to Open/ReSave large password protected pptx in 16.6 is significantly bigger than in previous versions
  • Time required to Open/ReSave large pptx in 16.6 is significantly bigger than in previous versions
  • Wrong charts rendering in generated thumbnails
  • Embedded Objects icon are changed after saving ppt
  • NullReferenceException on saving PPT presentation to ODP
  • Aspose.Slides 16 6 0: DefaultRegularFont setting doesn't work properly
  • Arrows are missing in saved presentation
  • Exception on exporting pptx to pdf
  • ArgumentOutOfRangeException on loading presentation
  • Aspose.Slides does not interpret CSS line-height property correctly
  • Incorrect Language Id is retrieved when using Aspose.Slides
  • Protected view error message appearing on saving presentation
  • LanguageId is null for text frame text
  • Underline is missing
  • Incorrect rendering of EA portions
  • Font ges changed on saving presentation
  • Value cannot be null on saving PPT presentation
  • NullReferenceException on saving presentation
  • Unsupported moniker type exception on loading presentation
  • Space character is changed after saving a ppt file
  • Wrong shape constraints in loaded presentation
  • Shape Fill and background color gets changed on saving presentation
  • Drawing text in spills out of a table border
  • XmlException on slide cloning
  • ArgumentNullException on presentation save
  • Error while generating thumbnails
  • PresentationInfo.LoadFormat method returns Pptx for pptx and ppsx files
  • High memory consumption on presentation load and save
  • Curved Text in a Group rendered incorrectly on slide clone
  • PptxReadException thrown on loading pptx
  • White Block images on Chart Lines after Cloning
  • PPTX slide text formatting gets disturbed on cloning slides
  • IIS Hangs with high CPU usage when converting slides to jpg
  • SLEmbedded Ole objects Icons get disturbed on opening and saving presentation
  • Shape segment is changed on PPT resaving
  • Background color missing in cloned shape with Aspose.Slides
  • Wrong Colors after cloning from PPTX
  • The direction of the shapes changes when saving in PPT format
  • AutoShapeType is not correct when getting the autoshape from PPT file
  • Embedded OLE Frame failed to open in PowerPoint
  • Text color changes in shape when slide is cloned
  • Shape border line is improperly rendered for thumbnail in PPT
  • SmartArt Text is lost on generating slide thumbnail
  • UnsupportedFormat exception on loading odp file
  • Wrong Gradient type returned for the shape
  • Arrow shape rendered as square in exported PDF
  • CloneSlide Problem: MS-PowerPoint 2000 shows blank slide instead of Rectangular Callout shape
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.

Tuesday, September 6, 2016

Recursive Calculation of Formulas & Fonts Configuration for Rendering Spreadsheets using Java

What’s new in this release?

We are pleased to announce the new release of Aspose.Cells for Java 8.9.2. This release includes many new features and enhancements along with some critical bug fixes that further improve the overall stability of the API. Aspose.Cells for Java 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. Developers can Set Font Sources and can also Substitute Fonts. It has exposed the Boolean type property to true and passing the object to calculateFormula method directs the Aspose.Cells APIs to calculate the dependent cells recursively when calculating cells which depends on other cells. Aspose.Cells for Java 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. It 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. This release includes some important enhancements,  such as HTML rendering engine for shapes such as TextBoxes, Improved PDF rendering engine for charts as well as cell text alignment, Tweaked Aspose.Cells’ formula calculation engine to match the results with Excel application and Handled a few exceptions such as IndexOutOfBoundsException, NumberFormatException & OutOfMemoryError for certain scenarios. This release includes several enhanced features and bug fixes as listed below
  • Calculation time has increased with recent API revisions
  • User configurable fonts substitution mechanism is required
  • Workbook.calculateFormula() method never terminates for the source Excel file
  • Unable to catch image resource while rendering spreadsheet to HTML with IStreamProvider
  • Problem with rendering CheckBoxes to HTML
  • Issue with getDisplayStringValue() for Date formatted values
  • Using Light Cells APIs to process an XLS file, the first cell of the first sheet is always processed
  • Character spacing and break not correct for vertical text while rendering spreadsheet to PDF
  • Column widths are different on CentOS than on Windows
  • Chart scale has shifted while rendering spreadsheet to PDF
  • Alignment problem when rendering an Excel file to PDF
  • Formatting of legend entries is disturbed while rendering spreadsheet to PDF
  • Horizontal axis labels have not been rendered completely, that is; all labels are missing some contents in the rendered image.
  • File is corrupted after formula calculation and save
  • Calculation result is not correct
  • Array Formula is not being calculated properly
  • Some values from the Excel file are missing in the output HTML - XLS to HTML conversion
Other most recent bug fixes are also included in this release

Overview: Aspose.Cells for Java

Aspose.Cells is a Java component for spreadsheet reporting without using Microsoft Excel. Other features include creating spreadsheets, opening encrypted excel files, macros, VBA, unicode, formula settings, pivot tables, importing data from JDBC ResultSet and support of CSV, SpreadsheetML, PDF, ODS and all file formats from Excel 97 to Excel 2007. It is compatible with Windows, Linux & Unix and supports all advanced features of data management, formatting, worksheet, charting and graphics

Monday, September 5, 2016

Work with OneNote Page Revision Information & Enhanced Working with Page History using .NET

What’s new in this release?

We are pleased to announce the release of Aspose.Note for .NET 2.5.0.  This month’s release provides support for reading/writing revision information to a document’s page type. It also enhanced the functionality of working with history of a document such as rolling back to previous page version, pushing current page version to history and modifying page history. This month’s release provides the capability of working with page revision information of a document such as recent author and last modification time. This feature lets you read as well write the page revision information to a document’s page. Aspose.Note API already provides support for working with Page history in a document. This month’s release brings further enhancements to this capability by providing the facility to rolling back to previous page version, pushing current page version to page history and modifying page history. Rolling Back to Previous Page Version lets the API users to roll back to a previous version of the API by getting the last version from the page’s history. The current page version of the page can be included in the history collection by using the Page.Clone method. Modifying Page History feature allows modifying the information related to a page history such as title and author. This month’s release also fixes a number of bugs related to API functionality that further improves the API stability in terms of features and quality. The list of new and enhanced features added in this release are given below
  • Implement saving document history to *.one format
  • Add revision information to the document's page type
  • MD5 check error for OneNote 2016 format
  • Fix bug related to possible empty NotebookManagementEntityGuid in the PageSeries node
  • Last subpage is in incorrect position after opening and then saving document
  • Pages with subpages which we create cannot be collapsed by MS OneNote
  • Loading attached OneNote documents raise exception
  • Exception "An item with the same key has already been added" raised while loading the attached one note file
  • FileCorruptedException during parsing of sample file
  • Failure to generate output files if path is the same as execution folder
  • Inconsistent file names while exporting flattened notebook
  • Notebook's structure is changed while saved with NotebookSaveOptions.Flatten
  • Incorrect pages in Page History
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Note for .NET documentation that may guide users briefly how to use Aspose.Note for performing different tasks like the followings.
Overview: Aspose.Note for .NET
Aspose.Note for .NET is a set of .NET components that enables developers to work with Microsoft Office OneNote files in C#, VB.NET, ASP.NET web applications, web services & Windows applications. It allows developers to open files & manipulate elements of OneNote books, from text, images & properties, to more complex elements, & then export to PNG, GIF, JPEG, BMP or PDF formats. It is a pure .NET alternative to the MS OneNote Object Model & supports OneNote 2010, OneNote®  2010 SP1 & 2013 files.
More about Aspose.Note for .NET

Sunday, September 4, 2016

Aspose.Newsletter September 2016: Automate PowerPoint Presentation Creation & Other News

Aspose Newsletter for September 2016 has now been published that highlights all the newly supported features offered in the recent releases. It also includes information about Automate PowerPoint Presentation Creation, Conversion, & Editing, Introducing C++ API to work with Excel formats, JasperReports Server 6.3.0 Support in Aspose.Words and Aspose.Cells for JasperReports, new features and improving existing ones in Aspose for Cloud, Working with Bookmarks of Microsoft Word Documents using Aspose.Words for .NET, Binding SMTP Client to Specific IP Address on Host using Aspose.Email for Java and much more.
Automate PowerPoint Presentation Creation, Conversion, and Editing
Aspose.Slides for .NET and Java APIs can work with any type of .NET or Java applications. users can add the code into their existing applications. Users can use an existing templates and edit those using Aspose.Slides for .NET or Java.  Let Aspose APIs make users work easier! Download a free Trial
Introducing Aspose.Cells for C++ API to work with Excel formats
aAspose team is delighted to announce the addition of a new platform into Aspose file format APIs — C++. Aspose.Cells for C++ is the first one and Aspose well add more APIs for C++, however, users may start processing an Excel spreadsheets using C++. Aspose team is starting with a selected set of features, but more will be coming soon as Aspose team is release new versions regularly and frequently. Read blog announcement about C++ API to work with Excel formats
JasperReports Server 6.3.0 Support in Aspose.Words and Aspose.Cells for JasperReports
Aspose team has released new versions of Aspose.Words for JasperReports and Aspose.Cells for JasperReports. Both of these APIs now support JasperReports Server 6.3.0. It’s quite a great news for anyone looking to integrate Microsoft Word and Microsoft Excel file processing features into the latest version of JasperReports Server. You can read more about these updates for Aspose.Words for JasperReports and Aspose.Cells for JasperReports in Aspose blog
Aspose for Cloud – A lot has been going on!
Aspose team has introduced file format APIs for the Cloud quite some time ago and a lot of developers and companies started to use them in their products and applications. Aspose team has been adding new features and improving existing ones. Users can start exploring cloud APIs for free and once satisfied, select a plan as per their needs. The Cloud APIs provide flexibility as they can be used in any type of application on any platform using REST APIs. Users can read more about Cloud APIs in Aspose blog or on website
Working with Bookmarks of Microsoft Word Documents using Aspose.Words for .NET
  
Manipulating bookmarks in a Word document is a common requirement when working with the documents directly or programmatically. Aspose team has described in detail how to create, retrieve, or move bookmarks in a Word document using Aspose.Words for .NET. The details can be found in the article titled Working with Bookmarks
Binding SMTP Client to Specific IP Address on Host using Aspose.Email for Java
The following article describes and shows you the code to bind SMTP client to a specific IP address using Aspose.Email for Java: Binding SMTP Client to Specific IP Address on Host. You can also learn how to work with other SMTP features to send emails using Aspose.Email for Java API in the following section: Sending Email Messages with SMTP
Updates about new Product Releases
  1. Aspose.Total for .NET - a compilation of Aspose latest .NET products.
  2. Aspose.Words for .NET 16.7.0 - Support for MathML in HTML export and many other features
  3. Aspose.Pdf for .NET 11.9.0 – PDF to PDFA and DOCX conversion, XFA to standard form conversion.
  4. Aspose.Slides for .NET 16.5.0 – Support for rendering hidden slides in PDF and PictureBullet for PPTX format
  5. Aspose.Email for .NET 6.6.0 - Splitting PST File with defined criterion supported
  6. Aspose.Imaging for .NET 3.9.0 - Create EMF metafile image, export text as shape when converting EMF to SVG
  7. Aspose.Tasks for .NET 9.5.0  Improved performance of task creation in the latest version
  8. Aspose.Diagram for .NET 6.7.0 – Improved Auto Scaling of a Shape and Set an Event Cell in the Visio Drawing
  9. Aspose.Total for Java – a compilation of Aspose latest Java products.
  10. Aspose.Words for Java 16.7.0 - Support for MathML in HTML export and many other features.
  11. Aspose.Pdf for Java 11.6.0 – Over 20 improvements including improvements to HTML escaping in HTML to PDF export and warnings on font substitution.
  12. Aspose.Slides for Java 16.5.0 -  Support for rendering hidden slides in PDF and PictureBullet for PPTX format.
  13. Aspose.Email for Java 6.8.0 – Splitting PST File with defined criterion supported
  14. Aspose.Barcode for Java 8.0.0 - Implement new algorithm to recognize 3D-distorted Aztec codes.
  15. Aspose.Imaging for Java 3.7.0 - Implemented support for Scalable Vector Graphics (SVG) 1.1 and Support FontSettings for CAD and EMF formats
  16. Aspose.Diagram for Java 6.7.0 - Detect Visio File Format and Modify Event Cells of a Visio Shape.
  17. Aspose.Total for Android – all the latest versions of Aspose Android APIs.
  18. Aspose.Total for SharePoint – a compilation of Aspose latest SharePoint products.
  19. Aspose.Total for Reporting Services – a compilation of Aspose latest Reporting Services products
  20. Aspose.Total for JasperReports – The latest versions of Aspose JasperReports product
Supporting User Groups and Conferences
Aspose is sponsoring a number of user groups and upcoming events, including:
  • Sep 2016: Perth .NET User Group – Australia
  • Sep 12-14: API World 2016 Conference & Expo – Washington, D.C.
  • Sep 14: Java Metroplex Users Group Meeting – Dallas, TX
  • Sep 19-23: BASTA! Fall 2016 Mains – Germany
  • Sep 29- Oct 01: .NET UY Conf 2016 Montevideo – Uruguay
Would you like us to sponsor your user group? Get in contact at user.groups@aspose.com
Collect your copy of Aspose Newsletter, February 2016 edition

Thursday, September 1, 2016

Generate DutchKix, DotCode Barcodes & Improved Barcode Recognition Algorithm using Java

What’s new in this release?

We are pleased to announce the new version of Aspose.BarCode for Java 8.0.0. This release supports generating/reading DutchKix and DotCode barcode types. Several new enhancements have also been made in barcode recognition algorithm to further improve recognition process while reading barcodes from poor quality QR, Code128, DataMatrix and Aztec codes. Aspose.Barcode for Java allows users to generate DutchKix or DotCode barcodes. Developers can also set SymbologyType to DutchKix or DotCode to generate these barcodes. There are some important enhancements part of this release, such as Improved algorithm to read barcodes even if the image is not rotated, Improved algorithm to Read the barcodes from a PNG image having 100 multiple barcodes in it, improved detection of the barcodes with default settings, support recognition of invasion in the quiet zone for a data matrix, improved 3D-distorted Aztec code recognition, improved recognition of the Aztec code, recognize poor quality code128 with histogram method, improved DotCode regions recognition and read the corrupted QR barcode. Below is the list of main improved features and bug fixes added in this release.
  • Add new BarCode type: DutchKix
  • Add new BarCode type: DotCode
  • Barcode not reconginzed if image is not rotated
  • Unable to Read the barcode from a PNG image having 100 multiple barcodes in it
  • BarCodeReader not detecting the barcodes with default settings
  • Support recognition of invasion in the quiet zone for data matrix
  • Incorrect 3D-distorted Aztec code recognition
  • Incorrect recognition of the Aztec code
  • Recognize poor quality code128 with histogram method
  • Program hangs on Aztec code
  • Can't recognize 3D-distorted Aztec code from the JPG image
  • Several consecutive recognitions give different results
Overview: Aspose.BarCode for Java

Aspose.BarCode is a Java based visual component for generation & recognition of 1D & 2D barcodes to support Java, web applications and J2ME platform. It supports 29+ barcode symbologies like MSI, QR, OneCode, Australia Post, Aztec, Code128, Code11, EAN128, Codabar, Postnet, USPS and also supports image output in GIF, PNG, BMP & JPG formats. Other features include barcode size & color settings, rotation angle & caption. You can render barcodes to images, printers, HTTP servlet response & graphical objects too.