Set Connector Shape Appearance & Font Directory Paths for Rendering Visio Diagrams

What’s new in this release?

We are pleased to announce the new release of Aspose.Diagram for .NET 5.2.0. With this new release, developers can now set the font directory paths for rendering in Visio diagrams and also they could set connector shape appearance. In addition to that we have added support to refresh milestones on the timeline shape and included another print method which takes printer and document name parameters on a customer request. It allows to customize document name during the print job. Besides above new features, we also bring performance, formatting, and quality improvements in exporting Visio diagrams to any other supported formats. The operating systems store fonts in different folders and Aspose.Diagram looks for fonts in the respective Fonts folder. Developers can now specify locations of their own or third party fonts folders. Microsoft Office Visio offers connection types by going to the Design tab, and at the far left of the ribbon you can see Connectors in the Layout group. There are three types of Connectors in Visio: Right Angle, Straight Lines and curved, which can be found from the popup menu if you click the connectors button. This new release of the Aspose.Diagram APIs has included this feature support. Developers can now manage connector type shape’s appearance programmatically. The timeline shape is the foundation to which we add the project milestones and events, Aspose.Diagram APIs allows to manage it. Using the older version, when we changed the period of timeline shape, milestones remain schedule based on the previous time period. To manage this thing, we have added a new RefreshTimeLine method in TimeLineHelper class. We have added another print method which sends print jobs to the printer. It takes printer and document name as parameters, so far users can customize the document name in job print queue. In this recent release version, we have improved export areas regarding VSD to PDF, VSD to PNG, VSD to SVG and VSD to VDX. We have also included some fixes of manipulation.  Here is the list of important enhancements and bugs fixes in the new version.

• Add support to set connector appearance
• Add support to set fonts folder path 
• The timeline data does not update in Visio Viewer
• Performance issue when exporting VSD to PDF format
• VSDX to PDF conversion, incorrect rendering of the text items
• Can't add shape second time in the same page or other one
• Can't move shapes manually in Microsoft Office 2010/2013  
• Add support to pass printing job name as another parameter
• Update EULA html document in Non-MSI packages     
• Can't access shape ParaCollection objects
• Argument Out of range error message occurred while placing a shape
• Shape is using single connection point instead of different connection points
• Warning message when opening resultant VDX diagram
• VSD to PDF conversion, shapes are not properly visible
• VSD to PNG conversion, shapes are not properly visible
• VSD to SVG conversion, shapes are not properly visible
• VSD to VDX conversion, shapes are not properly visible
• VSD to VDX conversion, shape's text goes outside the border
• Can't glue shape inside the container
• Default date format is not available for Milestone shape
• Default date format is not available for Timeline shape

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.

• Homepage of .Net Visio Component Aspose.Diagram for .NET
• Download Aspose.Diagram for .NET

Convert PDF to Editable PPTX File & Multi-Column PDF Generation in .NET Apps

What's New in this Release?

We are pleased to announce the release of Aspose.Pdf for .NET 10.3.0. This new release provides some great features and enhancements, which keeps this API high among the list of its competitors.  We know that PDF is one of the widely used file format for data sharing because it ensures the document structure/contents remains intact, when viewing the file over various platforms/devices and even it does not matter what your regional or personal system preferences are. In order to deal with PDF format, Aspose.Pdf for .NET is one of the great API’s in industry to facilitate users to programmatically create as well as manipulate any existing PDF files. Recently many of our customers requested a feature to transform PDF files to PPTX format, and we are pleased to share that this new release of Aspose.Pdf for .NET offers this great feature. So in order to accomplish this requirement, you only need to instantiate an object of PptxSaveOptions class and pass it as second argument to Document.Save(..) method. Magazines and newspapers mostly have news; mostly displayed in multiple columns on the single pages instead of the books where text paragraphs are mostly printed on the whole pages from left to right position. Many document processing applications like Microsoft Word and Adobe Acrobat Writer allow users to create multiple columns on a single page and then add data to them. Aspose.Pdf for .NET also offers the feature to create multiple columns inside the pages of PDF documents. PDF/A is widely used standard to preserve data inside document for long term and also to ensure the integrity of data inside the document (document is not modified, once its compliance is set to PDF/A format). Recently we have come across a requirement to provide support for attachments in PDF/A files and as per Adobe Community post, PDF/A_3a compliance format supports the feature to attach any file type as attachment. Aspose.Pdf for .NET offers the feature to use Custom/TrueType fonts while creating/manipulating PDF file contents, so that file contents are displayed using contents other than default system fonts. The FindFont(..) method of Aspose.Pdf.Text.FontRepository class provides the capabilities to find specific font from system font repository (i.e. C:/Windows/Fonts/). The method is case-sensitive and requires exact Font file name. In this new release, we have provided an overload method public static Font FindFont(string fontName, bool ignoreCase), which takes second argument to specify either the font name should be case-sensitive or not. As well as the enhancements and features discussed above, there have been specific improvement for PDF to HTML and HTML to PDF conversion features. Among these fixes, the PCL to PDF, SVG to PDF, PDF to Excel, PDF to DOC, PDF to TIFF and TIFF to PDF conversion, conversion of PDF to PDF/A compliant documents, text replacement, rendering PDF files to XPS format are also improved. The list of important new and improved features are given below

• Support of multi-column PDF in new generator
• PDF to PPTX conversion support
• support of PDF/A with attachments
• Support OTF fonts
• Make FindFont(..) case insensitive
• Generating multi column TOC in PDF document
• Table breaking across page should not have bottom border on page 1 and top border on page 2
• HtmlFragment throws ArgumentException against large HTML
• Parallel Processing consumes 100% CPU
• PDF to HTML - Error in console when viewing resultant file
• HTML to PDF: HtmlFragment throws ArgumentException
• Text foreground color is not being applied
• XPS to PDF conversion fails on 3.5 and 4.0 .NET platform
• PDF to DOC: Header image and text is missing
• PDF to DOC: Text renders incorrectly
• TextStamp changes position depending on if Draw is set True or False
• Setting Draw property of TextStamp class to false changes view
• PDF to HTML: Incorrect colors in output html
• Incorrect page count
• HTML to PDF - rgba background colors doesn't work
• PDF to TIFF - Output is not correct
• Signature gets corrupted when removing page from PDF file
• PDF to HTML - Spaces between words are eliminated
• PDF to HTML: Output HTML contains squares between lines
• Setting zoom using PdfPageEditor class corrupt the output image
• HTML to PDF: incorrect output
• PDF to HTML: incorrect rendering of text in output HTML
• PDF to HTML- lots of errors loading HTML in Chorme/FireFox
• HTML to PDF: footer overlaps the document as column
• PDF to XPS: Words are being rendered incorrectly
• PDF to DOC/DOCX: Underlines rendered incorrectly
• TXT to PDFA - OutOfMemoryException is being generated
• PDF to PNG results into distorted image
• HTML to PDF is not honoring Table Columns width and rows are breaking at page end
• HTML to PDF conversion issue
• Convert HTML to PDF - Text layout issue
• PdfPageEditor removes data from PDF document
• Problems with the replacement of several segments of text found in one fragment.

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

Overview: Aspose.Pdf for .NET

Aspose.Pdf is a .Net Pdf component for the creation and manipulation of Pdf documents without using Adobe Acrobat. Create PDF by API, XML templates & XSL-FO files. It supports form field creation, PDF compression options, table creation & manipulation, graph objects, extensive hyperlink functionality, extended security controls, custom font handling, add or remove bookmarks; TOC; attachments & annotations; import or export PDF form data and many more. Also convert HTML, XSL-FO and MS WORD to PDF.

• Homepage of Aspose.Pdf for .NET C#
• Online Demo for Aspose.Pdf for .NET

Search Messages using Search String Encoding & Send DKIM Signed Emails using Java

What’s new in this release?

We are pleased to announce the new release of Aspose.Email for Java 5.2.0. We are pleased to share that the feature of signing messages with DKIM has been implemented in this month’s release. In addition, the API also provides the capability to specify search string encoding while searching for messages using ImapQueryBuilder. For a detailed list of API changes, please consider visiting our documentation section, Public API changes in Aspose.Email for Java 5.2.0. This latest version of Aspose.Email for Java includes enhancements like Sending DKIM Signed Messages and Using Encoding in ImapQueryBuilder. With this month’s release, the API now provides the feature of signing email messages with DKIM (Domain Keys Identified Mail). The MailMessage class’s dKIMSign method provides the usage of this feature by using the private key file and DKIM signature Info. Once signed, the message can be sent using the API’s SMTP client. Aspose.Email provides the capability of listing messages from IMAP server mailbox, with the capability of applying criterion based searches using ImapQueryBuilder. This month’s release further enhances the functionality of searching messages by specifying search string encoding. This helps querying the mailbox for different search strings based on the specified encoding e.g. Turkish characters such as ğüşıöç. This month’s release also includes a number of bug fixes as part of either ported from its equivalent .NET version or reported actually with the Java version of the API. These include, a number of issues related to TNEF messages conversion and display at receiver’s end, message content encoding issues during message conversion to different formats, Limitation on adding more than 1020 inline images while adding message to PST and exceptions while message conversion to TIFF, loading certain EML files and adding messages to PST files. The main improved features & bug fixes added in this release are listed below

• Add the DomainKeys Identified Mail (DKIM) signature to the email message headers
• Check oauth support for SMTP and IMAP clients for Yahoo and Yandex mail servers. Make TokenProvider as server-independent class if possible.
• Refactoring properties Body and TextBody of MailMessage.
• Provision of flag to avoid validity check while adding header values to HeaderCollection-Java
• MSG created from TNEF attachment doesn't open in Outlook
• MailMessage.Subjec loses the ending "space"
• DOCx->MHTML->MSG->Send using Outlook: Line Breaks are no more respected
• Changing the embedded message name of TNEF formatted EML does not take effect
• EML to MSG conversion raises NULL exception
• MapiMessage with more than 1020 inline images cannot be added to PST folder (Java)
• Message printing: problem with russian charset
• Mail subject is corrupted after load and save it as EML
• MailMessage.Load converts embedded inline image to attachment.
• MailMessage.Save as HTML to ByteArrayOutputStream raises exception
• MSG to PST: Subject Encoding issue

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

Multiple CAD Layout Rendering, PNG/GIF Transparent & Background Colors Support

What’s new in this release?

Aspose development team is pleased to announce the new release Aspose.Imaging for Java 2.6.0. This release contains many useful improvements, including the long awaited feature of AutoCAD drawings to raster image conversion. Aspose.Imaging for Java API now supports the conversion of CAD drawing formats such as DXF & DWG to raster image formats such as PNG, BMP, TIFF, JPEG and GIF. Aspose.Imaging for Java API has exposed the VectorRasterizationOptions and CadRasterizationOptions classes to the com.aspose.imaging.ImageOptions package that serve an efficient and easy to use interface for CAD to Raster Image Conversion. Aspose.Imaging APIs already support the feature of re-sizing existing images by passing the new height & width values as parameters to the Image.resize method but in that case the user had to calculate the aspect ratio himself. This is because when the width or height of an image is altered, the image either scales or shrinks to fill the new size. If the changes to the width and height of an image are not in proportion this could lead to stretched and distorted result. Aspose.Imaging for Java 2.6.0 has also exposed overload versions of the resizeWidthProportionally and resizeHeightProportionally methods that can accept ResizeType as second parameter to achieve desired results. An important point to note is that if you intend to get quality result after applying the re-size then it is suggested that you should always use ResizeType.LanczosResample because it will output highly qualitative results but may work slower than ResizeType.NearestNeighbourResample. On the other hand, ResizeType.NearestNeighbourResample algorithm is specifically used for fast re-sizing while compromising on the image quality. This method may be useful for thumbnail generation in real time or similar processes where performance is required. The main new and improved features added in this release are listed below

• CAD to Raster Image Conversion
• Resize Images Proportionally
• EmfPen incorrectly renders line width
• com.aspose.imaging.internal.Exceptions.ArgumentException: Value does not fall within the expected range at Image.rotateFlip for PNG format
• IWmfMetafileImage throws java.lang.IllegalArgumentException: Width (0) and height (0) cannot be <= 0
• Aspose.Metafiles ignore brush pattern in raster opperations (EMR_STRETCHDIBITS record)
• Aspose.Metafiles ignore logical brushes (EMR_CREATEBRUSHINDIRECT record)
• Aspose.Metafiles ignores the text quality value (EMR_EXTCREATEFONTINDIRECTW record)
• Aspose.Metafiles ignore logical brushes (EMR_CREATEBRUSHINDIRECT record)
• Application hangs while resizing a small Gif Image
• ImageLoadException: Image loading failed at loading a Multi-Page Tiff
• ImageLoadException: Image loading failed. Aspose.Imaging cannot load a Tiff generated with Aspose.Words for Java
• Conversion from PNG to JPEG renders the transparent area to black
• Setting the Brush Color does not seem to Take Effect when used to Draw String

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

Set Desired Image Dimensions for Spreadsheet Export, Modify SQL DB Connection Settings

What’s new in this release?

We are pleased to announce the new release of Aspose.Cells for .NET 8.4.1.  Microsoft Excel application allows creating the database connection so that the data could be bound/ fetched and loaded in the spreadsheets to refresh Pivot Tables, Charts or just the worksheet. The external data source is connected to the workbook through a data connection, which is a set of information that describes how to locate, log in, query, and access the external data source. Aspose.Cells for .NET API does not allow to create a database connection yet, however, some revisions back, the API had exposed the ExternalConnection class that contains the method & properties that could be used to review the database connection details stored in a spreadsheet. Most of the properties associated with ExternalConnection class were read-only until the release of Aspose.Cells for .NET 8.4.1. With this release, the API has provided the support to manipulate the database connection settings. Another worth mentioning feature is the support for setting desired image dimensions while exporting spreadsheets & charts to image formats. Aspose.Cells for .NET 8.4.1 has exposed the ImageOrPrintOptions.SetDesiredSize method to set the dimensions of the resultant image while exporting spreadsheets & charts to images. The SetDesiredSize method accepts two integer type parameters, where first is the desired width and second parameter is the desired height. Microsoft Excel has predefined settings to render comments while printing the spreadsheet or saving them in PDF format. Aspose.Cells APIs have borrowed this concept from Microsoft Excel and have exposed the PageSetup.PrintComments property & PrintCommentsType enumeration to facilitate the rendering of comments while converting spreadsheets to PDF format. The API has recently exposed the DataLabels.Characters method to retrieve an instance of FontSetting class that corresponds to the sub-string of ChartPoint.DataLabels. In turn, the instance of FontSetting class can be used to format the sub-string of the Data Labels with different font settings & color. Aspose.Cells for .NET 8.4.1 has exposed the Workbook.IsLicensed attribute which could be of great help in determining if the license file/key has been successfully loaded or not. If you access this property before setting the license, it will return false otherwise true for properly set valid license. In this release, several important issues have been addressed. For example, issues around writing Microsoft Excel file formats, applying formatting to the cells, copying rows, manipulating PivotTables, using PageSetup options, rendering HTML file format, manipulating shapes, rendering images from Excel worksheets, manipulating charts with formatting, 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 further and fixed a few relevant issues in this release. This release includes several enhanced features and bug fixes as listed below

• Set SQL Data Connection
• Support to Print Comments at the End of Sheet
• Rich Text Feature for Chart's DataLabels
• Pivot Table's data view in HTML does not correlate
• Pivot Table does not refresh while rendering to HTML
• Report Filter selections change
• Incorrect rendering of HTML while converting spreadsheet to HTML
• pivot table cells in group headers have incorrect styles
• Removing the source sheet causes exception on save
• The sort order of PivotChart's series data points is wrong
• Wrong conversion from HTML file to PDF
• Re-saving the XLS spreadsheet makes the result corrupt
• Date is overlapping with text in the left footer in the rendered PDF file format
• Double cell border is not printing properly for the last cell
• Missing table header border when converting to PDF
• Aspose doesn't print empty page
• Spreadsheet to PDF generates a blank PDF
• Pixels deteriorated a bit for the image in the output PDF file
• Cells that had dates and/or numbers with Hebrew words
• The logo with indentation wrong
• Colon in the end of the last word in the first line broke off
• The spaces between the Hebrew words vanished mashing the sentence into one word
• Support RenderToSize API for Worksheet Image
•  FillFormat.GradientColorType returns PresetColors
• API returns null for DataLabel.NumberFormat
• Chart x-axis has negative values but only the minus sign (-) is shown
• Separator is read as "Auto" instead of "(NewLine)" for the Chart's Datalabels
• The Category axis' Major Minor and Base units in the chart changed
• Arrow is added to each trend element while rendering the chart to image
• Graph legend's size (Hebrew and English words) varied in the PD
• Setting CategoryAxis' CategoryType to TimeScale causes Chart.Calculate method stuck
• Missing Secondry Vertical Axis Values while rendering the Chart to Image
• Missing Secondry Verical Axis Values while rendering the Chart to Image
• Arrangement of the legends has changed after rendering the Chart to Image
• Half number lines and text do not show up for the x axis
• Chart exported to PDF have extra lines
• I've got a 0byte image - Shape2Image Error
• Chart mistakes when rendering container range
• Opening and re-saving an Excel file with SplitView results in a corrupted file
• Images in workbook cause it to not be openable
• Incorrect values returned for formula fields as compared to Excel
• Dropdown filter cannot be selected after loading and saving
• Loading and saving the XLSM makes the result corrupted
• Formula involving Named range cell is not read fine
• Value of Linked Cell of Radio Button is wrong
• Workbook.CalculateFormula gives different results from Excel
• Text style changed after loading a spreadsheet and saving back
• Cells.CopyRows has strange behavior with borders formatting
• Copy then paste a single row with multiple columns is not working
• GridWeb component load excel file problem with french culture
• GridDesktop is unable to find embedded resource license
• Shapes are not rendered properly in gridweb
• Moving worksheets in GridDesktop
• Some of the methods are missing in GridWeb

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

SmartArt Customization, Presentation Export to PDF & Slide Thumbnail are Enhanced

What's New in this Release?

We are happy to share the announcement of Aspose.Slides for .NET 15.3.0. This is a maintenance release in which we have resolved issues related to different PowerPoint presentations features in Aspose.Slides for .NET API. We have resolved certain issues that occurred during presentation access, saving and rendering to PDF, HTML or slide thumbnails, in the form of different exceptions like SystemOutOfMemory Exception , NullReference, ArgumentException, InvalidOperationException, ObjectReferenceException,and IndexOutOfRange. The issue of presentation repair message appearing in Aspose.Slides generated presentations when viewed in different PowerPoint versions has also been addressed and resolved in this release. The issue of Password protecting the PPT format presentations has also been addressed. We have improved the chart rendering support and certain issues involving improper chart legends, improper chart axis labels, wrong chart label color for many chart types. The Donut chart type rendering has also been improved in this release. The rendering of SmartArt shapes has also been improved to a great deal and many text rendering issues incurring in SmartArt shapes have been resolved. The export to PDF and slide thumbnail has been improved for various slide areas including missing highlighted text, wrong text alignment, missing text, changed font properties, wrong bullet types, improper text curving, improper hyperlinks and wrong Word Art rendering. The issues related to slide cloning have also been rectified in this release. The issues related to working with tables have also been addressed in this release and pending issue concerning to splitting table column has been resolved. This list of new, improved and bug fixes in this release are given below

• Improved SmartArt customization support
• Presentation repair message on saving presentation with video
• Presentation gets corrupt when opened in PowerPoint 2007
• Lines appearing in the exported PDF for the chart
• Improper positioning of the comments in presentations
• IWarningCallback implementation shows different substitution fonts for same font
• Text highlighting missed in generated PDF
• FontManager returns 0 as fonts count if the presentaiton is loading using stream
• Wrong text color of Data Label with value 23%
• Text alignment in merged cell of the table is not correct in PDF file
• SplitbyColSpan not splitting the table properly
• Chart missing and improperly in generated thumbnail
• Text on SmartArt (after re-saving) is improperly rendered in thumbnail
• Text has wrong position on slide after saving presentation
• Wrong image rendering in generated Html
• Wrong legend rendering in generated thumbnail
• Exception: Only FileMoniker is supported on opening the PPT file
• Slide text get missing when slide thumbnail is generated in multiple passes
• Text missing in exported PDF
• Changing the font height does not refelect upon the slide in exported SVG
• Wrong ParagraphFormat.Bullet.Type value after export to PPT
• Wrong line width after export to PPT
• Chart labels are loosing orientation after updating the values
• Text curving from PPT presentation serialized in PPTX improperly
• WordArt text Curve-Up rendered improperly from ppt presentation
• Wrong title text formatting after saving PPTX presentation
• Changing border FillFormat.FillType to wrong value due to serialization
• Replacing unsafe ASCII characters with a "%" by printable symbols.
• System.IndexOutOfRangeException on taking table height after merging cells
• The change of a hyperlink is not saved to ouptup PPT and PPTX presentations
• System.IndexOutOfRangeException on taking table height
• Improper doughnut chart rendering in generated thumbnail
• Password protection not getting applied on PPT file
• Presentation repair message appears in PP 2007 for Aspose.Slides saved presentation
• Wrong angle of WordArt text on thumbnails and PDF from ppt presentation
• InvalidOperationException: on adding video frame in PPT file
• Object Reference Exception is thrown on saving the file
• Charts series and y-axis labels are improperly rendered in generated thumbnails
• Chart is improperly rendered in generated thumbnail
• Exception: This export format is not implemented for PPT yet when saving presentation using HttpResponse
• TextFrame is surrounded with black border in Aspose.Slides saved presentation
• Cloning slide with embedded video throws presenation repair message
• ArgumentOutOfRangeException is thrown on opening the PPTX file
• ArgumentOutOfRangeException exception on saving presentation
• Slide Text missing in generated PDF
• PowerPoint found content in presentaion that it did not understand
• Missing SmartArt in the generated PDF file
• Smart Art not appearing in the generated PDF file
• SmartArt is missing in generated thumbnail
• InvertIfNegative property is set to true when series data point color is set
• PowerPoint 2007 throw error message on opening Aspose.Slides generated presenation
• Smart Art missing in the generated PNG file
• Chart improperly rendered in generated thumbnail
• SmartArt shapes distortions in generated PDF
• SmartArt is missing in generated PDF
• SmartArt shape is corrupted when Smart Art text is accessed and changed
• Aspose.Slides failed to read the master theme name for presentaiton
• Shape improperly rendered
• Font family changed for the text of SmartArt in generated thumbnail
• Circle around shapes failed to render
• Text missing from rendered SmartArt
• Add shapes to group shape corrupts presentation

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 you can create, access, copy, clone, edit and delete slides in your 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.

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

Get PDF Page Count without Saving & Enhanced PDF to TIFF Conversion Using Java

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Pdf for Java 10.1.0. It provides some exciting features which are already supported in its sibling (Aspose.Pdf for .NET). Among these new features, the bugs reported in previous release are also resolved. Unless the PDF file is saved and all the elements are actually placed inside the PDF document, we cannot (because we cannot be certain about the number of get the page count for particular document pages in which all the elements will be accommodated). However starting with release Aspose.Pdf for Java 10.1.0, we have introduced a method named processParagraphs(…) which provides the feature to get page count for PDF document, without saving the file. So we can get page count information on the fly. Please try using following code snippet to accomplish this requirement. In every new release, we make some modifications in API and the modifications include changes in class names, change in method name, new overloads for existing method etc. These changes are made to correct any spelling mistakes, support new feature requests, removal of redundant features implementation etc. As well as the enhancements and features discussed above, there have been numerous fixes related to recently introduced PDF to TIFF and TIFF to PDF conversion, adding watermark/stamp objects, printing PDF documents, SVG to PDF conversion and much more. Some important improved features included in this release are given below

• Incorrect Rectangle values
• Evaluation watermark not appearing when printing PDF file
• PDF to JPEG - taking much time and memory
• PDF to TIFF - output is garbled
• Unable to modify FreeTextAnnotation in PDF
• Exception when trying to add watermark
• PdfFileMend - Image is not appearing in resultant PDF file
• Error when using setPrintable() method
• Memory leakage in document.save method
• PdfViewer: Print range of pages
• PdfViewer: Printing PDF document issue
• Line drawn using PdfContentEditor is missing in printout           
• TIFF to PDF - Exception during conversion
• PDF to PNG - OutOfMemory Exception is being generated
• TIFF to PDF: pages are being rendered in blue color
• TIFF to PDF - Color of text is being changed in PDF
• Image to PDF: multipage Tiff image is not rendering completely
• Password prompt when viewing document
• aspose-pdf: Security.setUserPassword does not work after V 4.2.1
• save asks for "execute" permission
• SVG to PDF: Image won't be inserted

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.\

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

Databar Stacked Codes Generation/Recognition & Patch Code Encoding in Java Apps

What’s new in this release?

The new version of Aspose.BarCode for Java 6.8.0 has been released. This new release supports the DataBar Stacked, DataBar Expanded and DataBar Stacked Omnidirectional symbologies. Our users can now add encoding and decoding operations to their Java applications. DataBar stacked is a variation of the RSS-14 symbology that is stacked in two rows and is used when the normal symbol would be too wide for the application. This new release also supports encoding of Patch Code symbology, includes a new Line Codes Restoration filter, allows to check the license status. Previously, we were providing two jar files. One for the JDK 1.4 and higher versions and other for the JDK 1.6 and higher versions. In this new release, we have dropped the support of JDK 1.4 and JDK 1.5. Since, we have provided a single jar for JDK 1.6 or higher versions. It is because both JDKs are discontinued by Sun/Oracle. Even commercial (non-open) support of JDK 1.5 is dropped about a year ago. If you are presently using JDK 1.4.x or 1.5.x, you must upgrade your JDK prior to migrating to this new release. It also supports DataBar Stacked, DataBar Expanded Stacked and DataBar Stacked Omnidirectional Symbologies. We’ve added encoding support of Patch code symbology, whereas decoding capability is already present. The Patch Codes aid in batch scanning of documents. It is a specific barcode and often is used in whole pages. We’ve added a new Line Codes Restoration filter. This filter restores corrupted strokes for 1D barcodes. This degradation could come from dirty, dusty products or discarded barcode resulting in touched or missing parts of the bars. The major areas include enhancing of the barcode image,  improve accuracy of recognition, stop cropping of code text while change in resolution and improve recognition performance. This release comprises a number of key fixes that help us reading and writing capabilities.  Below is the list of main improved features and bug fixes added in this release.

• Add support for Databar stacked codes generation/recognition
• String index out of range error message while generating a Code128 symbology
• code39 barcode not found from scanned tif image
• Move Java APIs Code Baseline to JDK 1.6
• Incorrect recognition of a linear code from JPG image
• Can't recognize Code39 codes from the JPG file
• Can't recognize PDF417 barcode from the TIF image
• Can't recognize PDF417 barcode from the TIF image
• Cropped text after resolution changing
• Incorrect GS1Code128 bars pattern/sequence
• InvalidOperationException while recognizing an Interleaved2of5 code
• Can't read Code39 from the tif file
• Can't recognize QR code form the PDF document
• Incorrect recognition of Code128 code from the jpg image
• Performance issue while reading PDF417 and Code128 codes
• Incorrect GS1Code128 bars sequence
• Add support to encode PatchCode symbology
• Can't generate a Databar Expanded code with a specified string
• Unable to recognize second EAN13 barcode from jpg image
• Can't recognize Code128 code from the TIF image
• Incorrect recognition of Code128 code from the tif image
• Incorrect type recognition of UPC and EAN barcodes
• Multiple incorrect recognitions of a single Pharmacode
• Incorrect recognition of Pharmacode from the JPG image
• Can't read Code128 barcode from JPG image
• Incorrection recognition of PDF417 code from the tif format
• Can't put two FNC1 characters in type GS1 DataMatrix
• Can't recognize PDF417 code from png image
• Can't recognize PDF417 code from png image
• Can't recognize PDF417 code from png image
• Can't recognize DataMatrix code from a tif file
• Incorrect recognition of Code128 codes from a tif file

Include "End User Agreement.html" file in Non-MSI packages

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.

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

Send DKIM Signed Emails & Pre-Fetch Message Size from Exchange Server using .NET

What's New in this Release?

We are pleased to announce the release of Aspose.Email for .NET 5.2.0. With this month’s release, you can now send DKIM signed emails. We have also provided the facility to fetch message size from Exchange server before the whole message is fetched.  This month’s release provides the feature of signing email messages with DKIM (Domain Keys Identified Mail) that enables organizations to take responsibility for the message that is in transit. A digital signature is added to the email message headers using the user defined private keys. The API’s MailMessage class provides the method DKIMSign that uses the Crypto Service Provider and DKIM Signature Info for signing the message. Once signed, the message can be sent using the API’s SMTP as well as Exchange Clients. Outlook InterOp provides the feature of retrieving message size before actually fetching the complete message from the Exchange server. In case of Aspose.Email API, the summary information retrieved from Exchange server is represented by ExchangeMessageInfo class and represents the only information that is fetched before actually retrieving the whole message. This month’s release enhances the functionality provided by this class to fetch message size as well before the complete message is fetched from the server. This information is represented by the Size property of the class. We have also enhanced the ImapQueryBuilder for specifying search string encoding while listing messages from IMAP server. This helps querying the strings that are, for example, in Unicode format and were not supported earlier. An example is Turkish characters such as ğüşıöç. This month’s release also fixes a number of bugs that were discovered by our valued customers while working with our API. We have fixed them all, resulting in improved API functionality. Some of these include issues related to TNEF messages sending via SMTP and Exchange clients, Encoding issues while converting messages to other formats, issues related to PST during exporting messages, exceptions while listing messages from IMAP client, loading certain message files and converting messages to TIFF and Exchange Server. The main bug fixes, new & improved features added in this release are listed below

• Add the DomainKeys Identified Mail (DKIM) signature to the email message headers
• EWS: Can there be any way of retreiving Message size before actually fetching it?
• Check oauth support for SMTP and IMAP clients for Yahoo and Yandex mail servers. Make TokenProvider as server-independent class if possible.
• Refactoring properties Body and TextBody of MailMessage.
• Provision of flag to avoid validity check while adding header values to HeaderCollection
• Behavior of connectin gto Exchagne Server on nonsecure port (143) and negotiate secure connection
• MSG created from TNEF attachment doesn't open in Outlook
• MailMessage.Subjec loses the ending "space"
• DOCx->MHTML->MSG->Send using Outlook: Line Breaks are no more respected
• Changing the embedded message name of TNEF formatted EML does not take effect
• System.NullReferenceException raised while conversion of EML to MSG
• IEWSClient: Appending InterpretAsTNEFDraft message includes Winmail.dat in message attachments
• MapiMessage with more than 1020 inline images cannot be added to PST folder
• IEWSClient: InterpretAsTnef changes message class when appended to Inbox
• Message printing: problem with russian charset
• Mail subject is corrupted after load and save it as EML
• MailMessage.Load converts embedded inline image to attachment.
• MailMessage.Save as HTML to MemoryStream closes the stream
• MSG to PST: Subject Encoding issue

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.

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

HTML5 Spreadsheet Editor V1.6: Add Formula Bar, Change Background & Font Color

What's New in this Release?

Aspose team is happy to announce the release of HTML5 Spreadsheet Editor 1.6.0. Html5 Spreadsheet Editor is a web application that can view and edit spreadsheet documents in a web browser. It supports Excel, SpreadsheetML, CSV, OpenDocument and many other formats supported by Microsoft Excel. All basic features including cell editing, formatting, formula editing, row and column management etc. are supported. HTML5 Spreadsheet Editor uses many features of Aspose.Cells for Java and shows how to use them to create, manipulate and render a spreadsheet in your Java application. Below is the list of important new features included in this release.

• Change font color
• Change background color
• Add formula bar
• Add a box beside formula bar to see current cell
• Add button beside formula bar to insert a formula in current cell
• Bug fix: Cell editing modifies value of wrong cell on orignal sheet
• Bug fix: Editing an empty cell in a new sheet results in very big text.
• Removed confusion caused by cell editor while editing a cell with long text
• Add support to CellsService for clean cache
• Add support to LoaderService to unload Workbook objects
• Clean up server resources when user close the spreadsheet
• Aspose Color to CSS color conversion is now more simplified
• Add a separate service for Workbook for workbook related tasks including add/remove sheets, loading/unloading, save and export etc.
• Add custom JSF renderer to render inline cell editor
• Add Logger to all classes to ease tracing of errors and debugging
• Optimized code. Fixed 103 issues reported by SonarQube

About Aspose
Aspose offers a powerful set of file management components with which developers can create applications which can open, edit, create and save some of the most popular business file formats. Supported formats include Word documents, Excel spreadsheets, PowerPoint presentations, PDF documents, and Microsoft Project files. Tools allow developers to perform OCR, work with images, create and read barcodes and perform many other document conversion and management tasks. Aspose produce components for .NET, Java and SharePoint, as well as rendering extensions for SQL Server Reporting Services and JasperReports exporters.

• Aspose for Java components
• Download the complete source code

Retrieve OneNote Document Nodes & IOneNote Table Export inside .NET Apps

What’s new in this release?

We are pleased to announce the release of Aspose.Note for .NET 1.4.0. In this major build, we have optimized the parsing algorithm of OneNote document, and border lines of the table can be preserved in the output PDF and thumbnail formats. We have also added a new generic approach to retrieve OneNote document nodes and the older one has been marked as obsolete. This release also includes the most recent bug fixes along with the above enhancements. This release comprises a number of key fixes that help us improve accuracy, performance and rendering capabilities. Some of them includes OneNote to PDF conversion, can’t open the output PDF file, OneNote to PDF conversion, some words cannot be shown, OneNote to PDF conversion, the table borders are not preserved, OneNote to PDF conversion, the date text overlaps with time, InvalidOperationException occurred while loading OneNote document, Argument Exception message while exports of OneNote to PDF format, Invalid data error while loading OneNote document and several other. The main features and bug fixes added in this release are listed below

• Drawing table lines during PDF or Image export.
• Optimized the parsing algorithm of OneNote file.
• New generic method CompositeNode.GetChildNodes<T>().
• OneNote to PDF conversion, can't open the output PDF file
• InvalidOperationException occurred while loading OneNote document
• OneNote to PDF conversion, some words cannot be shown
• Argument Exception message while exporting OneNote to PDF format
• OneNote to PDF conversion, the table borders are not preserved
• Invalid data error while loading OneNote document
• OneNote to PDF conversion, the date text overlaps with time
• Invalid data error while loading OneNote document

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.

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

Custom Barcode Generator & Better Layout Engine for Handling RTL Text in Word Docs

What's New in this Release?
 
Aspose development team is happy to announce the monthly release of Aspose.Words for Java &.NET 15.3.0.  This month’s release contains over 138 useful new features, enhancements and bug fixes to the Aspose.Words products. Here is a look at just a few of the biggest features and API changes in this month’s release, improvements in the layout engine for handling RTL text, text boxes, cell vertical alignment and others, improvements in import/export for all file formats, Optimized output size of PDF documents for some cases, Document.WarningCallback property can now send you loss of formatting warnings at any time during document lifetime, not only during saving, Fields are now updated inside DrawingML shapes, ShapeRenderer.OpaqueBoundsInPoints returns the “real” shape bounds, improvements in rendering of fills, 3D text effects and others, the DISPLAYBARCODE field is supported now so you can add a custom barcode generator and many more. It also support generating a custom BarCode image for dISPLAYBARCODE field. It also add a new method that inserts content to a document at the current position of DocumentBuilder’s cursor. The Document can raise warnings at any stage of its life cycle. So, to be able to receive all the warnings, a new property was added into DocumentBase class. New property OpaqueBoundsInPoints and method GetOpaqueRectangleInPixels have been added to ShapeRenderer class. They allow getting opaque bounds of the shape in points. Before this option was introduced it had been needed to work with raw pixel data to get this bound. The list of new and improved features added in this release are given below

• Improvements in the layout engine for handling RTL text, text boxes, cell vertical alignment and others.
• Improvements in import/export for all file formats.
• Optimized output size of PDF documents for some cases.
• Document.WarningCallback property can now send you loss of formatting warnings at anytime during document lifetime, not only during saving.
• Fields are now updated inside DrawingML shapes.
• ShapeRenderer.OpaqueBoundsInPoints returns the "real" shape bounds.
• Improvements in rendering of fills, 3D text effects and others.
• The BARCODE field is supported now so you can add a custom barcode generator.
• Add feature to support HTML TextArea tag to load into DOM same as MS Word does
• Aspose.Words corrupts the document when saving from DOCX to WordML
• Support for DISPLAYBARCODE merge field
• Export Content Controls as SDT tags in HTML
• Implement support for new AbsolutePositionTab model node.
• Add feature to implement IWarningCallback for Document.RenderToSize method
• Issue with resizing DrawingML node
• Aspose.Words.FileCorruptedException occurs when specifying password via LoadOptions
• Document.AppendDocument throws System.ArgumentException for cloned documents
• Footer position is changed after conversion from Docx to Pdf
• Throw warning using IWarningCallback when an image is unavailable
• Doc to Pdf conversion issue with footer position
• DrawingML shape that simultaneously has 3D effect and others effects is rendered incorrectly (except simultaneous applying three effects - 3D effect, Outer shadow and Reflection)
• Header content does not render correctly in HtmlFixed
• Frames with inline shapes truncated, wrapped incorrectly in a multi-column section
• Consider support of CSS3 paged media attributes
• Page Background specified using picture is not displayed in HTML.
• Space appears between two inline images in HTML output
• Size of image is incorrect after inserting to document.
• document to pdf conversion, shape width increase
• Space between number and text in a heading is incorrect when rendering
• Docx to PDF conversion issue with table
• Table is not being rendered properly during conversion DOC to PNG
• Text formatting issue while converting Docx to Pdf
• Table in footer has incorrect width.
• Docx to PDf conversion issue, text misplaced
• Position of floating DrawingML is incorrect after exporting Docx to HTML
• Bullet symbols in SmartArt are not rendering in Pdf
• Odt tracked changes sorting differ
• Incorrect formatting of slashes in number format of chart axis label.
• Thin line disappear.
• Some TIFF Images are missing after re-saving Doc
• DataColumn doesn't support dataTypes if it was created directly (without ResultSet)
• Too long conversion to png of metafile image with Gradient fill.
• UTF7 Encoding regression.
• Fields in shapes // Aspose.Words does not update SECTIONPAGES fields automatically
• DocumentBuilder.InsertImage lose original size of image
• Doc to Pdf conversion issue with SYMBOL 168
• Doc to RTF conversion issue with TextBox orientation
• Comments indication are shifted to the right in FF/Chrome for the document
• Aspose.Words generated PDF output does not match MS Word
• Aspose.Words corrupts the document when saving from DOCX to WordML
• Bullets are missing from SmartArt when Docx is exported to Pdf/Doc
• Image width/height are not being set correctly in DOCX when aspect ratio is locked
• Text position is changed after conversion from Docx to Pdf
• DrawingML.Width and DrawingML.Height do not work
• Doc to Pdf conversion issue with footer's contents
• Table's header row is missing after re-saving the Doc file
• Position of table's contents are changed after re-saving Doc file
• Document.Save corrupts the Hyperlinks
• Bug whereby comments appear in wrong place when converting RTF to Word format
• The text formatting of DrawingML is lost after converting from Docx to Pdf/HTML
• Text color of DrawingML is lost after conversion from Docx to Pdf/Html/Doc/Docx
• Blue lines appear when converting a flow chart to PDF
• Tab characters are added after re-saving RTF
• Incorrect representation of RTL text in HTML DOM
• Bookmark position is changed after conversion from Doc to Html
• Border should not be visible in Aspose.Words generated output documents
• Some entries of TOC are pushed down to the next page in PDF
• HTML to Docx/Doc issue with left indentation
• Docx to Pdf conversion issue with left indentation of list items
• Issues with table heights in PDF
• Html to Doc/Pdf/Html conversion issue with Arial black font
• ParagraphFormat.LeftIndent return incorrect value
• Incorrect Y position is returned by LayoutEnumerator
• Twip-based attributes with fractional parts rounds up for DOCX or WML.

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.

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

Get Decoded Values from Message Headers & Preserve Original Email Address using Java

What’s new in this release?

We are pleased to announce the new release of Aspose.Email for Java 5.1.0. For a complete list of enhancements and improvements, please visit the product download page. Complete list of API changes in this recent version can be found in our documentation article, Public API Changes in Aspose.Email for Java. Message headers include encoding characters along with normal message text. This month’s release provides the capability of getting decoded header values using the getDecodedValue method of HeaderCollection. This month’s release also includes an enhancement of preserving original email addresses that may contain malformed/invalid characters. Such characters can be part of the mail address in cases, for example, where the email is received internally within organization from Exchange server. The setPreserverOriginalAddresses can be used to ignore the validity check while converting MailMessage to MapiMessage. This release also includes an enhancement where message’s HTML body equivalent text can be retrieved if the HTML information is malformed due to some reason. This can be achieved using the getHtmlBodyText method of MailMessage class. Ported form its equivalent .NET version, this month’s release also includes a number of bug fixes which further improves the API functionality. These include issues related to PST such as sender name not shown in PST, corrupt task and meeting body while adding tasks to PST, and exceptions while extracting messages from a PST, encoding issues while converting messages from one format to another and Exception while loading appointment from ICS, loading EML files and EML to MHT conversions.  The main improved features & bug fixes added in this release are listed below

• OAuth support for SMTP and IMAP clients for Outlook.com
• Option to save original email address with invalid characters in MapiMessage - Java
• Encoded header "Thread-Topic" not visible properly
• Take value of Body from PR_HTML if Body Property is disturbed
• Sender Name not shown in PST
• MailMessage.Subject returns wrong Subject
• Message body garbled while loading from Mhtml and sending through Outlook
• Task body corrupted after adding it to PST
• Meeting body corrupted after adding to PST
• Appointment body and reminder values corrupted after adding to PST
• The MimeBasePart.DecodeHeaderValue method not working properly
• Saved message formatting corrupted after sending it
• Dynamic Tag not working in template MSG file

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

OCR & OMR Features are Now Combined into a Single Component

What’s new in this release?

We are pleased to announce the new release of Aspose.OCR for .NET 2.4.0. In this merged version, we have combined the Aspose.OCR & Aspose.OMR namespaces in one assembly and published it as Aspose.OCR for .NET 2.4.0. Now you can use the single component to work with both OCR & OMR features without even changing your existing code. From API point of view, nothing has changed. All the classes, method, enumerations & properties that were previously present in Aspose.OMR namespace still reside there, whereas all the APIs relevant to OCR features still belong to Aspose.OCR namespace.  In order to keep this transition simple, we haven’t changed anything in the public API so you do not need to worry about changing your existing code to accommodate this merger. However, number of assemblies for the Aspose.OCR for .NET package have been reduced to one, that mean; you can use the single assembly (Aspose.OCR.dll) for both OCR & OMR features from now onward. This release has addressed a few critical issues and has incorporated some enhancements such as fixed the implementation of IRecognitionBlock.RecognitionData that used to return null for the custom recognition blocks. Due to this issue, the API didn’t allow to retrieve the symbols & words that belongs to a specific block on image, fixed the problem with invalid overloaded comparer that used to trigger the ArgumentException at OcrEngine.Process, improved the exception handling for the cases where OMR elements have invalid dimensions and several others.  This release includes plenty of new & improved features as listed below

• IRecognitionBlock.RecognitionData always returns Null
• Merge OMR functionality into Aspose.OCR assembly
• Support Ctrl+A hotkey
• System.IndexOutOfRangeException at OmrEngine.ExtractData
• ArgumentException: IComparer (or the IComparable methods it relies upon) did not return zero when Array.Sort called x. CompareTo(x). x... at OcrEngine.Process
• Provide a meaningful exception message when OCR element dimensions are out of image bounds

Other most recent bug fixes are also included in this release

Overview: Aspose.OCR for .NET

Aspose.OCR for .NET is a character recognition component built to allow developers to add OCR functionality in their ASP .NET 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 (BMP, TIFF) files from within their own applications. It allows developers to extract text from images quickly & easily, saving time & effort involved in developing an OCR solution from scratch.

• Homepage of Aspose.OCR for .NET
• DownloadAspose.OCR for .NET

Create Hyperlinks to Sections in Same PDF & PDF Contents Redaction in .NET Apps

What's New in this Release?

We are pleased to announce the release of Aspose.Pdf for .NET 10.2.0. We all are very well versed that data is very important and critical for individual as well as for organizations, and we prevent our data form unauthorized access through encryption and data encapsulation. Aspose.Pdf for .NET is great when it comes to applying security restrictions and specifying access privileges over PDF documents. Recently we came across a requirement to redact certain page region so that information cannot be viewed/access/copied by customers receiving the documents. So in order to accomplish this requirement, we have enhanced our Annotations feature. We know that Aspose.Pdf for .NET provides the feature to add as well as manipulate Annotations in existing PDF file, so in order to further enhance the powers of Annotations, a new class named RedactionAnnotation is provided, which can be used to redact certain page region or it can be used to manipulate existing RedactionAnnotations and redact them (i.e. flatten annotation and remove text under it). Aspose.Pdf for .NET provides great feature to PDF creation as well as its manipulation. It also offers the feature to add links to PDF pages and a link can either direct to pages in another PDF file, a web URL, link to launch an Application or even link to pages in same PDF file. In order to add local hyperlinks (links to pages in same PDF file), a class named LocalHyperlink is added to Aspose.Pdf namespace and this class has a property named TargetPageNumber, which is used to specify the target/destination page for hyperlink. Aspose.Pdf for .NET provides the capabilities to transform HTML file to PDF format and vice versa, it offers the feature to render PDF pages to HTML format. We know that due to open standards of HTML, the format is quite complex and due to custom implementation of these standards, errors may occur during HTML to PDF conversion. With every new release, we are trying our level best to make the feature to HTML to PDF conversion as stable and viable as we can. Even in this release, the HTML to PDF conversion has been one of the key improvement areas. Please note we have modified our API to cater the requirement of suppressing unsupported tags exception (which may occur) when new/custom HTML tags are parsed through our API, so that no exception / error should be displayed and HTML to PDF transformation process is completed without any intervention. An HTML file may reference external resources such as Image or CSS and during HTML to PDF conversion, we need to provide the path towards these resources, so that they are properly rendered inside resultant PDF. As well as the enhancements and features discussed above, there have been specific improvement for PDF to HTML and HTML to PDF conversion features. Among these fixes, the PCL to PDF, SVG to PDF, PDF to Excel, PDF to DOC, PDF to TIFF and TIFF to PDF conversion, conversion of PDF to PDF/A compliant documents, text replacement, rendering PDF files to XPS format are also improved. The list of important new and improved features are given below

• Support for PDF contents Redaction is required
• Support LinkPageNumber property for TextFragment object
• HTML to PDF conversion - Line break issue
• HTML to PDF conversion - Formatting Issues
• Hyperlink feature in TextSegment
• While converting TIFF to PDF, resultant file is much larger
• HTML to PDF: Suppress unsupported html tags exception
• Support of relative path in HTML to PDF conversion
• TextSegment should support hyperlink property
• HTML to PDF: support of absolute value of CSS position property
• To get rectangle of Cell Text
• Wrong Text Extraction from XPS Document
• PDF to PDF/A-2A compliance fails
• PDF to HTML - Text is Displaced in resultant HTML
• PDF to DOC: text is misplaced
• PDF to HTML - text is overlapping in resultant file
• CircleAnnotation disappears when flattening the document
• SquareAnnotation missing from flattened document
• LineAnnotations missing from flattened document
• Font embedded became true after save
• Multipage TIFF to PDF conversion - Images size issue
• Incorrect page count being returned
• When using SetPageSize(..), the page gets cropped
• Text formatting is lost when converting HTML file to PDF
• HTML to PDF conversion formatting issues.
• Formatting issues during HTML to PDF conversion
• HTML to PDF conversion problem
• Problem loading/formatting pdf via html and css inline
• HTML to PDF: Resultant PDF is 0KB
• PDF to HTML - Contents in resultant file are upside down
• HTML to PDF: Page contents go beyond right page margin
• Convert HTML to PDF not respecting CSS/ IsFitToPage
• HTML to PDF: Single table is split into multiple tables
• HTML to PDF: Table cell data is splitting over two pages
• HTML to PDF: Bottom border is missing in last row of table
• HTML to PDF: Top border is missing in first row of table in subsequent pages
• HTML to PDF - Dotted Underline in HTML not visible in PDF
• HTML to PDF rendering issue, text goes off the page
• Text Fragments Not Being Fully Replaced
• HTML to PDF - Some objects are not appearing on correct location
• PDF Read Out Loud is not working properly when PDF is Creating with PdfConformance.PdfA1A
• Text replace feature is not working when Regional settings are Turkish
• TextFragmentAbsorber gets wrong coordinates of seached Text
• Strange output when converting html to pdf
• Replace text changes space between characters
• Text Replace is not working
• CPU usage rises to 100% while using TextAbsorber in Multi-threaded envoirnment
• Incorrect page count in TOC
• Printed output is not good quality
• ProcessParagraphs() method does not update table cell contents
• Unexpected behavior of GetHashCode() method of CommandParameterCache class
• Bug Converting PDF to PNG (Some Characters are missing)
• Thai text get lost and scrambbled when converting PDF pages as images
• Text replace and add image feature increases the PDF file size
• Watermark not showing on resultant PDF

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

Overview: Aspose.Pdf for .NET

Aspose.Pdf is a .Net Pdf component for the creation and manipulation of Pdf documents without using Adobe Acrobat. Create PDF by API, XML templates & XSL-FO files. It supports form field creation, PDF compression options, table creation & manipulation, graph objects, extensive hyperlink functionality, extended security controls, custom font handling, add or remove bookmarks; TOC; attachments & annotations; import or export PDF form data and many more. Also convert HTML, XSL-FO and MS WORD to PDF.

• Homepage of Aspose.Pdf for .NET C#
• Online Demo for Aspose.Pdf for .NET

Fax: 866.810.9465

Set Automatic Fill Color for Chart & Verify Presentation Format without Loading

What's New in this Release?

The long awaited version of Aspose.Slides for Java (15.2.0) has been released.
We have introduced support for setting automatic fill color for chart series based on presentation theme. Now, users don’t have to bother for setting the individual series colors. More details about the supported feature are available in the article Setting Automatic Series Fill Color. We have also provided support for verifying the presentation file format without even loading it using Aspose.Slides Presentation class object that actually loads the entire presentation and then tells its format description. The PresentationFactory class now offers support to get the valid presentation file format before loading that. We have improved the presentation rendering support and have resolved certain rendering issues incurring during generation of slide thumbnails, exported PDF, Tiff, SVG and XPS files in Windows, Linux\Unix and MAC platforms. The issues include improper text, missing background, blank slides, improper SmartArt, incorrect table and different charts elements rendering. We have rectified issues that appeared when accessing, saving and rendering presentation to PDF, HTML or slide thumbnails, which resulted in different exceptions like NullReference, PptxReadException, ObjectReferenceException,and IllegalArgumentException in previous releases for MAC, Linux and Windows environments. Some important enhancement & bug fixes included in this release are given below

• RemoveAt method for chart series data point collection is missing
• To get Fill Color of Series when Fill Type is Automatic
• Implement all types of hyperlink monikers
• Support for availability of same property for getting the file format as of Aspsoe.Cells and Aspsoe.Words
• The slide background is wrongly rendered in generated PDF
• IllegalArgumentException on accessing the presentation
• IWarningCallback implementation for font substitution does not completely show the font name
• Chart thumbnail is improperly rendered using Aspose.Slides for Java
• Deadlock in Presentation (com.aspose.slides.acm.do) in multithread mode
• Bullets are missing in generated thumbnails
• PPTX is converted to byte array and loaded causes issue
• Bullets are improperly rendered in generated thumbnail
• Content is not showing in the generated HTML file
• Image quality is not good when converting PPTX to Image conversion
• Bitmap. throws java.lang.ArrayIndexOutOfBoundsException: 74
• Aspose.Slides failed to read the master theme name for presentaiton
• Text improperly rendered in generated thumbnail
• Slide thumbnail is improperly rendered in MAC environment
• Error message pops up on opening Aspose.Slides modified presentation
• Chart value axis text is not fitting inside defined filled area
• Chart data in plot area is missing in generated thumbnail
• Chart category axis is improperly rendered in generated thumbnails
• Bitmap. throws IOException: Error reading PNG image data
• Java.lang.AssertionError: Cannot read a name from the name table in a font. when converting PPTX to PDF on Solaris
• Text rendered with blue color in generated slide thumbnails
• Background color blending allignments changing after transforming to PDF
• Paragraph spacing changed for Aspose.Slides generated text frame text if font is changed
• Font size in PDF and in thumbnails is bigger than in original PPTX

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.

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