Read, Write Data of Visio Shapes & Detect Format of Macro Enabled Visio Drawings using .NET

What’s new in this release?
Aspose team is pleased to announce the new release of Aspose.Diagram for .NET 17.4.0. Developers can deem the best workflow for their .NET project applications. The new API version allows developers to detect the format of macro enabled Visio drawings, modify the VBA project in the VDX drawings, apply settings over headers and footers as well as retrieve data of the Visio shapes with more accuracy and performance. Developers can also install an Aspose.Diagram Nuget package in their .NET applications because we publish each version as a NuGet package on the NuGet gallery.Aspose.Diagram for .NET API has already added support of detecting the format of all Visio files. A client was not able to detect the format of their macro enabled drawings. Using the new API version, developers can now take benefit of an Enhancement to detect the format of macro enabled drawings with high accuracy. The API provides the capabilities of reading and writing data of Visio shapes. Using this new release, developers can find improvements in reading and writing properties of Visio shapes. A help topic is provided on blog announcement page that shows how developers can manipulate with data of Visio shapes. In general, the recent release improves export of the VSD and VSDX drawings to SVG, prevents API to miss shapes during export and also improves the layout structure of connectors.  Here is the list of important enhancements and bugs fixes in the new version.

• Improve setting the UIVisibility of Visio Page
• Detecting format of VSDM, VSSM and VSTM files
• Header/footer settings cannot be read from vsdx file
• Cannot modify VBA Project in the VDX
• Cannot retrieve Unique ID of a VSDX drawing
• Retrieves an incorrect type value of the Shape data for VSDM
• The connecting lines are not connected while creating a VDX
• The connectors in the VDX are not connecting shapes properly
• ObjectDisposedException is thrown when saving a diagram multiple times
• Shapes are missing in output VSDX 
• The Font is not set for a shape           
• Cannot retrieve from and to part of the connect of VDX     
• Visio cannot open VSDX file when GIF image is added
• Does not preserve compound type of the connector shape in VSDX
• The arrow button is not being displayed correctly on converting a VSDM to SVG
• A duplicated text line is over-written while converting a VSDM to SVG
• Incorrect layout of connectors on saving in the VSDX format
• Incorrect layout of connectors on saving in the PDF format
• Missing shapes on converting a VSD to PDF
• Displaced shapes on converting a VSD to PDF
• VDX file is corrupted after saving - II
• Responsibility box at bottom of the shape is partially shaded on saving a VDX to SVG
• The text phrases are not being spaced correctly on saving a VDX to SVG
• An additional text appeared on saving a VDX to SVG
• The text items are overlapping on saving a VSDM to SVG
• ArgumentOutOfRangeException on diagram saving
• Images are missing in saving VSDX
• Displaced text and a missing character on converting a VSDM to SVG
• Incorrect display at the bottom on converting a VSDM to SVG
• VDX file is corrupted after saving - I
• An error occurred on saving a drawing in PNG - I
• An error occurred on saving a drawing in PNG - II
• Cannot retrieve the accurate date and time value when the drawing was last saved
• A rectangle shape is being rendered on converting a VSD to JPG

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

• Add, Retrieve, Copy and Read Visio Shape Data
• Detect the Format of Visio File

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.
More about Aspose.Diagram for .NET

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

Microsoft Excel 2007 Themes/Colors Support & Delete Comments in Excel Worksheet in Cloud Apps

What's New in this Release?

We are pleased to announce the new release of Aspose.Cells for Cloud 17.5.0. Aspose.Cells for Cloud is a platform independent REST API that allows developers to process their Excel files on Cloud. This new release comes up with a couple of new features. Developers can delete all comments in an Excel worksheet and apply Microsoft Excel 2007 themes and color. It has also made enhancements to Import Data API, Copy Worksheet API, Task API and Convert API.  Using comments API users can delete all comments in a worksheet. This API also allows users to get all comments from a worksheet. The cellStyle API now also supports Microsoft Excel 2007 Themes and Colors. Using this API, users can update Cells’ Style in a worksheet and also get Cell’s Style information from a worksheet. The Convert API allows users to convert Spreadsheet to a number of different formats (e.g., text, html, Pdf, Tiff). This API accepts Spreadsheet Document and Save Options data in the request body and return converted the document in API’s response. Import Data API allows users to import data from an external file into a worksheet. It has both the options, to send data file in request body or to upload it to Cloud Storage. This API allows users to copy a worksheet and save with new name in the same workbook. Now users specify more Copy Options like CopyNames, ExtendToAdjacentRange and ReferToSheetWithSameName.  The list of new and enhanced features added in this release are given below

• Clear comments in the worksheet.
• Support Microsoft Excel 2007 themes and colors.
• An enhancement is made for Convert feature.
• Task API now also supports Request file.
• New resource parameters are added in Copy Worksheet API.         
• Import Data API now supports both Cloud file and Request file.   

Start a free trial today – all users need is to sign up with the Aspose for Cloud service. Once users have signed up, users are ready to try the powerful file processing features offered by Aspose for Cloud.

Overview: Aspose for Cloud

Aspose for Cloud is a cloud-based document generation, conversion and automation platform for developers that offer a unique suite of APIs to work with Word documents, Excel spreadsheets, PowerPoint presentations, PDFs, and email formats and protocols. It supports all features for file processing, document scanning, barcodes creation and recognition, and allows extracting text or images too. Users can also work with SaaSpose APIs using REST SDKs that can be called from .NET, Java, PHP and Ruby etc.

More about Aspose for Cloud

• Learn More about Aspose.Cells for Cloud
• Download Aspose.Cells for Cloud
• Aspose.Cells for Cloud Documentation

Bind Content Controls with XML Data (Custom XML Part) in Word Documents inside Java & .NET Apps

What's New in this Release?
Aspose development team is happy to announce the monthly release of Aspose.Words for Java & .NET 17.5.0. This month’s release contains over 84 useful new features, enhancements and bug fixes. Here is a look at just a few of the biggest features and API changes in this month’s release; MailMerge and Metafile Rendering Performance are Improved, Support TOA, IMPORT, INCLUDE, SHAPE Fields,  API to bind SDT to CustomXML Properties is Provided, Implemented Support for ShapeLayoutLikeWW8 Compatibility Option, Improved Calculation of Width of Spaces in Asian Text, Improved Text Wrapping for Lines Consisting of Many Tabs, Improved Layout of Multi-Column Sections When Column Ends with Page Break Followed by Paragraph Break, Alow Resolution Text Rendering to Images Improved, Underlined Text in EMF+ Images are now Rendered into Fixed Page Formats, HtmlFixed Output File Rendering Improved, Image Crop is now Taken into Account While Rendering HtmlFixed, Shaded DrawingML Images Rendering Fixed and DrawingML Charts rendering improved (axis label placement). The method is used to set the amount of space (in points) to add to the left/top/right/bottom of the contents of cell. It has added new feature in Aspose.Words 17.5 to  bind content controls with XML data (custom XML part) in Word documents. The XmlMapping class is used to specify the information that is used to establish a mapping between the parent structured document tag and an XML element stored within a custom XML data part in the document. Aspose team has added CustomXmlPartCollection.Add method in Aspose.Words 17.5. This method creates a new XML part with the specified XML and adds it to the collection. The list of new and improved features added in this release are given below

• MailMerge and Metafile rendering performance are improved.
• Support TOA, IMPORT, INCLUDE, SHAPE fields.
• API to bind SDT to CustomXML properties is provided.
• Implemented support for ShapeLayoutLikeWW8 compatibility option.
• Improved calculation of width of spaces in Asian text.
• Improved text wrapping for lines consisting of many tabs.
• Improved layout of multi-column sections when column ends with page break followed by paragraph break.
• A low resolution text rendering to images improved.
• Underlined text in EMF+ images are now rendered into fixed page formats.
• HtmlFixed output file rendering improved (removing zero-sized text boxes).
• Image crop is now taken into account while rendering HtmlFixed.
• Shaded DrawingML images rendering fixed.
• DrawingML Charts rendering improved (axis label placement).
• Support TOA field
• Support IMPORT field
• Support INCLUDE field
• Support SHAPE field
• Provide an API to bind SDT to CustomXML properties.
• Incorrect text wrapping when a line starts with a huge space
• Outline is incorrect upon converting VML to DML
• Aspose.Words Objects are very verbose
• MHTML import. Image format EMZ is not supported.
• Simplifiy OMath when copying it into toc entry
• Take image crop in account when render to HtmlFixed.
• Documents rendered incorrectly
• Obtain the correct distance between list label and content of list item
• Backslashes and double quotes are not processed properly by the FieldTokenDecoder
• An odd space added between spans at export to PNG
• Rendering RTL tables to GDI/PNG is wrong
• Doc to fixed file format conversion issue with STYLEREF
• non-breaking space. Text position is changed after conversion from Docx to Doc/Pdf
• Aspose.Words does not import the Run nodes correctly in DOM
• space width + BalanceSingleByteDoubleByteWidth. Cell's text moves to next line in output Pdf
• Rtf to Docx conversion issue with spaces's width.
• ShapeLayoutLikeWW8. Doc to Pdf conversion issue with content's position
• Veracode vulnerabilities in running Aspose.Words API code
• ShapeLayoutLikeWW8. Doc to Pdf conversion issue with shape's position
• Bookmark.Remove() removes only some bookmarks.
• Chart is corrupted after conversion from MS WORD to PDF
• List labels are lost after conversion from RTF to PNG
• Image is lost after modifying the output Doc with MS Word 2003.
• Document.AcceptAllRevisions does not accept all tracked changes
• Chart image size seems bigger than original when exporting to HTML
• Embedded Fonts are gone when printing Aspose.Words generated PDF
• If saving to HTML and CssSavingArgs.CssStream is provided, CSS outputs both to the stream and to a file
• Slope of Drawing Line is inversed when opening and saving the document
• Pictures are shifted in rendered documents
• Chart rendering is not accurate.
• Vertical Axis of chart does not render correctly
• Accept revisions cause a text deletion in Cell
• Paragraph space after is changed after mail merge
• Docx to Pdf conversion issue with Shape's text formatting
• FontSettings are not document-bound during import from HTML
• STYLEREF fields in headers resolve in Error when rendering Word document with revisions to PDF
• SVG is not exported in output DOC/PDF
• The stroke of SVG image is lost in output PDF
• Inline styles are used when styles are set to be saved separately
• Html to Docx/Pdf conversion issue with SVG image
• Text color is changed in DOCX to JPG conversion
• Range.Replace method does not replace text in footnote
• Text in DrawingML textboxes missing when converting to PDF
• Paragraph's text is rendered on previous page in output HtmlFixed/Pdf
• Document.AcceptAllRevisions removes the empty paragraph that causes incorrect page layout
• Pages are truncated in output HtmlFixed/PDF
• API throws InvalidCastException upon loading DOCX
• Date field is incorrectly formatted when FieldUpdateCultureSource.FieldCode is used
• Chart's vertical axis are in correct in output PNG
• Chart's vertical axis are rendered as decimal instead of integer
• The minimum axis bound is changed in output PNG
• Axis bounds and units of chart are changed in output PNG
• Incorrect conversion of x-axis data of a Chart
• Docx to PDF conversion issue with image rendering

Other most recent bug fixes are also included in this release
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Words for .NET documentation that may guide users briefly how to use Aspose.Words for performing different tasks like the followings.

• Applying Formatting on the Cell Level
• Binding Content Control to Custom XML Parts

Overview: Aspose.Words

Aspose.Words is a word processing component that enables .NET, Java & Android applications to read, write and modify Word documents without using Microsoft Word. Other useful features include document creation, content and formatting manipulation, mail merge abilities, reporting features, TOC updated/rebuilt, Embedded OOXML, Footnotes rendering and support of DOCX, DOC, WordprocessingML, HTML, XHTML, TXT and PDF formats (requires Aspose.Pdf). It supports both 32-bit and 64-bit operating systems. You can even use Aspose.Words for .NET to build applications with Mono.

More about Aspose.Words

• Homepage Aspose.Words for .NET
• Homepage of Aspose.Words for Java
• Download Aspose.Words for .NET
• Download Aspose.Words for Java
• Online documentation of Aspose.Words

Filter Messages from Exchange Server by Message Size & Identify Folder Type using EWS using Java

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Email for Java 17.5.0. This release allows modifying or deleting occurrences from a recurrence pattern, filtering messages from Exchange server based on message size, identifying folder and message types retrieved from Exchange server, and others. This release provides a new feature of modifying or deleting a specific occurrence from an event’s recurrence pattern. This is achieved using the MapiCalendarExceptionInfo class. Retrieving items from Exchange server folder, such as Deleted Items, can include items of different types. User’s logic is prone to error if items are fetched with the wrong API method. This month’s release provides the capability to get the item type from ExchangeMessageInfo, the summary information about an item, and use the appropriate method to fetch the message from the server as shown in the code sample on blog announcement page. This month’s release also provides the capability to get folder type information from FolderInfo, the summary information about a folder. It has also enhanced the functionality of filtering messages from Exchange Server by providing additional option of filtering messages by message size. Users can now specify a message size to retrieve only those messages that meet the message size criterion. EML files, that have well defined structure, can now be sent out using the API’s SMTP client without first loading in MailMessage. This helps in situations where there are limited memory resources in a system and addition loading of large messages by MailMessage can lead to out of memory issues. This month’s release also fixes several bugs that were either reported with the Java version of the API or with the equivalent .NET API. This further adds to the performance and stability of the API.The main improved features & bug fixes added in this release are listed below

• Option to modify/delete occurrences in a recurrence (.NET)
• Provision of MessageSize in ExchangeQueryBuilder
• Forwarding message without loading EML file using MailMessage
• Option to render selected or all information of an IPM.Contact to Mhtml
• Provide EWSClient.FolderType information in EWS client
• Provision of Message Class information in ExchangeMessageInfo
• Add/Update mail headers via mail merge     
• EWS client can't load emails in folders containing large number of messages.
• RRULE problem creating multiple events on same day
• RRULE problem creating events late by two days
• Restoring Pst to Outlook.Office 365 account causes error in calendar items
• EWSClient.GetContact (s) raises exception for this Exchange account
• Message count different in MBox read by Aspose.Email
• Mails not read from Mbox file - (.NET)
• ICS with RRULE not imported properly into PST
• Resaving MSG file loses the spaces and tabs in HTML body
• All Day Event Checkbox not clicked in Outlook PST created by Aspose.Email
• Sent mail changed to Draft after setting Read/Un-Read flag
• Setting Read/Un-Read flag does not take effect in the PST
• Exception while debugging ImapClient in VS 2017
• EWSClient.CreateFolder raises exception with AE 17.3, whereas worked fine with AE 17.1
• Out Of memory exception when processing Mbox file
• Exception raised while updating attachment name containing double single quote

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

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

MLeader Entity Support, Rendering DWF Files to Images & PDF Files using Java

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.CAD for Java 17.4.0. This is a major product release whereby Aspose team has added support for DWG and DWF file formats. It has enhanced the DWF file format support by including support for new MLeader entity. For more about supported feature, please visit documentation article, Support for MLeader Entity. Now, users can work with DWF files and render them to images and PDF files as per requirement. For more about supported feature, please visit documentation articles, Converting DWF to Raster Image Format and DWF to PDF. This release also includes improved rendering support for DWG file format as well in terms of exporting to PDF and images. There are some important enhancements part of this release, such as Converting DWG layers to PNG image has been improved, converting DWG layers to PDF has been improved and support for DXF and DWG file formats in FileFormat enumeration are further enhanced. The main new features added in this release are listed below

• Support DWF Format
• Support MLeader Entity for DWG format
• Converting DWG to PDF format is producing error
• Add support for DXF and DWG file formats in FileFormat enumeration.
• Converting DWG layers to PDF is producing incomplete text in the resultant PDF
• Converting DWG to PNG is producing incomplete image

Overview:Aspose.CAD for Java

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

More about Aspose.CAD for Java

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

Apply Physically Based Rendering Material to 3D Entities & Import GLTF 2.0 Files using .NET

What’s new in this release?

Aspose team is pleased to announce the release of Aspose.3D for .NET 17.05.0. The new version 17.5 of the API adds support of importing GLTF 2.0 (ASCII and Binary) files in the Aspose.3D API as well as allows developers to apply Physically Based Rendering (PBR) material to 3D entities. Developers may then save the final 3D scene to any supported file format. All other internal improvements are also incorporated. Developers can install Aspose.3D Nuget package in their .NET applications because we publish each version as a NuGet package on the NuGet gallery. Aspose team recommends clients to upgrade old version of the Aspose.3D API with this latest one. GLTF 2.0 (GL Transmission Format) improves the way of storing, transferring and rendering 3D models. With the help of Aspose.3D for .NET API, developers can import existing GLTF 2.0 (ASCII and Binary) models, and then save in any other supported 3D format. Aspose.3D for .NET offers the capabilities to create an instance of any supported 3D entities, set position in a 3D scene, and then save in the supported file format. Developers would now be able to apply Physically Based Rendering material to that entity instance before saving. This help topic helps to know the way of applying Physically Based Rendering material to an instance of 3D entity. This release includes plenty of new features as listed below

• New PBR material to support physically based rendering
• Allow Aspose.3D API to import GLTF 2.0 ASCII files
• Allow Aspose.3D API to import GLTF 2.0 Binary files      

Overview: Aspose.3D for .NET

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

More about Aspose.OCR for .NET

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

MS Excel 2016 Charts Support & Visual Studio 2013 Integration into Reporting Services

What’s new in this release?

The long awaited version of Aspose.Cells for Reporting Services 17.4.0 has been released. This release includes some important features and other enhancements. Aspose.Cells for Reporting Services now supports MS Excel 2016 charts to work with Aspose.Cells for Reporting Services Report Designer tool. Users can manipulate/design MS Excel 2016 charts to create/update the RDL file(s). Using Aspose.Cells for Reporting Services, users can integrate into the reporting services of business intelligence in Visual Studio 2013 for users’ needs. In this release, some useful enhancements and other fixes are added, such as it has added an enhancement for importing/rendering report define file into MS Excel. Moreover, a bug regarding importing GaugePanel is fixed where it failed when importing report definition file into MS Excel. This release includes plenty of new and improved features as listed below

• Support MS Excel 2016 charts to work with Aspose.Cells for Reporting Services Report Designer
• Support to integrate into the reporting services of business intelligence in Visual Studio 2013
• An enhancement is made to import/render report define file into MS Excel
• Import GaugePanel fails when importing report definition file into MS Excel
• Lost variables when open to save

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

Overview: Aspose.Cells for Reporting Services

Aspose.Cells for Reporting Services allows you to export native Excel reports in Microsoft SQL Server 2005 Reporting Services. Unlike the built-in renderer for Excel based reports, Aspose.Cells for Reporting Services provides an extended feature set and allows RDL reports to be converted to: Excel 97-2003 binary XLS format, SpreadsheetML or the Excel2007 XLSX format. With Aspose.Cells Report Designer tool, users can design & deliver reports into MS Excel directly without using Visual Studio IDE.

More about Aspose.Cells for Reporting Services

• Homepage of Aspose.Cells for Reporting Services
• Download Aspose.Cells for Reporting Services
• Online documentation of Aspose.Cells for Reporting Services

Working with GS1 Barcode & QR Barcode Detection are Enhanced using .NET

What's New in this Release?

The latest version of Aspose.BarCode for .NET 17.4.0 has been released. The major development in this release is the improved functionality of GS1 coded barcode. Many time GS1 code texts contain complex combination of digits and letters. Functionality of the GS1 barcode has been upgraded in such a way that it can parse and validate those complex combinations. Functionality of QR coded barcode recognition has also been improved and incorporated in this release. Aspose.BarCode for .NET allows developers to generate GS1 coded barcode according to AI (Application Identifier) specifications. Checksum calculation and validation for many AI specifications have been implemented. For example, consider code text “(703)123”, which is an incorrect code text (ref: 703 AI, with letters – 324a, with more than 4 symbols). Aspose.BarCode will throw following exception if user tries to generate the barcode with EncodeTypes as GS1Code128. Algorithm to detect QR coded barcode has been improved. Its targets detection logic has been updated. QR coded barcode can now be detected in combination with MaxQuality mode for better accuracy. This month’s release also includes few bug fixes that were reported by Aspose customers in the previous release, such as Recognition process of QR barcode in MaxBarCodes mode and Functionality of ExportToXml method has been improved. ExportToXml method now export dimension properties along with other properties of the newly define barcode into XML file. Below is the list of new and improved features supported in this version.

• Improve GS1 parsing and validation
• Improve targets detection for QR
• BarCodeBuilder allows to generate incorrect GS1 barcodes
• Unable to recognize the barcode using Aspose.BarCode
• Barcode generator accepts incorrect GS1 codetext
• BarCodeBuilder.ExportToXml method is not exporting dimensions of the barcode in the XML file
  

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.

More about Aspose.Report for .NET

• Homepage of C# & VB.NET Barcode Component Aspose.BarCode for .NET
• Download of Aspose.BarCode for .NET
• Online documentation of Aspose.BarCode for .NET

Access Embedded SWF File Data in Presentation & Improved Presentation Rendering using Java

What's New in this Release?
The long awaited version of Aspose.Slides for Java 17.4.0 has been released. Aspose team has included some new features support along with resolution of outstanding issues in this release. Now, suusers can access the embedded SWF file data inside presentation and can even extract that using Aspose.Slides. Please visit documentation article, Extracting Flash objects from Presentation for more details. Now, Developers can also verify if any given presentation has been crated or modified using Aspose.Slides. Aspose team has improved the charting support and issues related to line charts and chart data labels. It has also resolved the issues related to presentation access and saving which earlier resulted in different exceptions like, ArgumentNullException, NullReferenceException and NullPointerException. It has also rectified the corrupt presentations and error message appearing issue for saved presentations as well. This release has improved presentation rendering support in the API and has rectified issues related to text, image, charts, table cells, borders and other shapes rendering inside exported SVG, PDF and slide thumbnails. This release also resolved issues related to slides cloning and have resolved certain incurring issues including presentation layouts getting disturbed, broken text inside paragraphs and fonts styles getting changed in cloned presentations. This list of new, improved and bug fixes in this release are given below

• Support for a checking if presentation has been created or modified using Aspose.Slides  
• Get Position of the DataPoints          
• Getting automatic values for chart elements in a public API
• Extracting flash objects from presentation
• Get position of chart datalabel          
• Different Display setting percentage affect the picture scaling        
• Aspose.Total.Product family license failed to load
• Text broken after saving
• PPT not converted properly to PDF
• Presentation with media files not properly converted to html
• PPTX changed after cloning
• PPT to PDF creates corrupted output when pdfOptions.setSaveMetafilesAsPng(false) is used.
• Exception on loading PPTX
• Diagrams content missing while converting PPTX to PDF

Other most recent bug fixes are also included in this release
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Slides for Java documentation that may guide users briefly how to use Aspose.Slides for performing different tasks like the followings.

• Check if Presentation is Modified or Created
• Get Actual Max value of vertical axis on a chart

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.
More about Aspose.Slides for Java

• Homepage of Aspose.Slides for Java
• Downlaod Aspose.Slides for Java
• Online documentation of Aspose.Slides for Java
• Demos of Aspose.Slides for Java

Apply Checksum Validation on Codabar Barocde & Enhanced GS1DataMatrix Generation using Java

What’s new in this release?

Aspose team is pleased to announce the new version of Aspose.BarCode for Java 17.03.0. The major development in this release is the enhancements incorporated in Aspose.BarCode API to improve the overall performance of the API. Improved recognition speed of Aztec coded barcode, improved processing of DataMatrix and support of CodabloackF coded barcode recognition with AllSupportedTypes property are top of the list. Processing of rotated DataMatrix barcode has also been improved in this release. There are some important enhancement part of this release, such as barcode recognition from a BMP image, Datamatrix barcode generation of type DataMatrixEccType.Ecc200 , reading Code39standard coded barcode, CodablockF coded barcode, ITF14 coded barcode,  Metered licensing mechanism, Process of Aztec barcode recognition, Processing of CodabloackF barcode and Processing of rotated DataMatrix barcode has been greatly improved.  Below is the list of main improved features and bug fixes added in this release.

• Reading problem of DataMatrix barcode
• Improve recognition speed for Aztec
• Improve recognition speed for Aztec by reducing the number of passes
• Include CodablockF and Coupons in Silverlight control
• Incorrect recognition of CodabloackF with AllSupportedTypes
• Reading Barcode from a BMP image is generating exception
• Remove line offset for CodablockF (GraphicsUnit.Pixel)
• The recognition performance of rotated DataMatrix barcodes has been improved
• Too small quiet zone for ITF14 when border type is Frame or FrameOut
• Creating a Datamatrix barcode with DataMatrixEccType.Ecc200 throws a null reference exception
• Barcode reader is unable to recognize the barcode on an image
• Unable to recognize PDF417 barcode from a drivers' license image
• Dynabic.Metered: Aspose.BarCode has to be adjusted to the latest Dynabic.Metered version

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.

More about Aspose.BarCode for Java

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

AutoCAD DWF Files Rendering Support, Enhanced DWG Layers Conversion to PDF & PNG using .NET

What’s new in this release?

Aspose development team is pleased to announce the release of Aspose.CAD for .NET 17.4.0. The major development in this release is support for DWF file format. This is one of major releases where Aspose team has included new features in API. Now, users can work with DWF files and render them to images and PDF files as per requirement. For more about supported feature, please visit documentation articles, Converting DWF to Raster Image Format and DWF to PDF. This release also includes improved rendering support for DWG file format as well in terms of exporting to PDF and images. The support for new entity MLeader has also been included for DWG drawings as well. There are some important enhancements introduced in this release, such as support for DXF and DWG file formats in FileFormat enumeration, Converting DWG layers to PDF and converting DWG layers to PNG image are greatly improved. The main new features added in this release are listed below

• Support DWF Format
• Support MLeader Entity for DWG format
• Converting DWG to PDF format is producing error 
• Add support for DXF and DWG file formats in FileFormat enumeration
• Converting DWG layers to PDF is producing incomplete text in the resultant PDF
• Converting DWG to PNG is producing incomplete image

Overview:Aspose.CAD for .NET

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

More about Aspose.CAD for .NET

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

Set Horizontal & Vertical Resolution While Saving Word Documents to Images inside Cloud Apps

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Words for Cloud 17.4.0. This release contains 1 new feature and a couple of bug fixes. Aspose.Words core library has also been updated to version 17.4. Using Aspose.Words for Cloud 17.4 users can now set the Horizontal and Verticle Resolution while converting a word document to an Image format.  Please visit Specify Horizontal, Vertical Resolutions during Saving Word Document to Image Formats for more information. Other Bug fixes in this release include. This release fixes issues with Words Cloud under a high concurrency environment, Automatic tracking changes does not work when replacing text, Links returned from executeTemplate API call are malformed and Method “get run by index” returns incorrect run. Aspose.Words for Cloud provides a powerful set of API for manipulating, converting and saving Microsoft Word documents stored in the Cloud platform of your choice. Whether you are creating a new Word Document from scratch, converting an existing document to a PDF or modifying a Word document Aspose.Words for Cloud has your document needs covered. The list of new and enhanced features added in this release are given below

• Add feature to set Horizontal and Vertical Resolution of ImageSaveOptions
• Words SaveAs method concurrency issue under heavy load
• "Automatic tracking changes" does not work when replacing text
• Links returned from executeTemplate API call are malformed
• Method "get run by index" returns incorrect run

Start a free trial today – all users need is to sign up with the Aspose for Cloud service. Once signed up, users are ready to try the powerful file processing features offered by Aspose for Cloud.
Overview: Aspose for Cloud
Aspose for Cloud is a cloud-based document generation, conversion and automation platform for developers that offer a unique suite of APIs to work with Word documents, Excel spreadsheets, PowerPoint presentations, PDFs, and email formats and protocols. It supports all features for file processing, document scanning, barcodes creation and recognition, and allows extracting text or images too. Users can also work with SaaSpose APIs using REST SDKs that can be called from .NET, Java, PHP and Ruby etc.
More about Aspose for Cloud

• Learn More about Aspose.Words for Cloud
• Download latest release of Aspose.Words for Cloud
• Online Documentation for Aspose.Words for Cloud

Identify If Image is Transparent or Not & Improved Memory Usage for DNG File Format using .NET

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Imaging for .NET 17.4.0. This is a maintenance release whereby we have rectified several issues and brought enhancements in API. The support for determining transparency in images has also been included in this API.  There are some important enhancements introduced in this release, such as how to determine if the image is transparent or not, Improving memory usage for DNG file format, Support for converting SVG to PDF, Converting SVG to raster image (PNG in this case) file, Improve quality of resized image, TIFF images with JPEG compression should support all possible bits per sample combinations and Implementation of rate control algorithm for Aspose.Imaging Jpeg-2000 codec. Please refer to the release notes of Aspose.Imaging for .NET 17.4 for a full view of improvements along with sample code snippets for newly added features. The main new and improved features added in this release are listed below

•  
• How to determine if the image is transparent or not
• EMF image is not converted
• Stream is unexpectedly closed in multithreaded environment
• FontSettings.addFontsFolder only loads TTF fonts
• Saving of large PNG images leads to black resulting images
• Buffer overflows in PNG for Compact Framework
• Improve memory usage of DNG file format
• Converting SVG to PNG image is not showing proper shapes in PNG file
• Support for converting SVG to PDF
• Converting SVG to raster image (PNG in this case) file is showing blank resultant PNG file
• Improve quality when resized
• TIFF images with JPEG compression should support all possible bits per sample combinations
• Implementation of rate control algorithm for Aspose.Imaging Jpeg-2000 codec

Overview:Aspose.Imaging for .NET

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

More about Aspose.Imaging for .NET

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

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Pdf for Java 17.3.0.  It has specifically focused on PDF file conversion to various supported output formats. The PDF file to PDF/A format conversion and validation capabilities are among the salient features of Aspose.Pdf for Java and many customers are already taking benefit of these functionalities. In this release, the development team has specifically focused over these areas and have resolved many issues related to these features. With this new release, the API is more stable and capable of handling more complex documents and can gracefully handle documents with similar structure. The type of errors fixed for this feature include missing contents in resultant PDF/A file, garbled contents in resultant PDF/A, missing images in resultant file, missing compliance information in resultant file, errors due to color space etc. Aspose.Pdf for Java is an amazing API as it offers the feature to convert PDF files to various MS Office formats. Using this API, developers can transform PDF file to DOC, DOCX, XLS and PPTX format. Recently some customers reported problems related to the conversion of PDF files to DOCX format and in this release, many of these issues have been resolved and the API has become more stable in this area. Some general fixes in this area include resolution of exceptions, additional contents in resultant file and representation of contents in language other than English. However as mentioned earlier, the rendering mechanism has been greatly improved. Dynamic forms are based on an XML specification known as XFA, the “XML Forms Architecture”. The information about the form (as far as PDF is concerned) is very vague – it specifies that fields exist, with properties, and JavaScript events, but does not specify any rendering. The objects of XFA form are drawn at the time loading the document based on specifications. These documents also provides the capabilities to dynamically fill data inside them and save them separately. However when it comes to manipulation, it gets quite difficult and sometimes customers request to convert XFA forms to standard Acro Forms, as the standard form itself contains form fields and they are not generated on run-time. There is also great improvement in XFA forms to Standard Acro form conversion and API now provides more stability in this area. Apart from above mentioned improvements, the PDF to Image conversion, Text extraction, Text replacement, PDF file signing, Tex file to PDF conversion, PDF form filling, PDF file merge and import of Annotations are also improvement areas. Some important improved features included in this release are given below

• PDF to JPG: text missing in output image
• Form filled information changes after merge
• PDF to PDF/A-1B: document is not compliant
• PDF to PDFA1b: compliance failure due to CMYK error
• PDF to DOCX - Exception during conversion
• PCL to PDF: incorrect output is generated
• PDF to PNG conversion results into a blurred image
• Unable to convert XFA form to Standard AcroForm
• Unable to convert XFA form to Standard AcroForm
• Unable to validate PDF/A_1b compliance of document
• Latex to PDF: rendering is incorrect
• Incorrect color information is being retrieved for TextFragment
• PDF to PDF/A - Contents get garbled and file is not PDF/A compliant
• PDF to PDF/A - Contents get truncated in resultant file
• PDF to PDF/A - Page contents are messed up
• PDF to PNG: some images are missing on resultant image
• PDF to PDF/A - Resultant file is not compliant
• PDF to DOCX: Russian text is being added in resultant DOCX
• Regression: 16.10.0 generates invalid PDFA document
• When PDF is saved as DOCX, some additional new lines are added.
• TIFF to PDF: corrupt PDF is being generated
• TextFragmentCollection breaks Iterable interface
• PPdfFileSignature does not retain image given width
• XFA form is not being converted to Standard Acro Form.
• PDF Merge Gives NullPointerException
• Exception thrown when using Pdf Digital signature
• Annotation import throws exception An element with the same key already exists in the dictionary

Overview: Aspose.Pdf for Java

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

More about Aspose.Pdf for Java

• Homepage of Aspose.Pdf for Java
• Download Aspose.Pdf for Java
• Read online documentation of Aspose.Pdf for Java

Permanently Remove Messages from PST File & Enhanced Working with MAPI Properties using Java

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Email for Java 17.4.0. This month’s release provides the capability to permanently delete messages from Outlook PST file. It also supports new MAPI property in addition to the already set of supported properties. Other than these exciting new features, the API also fixes several bugs reported with the last version by Aspose valued customers. This month’s release enhances the functionality of deleting messages from PST file such that deleted messages won’t be recoverable from the file anymore. In situations, where the PST file needs to be handed over to another party after extracting desired messages, this is helpful in the sense that deleted messages are no more recoverable by any forensic tool. There are no public API changes to incorporate this functionality in an applications and upgrading to this latest version will do the needful.  Aspose.Email is rich in features while working with Outlook MSG files. It’s support for reading and setting wide range of MAPI properties for Outlook MSG file makes it favorite for manipulating such type of messages. This months’ release further enhances the capability of working with MAPI properties by providing support for a new property i.e. PT_FLOAT. This further enriches the set of properties supported by the API. Following code illustrates how to set this property for a MSG file using Aspose.Email API. This month’s release also includes several bug fixes that were reported by Aspose's users with the previous release.  The main improved features & bug fixes added in this release are listed below

• Delete messages from PST permanently
• Option to add PT_FLOAT property  Enhancement
• TNEF issue resulting in NDR on Exchange Server   
• Performance issue while adding MapiMessage to PST
• EML to MHTML converts German characters to Garbage values
• Attachment data is set as message body instead
• Accepted appointment cannot be saved in PST
• Provide Logging facility on session based for all communication clients
• PNG images corrupted after using them as mail attachments
• Saving EML to MSG causes inline images appear as attacments
• Attachment NamedProperties lost while fetching message from PST
• MailMerge not working for TO, CC and BCC
• MapiProperties lost after adding message to PST
• Information not read from VCF file
• Body could not be read from MSG file
• EML to MSG convertion Issue with embedded Signed and Encrypted message
• IGmailClient.UpdateContact raises Aspose.Email.GoogleClientException
• IGmailClient.ListAppointments raises Aspose.Email.GoogleClientException
• IGmailClient.GetSettings raises Aspose.Email.GoogleClientException
• Exception is raised while converting EMLs to tiff
• Saving MSGs/Calendar Items from PST raises exception
• MailPrinter raises exception converting email to TIFF

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

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

PDF to PDF/A Conversion, Enhanced Text Search & Text Extraction in PDF Files inside .NET Apps

What's New in this Release?

Aspose team is pleased to announce the release of Aspose.Pdf for .NET 17.4.0. It has specifically focused towards stability of existing features for PDF files creation as well as manipulation. Aspose.Pdf for .NET is widely being used by many customers and trusted name due to its robustness and reliability on various platforms. Therefore apart from standard desktop versions of Windows, it is equally supported on Server editions of Windows and users can use it in Desktop and Web Enterprise Applications. Keeping same aspects of stability and reliability in mind, with every new release, Aspose team are introducing some exciting new features as well as strive to bring more stability to existing features of API. Therefore in this new release, Aspose team has made improvements in PDF to PDF/A conversion feature to cater more customers scenarios and to handle documents with different structure and complexity. This API is also amazing in Text manipulation, whether its Text Addition, Text extraction, Text Search or Text replacement. However in this release, Aspose team has specifically improved the Text extraction feature and many of the customers reported issues related to this feature have been fixed in this release version. Furthermore, the PDF file conversion to other supported file formats is also improved. Ever since the release of the first MergedAPI version of Aspose.Pdf for .NET 6.0 in July-2011, it has included the Classes and Enumerations from legacy Aspose.Pdf for .NET under Aspose.Pdf.Generator namespace, the Classes and Enumerations of legacy Aspose.Pdf.Kit for .NET under Aspose.Pdf.Facades namespace and a new Document Object Model for PDF files creation as well as manipulation under Aspose.Pdf namespace. The legacy Aspose.Pdf.Generator only provided the capabilities to create PDF documents from scratch and legacy Aspose.Pdf.Kit for .NET provided the functionality to manipulate existing PDF files. But the new DOM approach of Aspose.Pdf namespace facilitates the creation of PDF files from scratch; as well as manipulation of existing PDF files. So in order to minimize / eliminate the confusion of customers to stumbled upon between legacy Aspose.Pdf.Generator and new Aspose.Pdf namespace, starting next release of Aspose.Pdf for .NET 17.5, Aspose team is going to discontinue Aspose.Pdf.Generator namespace from API. Nevertheless, the new DOM approach contains all the features offered by legacy Aspose.Pdf.Generator.  This change may impact some customers who haven’t yet migrated their code from legacy Aspose.Pdf.Generator to new DOM approach, but Aspose team is always delighted to help Aspose customers and would love to facilitate them regarding their migration towards new DOM. Also please note that with this change, the size of product binaries will also be reduced.  The list of important new and improved features are given below

• The flattened file from XFA form cannot be opened in Chrome or Firefox.
• Create separate local links for duplicate text
• NullReferenceException is thrown when trying to get artifact text
• ArgumentException is thrown when trying to get artifact text
• Exception when trying to load PDF document
• Exception when trying to get signature names
• Exception thrown when trying to get the names of the fields in a form
• PDF to PDFA conversion performance issue
• Failed to validate PDF_X_3 and PDF_X_1A
• Stamp looks incorrect when size and rotate angle are set
• Convert Web Page to PDF - bad layout
• When PDF is converted to PDF_A_1B, the text looks different
• For Helvetica and Courier fonts, page number in the TOC entry is missing
• When PDF is converted to DOCX, the text is missing.(converted to image)
• Images not rendered to next page
• PDF to PDFA1b conversion results in-compliant PDFA document

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.

More about Aspose.Pdf for .NET

• Homepage of Aspose.Pdf for .NET C#
• Download Aspose.Pdf for .NET
• Read online documentation of Aspose.Pdf for .NET

Use Enhanced GS1 Barcode Generation & Recognition in SQL Server Reporting Services

What’s new in this release?

We are happy to announce the new release of Aspose.BarCode for Reporting Services 17.4.0. The major development in this release is the enhanced functionality of GS1 coded barcode. More often it is seem that GS1 code text contains complex combination of digits and letters. With Aspose.BarCode for SSRS 17.4, parsing and validation of those complex combinations is possible. Aspose.BarCode for SSRS allows developers to generate GS1 coded barcode according to AI (Application Identifier) specifications. New validators have been incorporated that can validate text code having only digits and complex AIs (combination of digits & letters). API will throw an exception in case it fails to validate. According to AI specification (ref: 703 AI, with letters – 324a, with more than 4 symbols) code text “(703)123” is incorrect. Aspose.BarCode will throw following exception if user tries to generate the barcode with EncodeTypes as GS1Code128. The following exception message will be displayed for such an incorrect barcode. Functionality of ExportToXml method has been improved. ExportToXml method now export dimension properties along with other properties of the newly define barcode into XML file. Below is the list of new and improved features added in this new release.

• Improve GS1 parsing and validation
• BarCodeBuilder allows to generate incorrect GS1 barcodes
• Barcode generator accepts incorrect GS1 codetext
• BarCodeBuilder.ExportToXml method is not exporting dimensions of the barcode in the XML file
• Reorganize properties in Properties Window

Overview: Aspose.Report for .NET

Aspose.BarCode for Reporting Services is a .NET solution for the rendering of barcode images in SQL Server 2000, 2005 & 2008 Reporting Services. It supports 29+ linear (1D) and 2D barcode symbologies including MacroPdf417, Australia Post, OneCode, Code128, Code39, PDF417, UPCA, Codabar, MSI and QR etc. Also render barcode images on reports in BMP, JPG, PNG and GIF formats. Other features include EAN-128 application identifiers, DPI resolution settings, barcode size and location adjustments.

More about Aspose.Report for .NET

• Homepage of Aspose.BarCode for Reporting Services
• Download Aspose.BarCode for Reporting Services
• Online documentation of Aspose.BarCode for Reporting Services

Protect Excel VBA Project & Apply DBNum Custom Pattern Formatting inside .NET Apps

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Cells for .NET 17.4.0. Protect VBA Project of Excel Workbook and Lock it for Viewing, Specify Sort Warning While Sorting Data and Apply DBNum Custom Pattern Formatting in .NET.  The new release includes some valuable features and other enhancements with critical bug fixes. We have added certain features regarding VBA project’s protection for the users. There is also an enhancement for data sorting and custom pattern formatting. Aspose.Cells now supports the feature of protecting the VBA (Visual Basic for Applications) Project of Excel Workbook and locking it for viewing. Besides, users can also find if an existing VBA project is already protected and locked for viewing. The code snippet demonstrates how to protect an Excel Workbook VBA Project dynamically using Aspose.Cells and lock it for viewing. Aspose.Cells already supports Data Sorting, however earlier users could not sort a textual data as numerical data. For this purpose, Aspose.Cells implemented the DataSorter.SortAsNumber property. Whenever users sort textual data that looks like a number, MS-Excel shows this warning. DataSorter.SortAsNumber property implements this MS-Excel warning. It supports the DBNum custom pattern formatting. For example, if a cell value is 123 and users specify its custom formatting as [DBNum2][$-804]General then it will be displayed like 壹佰贰拾叁. Developers can specify custom formatting of a cell using Cell.GetStyle() method and Style.Custom attribute. Aspose.Cells for .NET 17.4.0 has enhanced its core for more stability as well as fixed many critical bugs. Moreover, there are numerous minor enhancements in order to improve the overall usage of the API.A few of the worth mentioning enhancements includes, such as Set Column Header ToolTip, sparklines disappear after re-saving and rendering to PDF, Formatting error inside shapes texts when Excel is converted to PDF, VbaProject.Sign causes an exception and Re-adding a picture to the same XLS throws a Null Reference error. Furthermore, in this release, we have fixed several other issues, such as issues around reading/writing MS Excel file formats, manipulating Pivot Tables, applying formatting to cells, manipulating Ole Objects and shapes, rendering and manipulating charts, rendering HTML to Excel and vice versa, rendering images from Excel worksheets, rendering images files from charts and exporting Excel workbooks to PDF format have been resolved. The formula calculation engine is enhanced too in the new release. This release includes several enhanced features and bug fixes as listed below

• Support "Lock project for viewing" Protection option in VbaProject Properties
• Password protect the VBA project
• Implement Sort Warning feature - Sort anything that looks like a number
• Function SetColumnHeaderToolTip(int colIndex, string toolTip) missing in newer APIs set - Aspose.Cells.GridWeb
• Change filter list to multiple checkbox selection list for GridWeb
• PivotTable Grouping and Pivot Report Filter selection disappear when loading in GridWeb
• Sparklines disappear after rendering to PDF
• Sparklines disappear after re-saving the file
• OutOfMemoryException while saving CSV to PDF
• Format tag in the SpreadsheetML content keeps hanging on loading
• Remove some calls to string.ToUpper() method (if possible) in the source code
• Some shapes are separated/distorted and dim in the rendered PDF file
• Removing worksheet causes to save a corrupt XLSM
• Saving worksheet as HTML with overflowed text in cells
• Some text is overlapping or invisible and vertical alignment is not right in Excel to HTML rendering
• When HTML is saved as XLSX, text layout is different
• When HTML is saved as XLSX, text format is changed
• When HTML is saved as XLSX, part of content is missing
• When loading HTML and save it as XLSX, paragraphs are missing and changed
• Issue with Pivot Filters Text
• Number format does not work correctly in the Pivot Table
• Some text is overlapping with other cells and vertical alignment is not right
• Problem while importing dates around 1900 from CSV file
• Font is bolder in the output PDF file when setting the PDF optimization type to "MinimumSize"
• Font changed in the output image/PDF
• Slight Vertical Alignment Difference between Excel and Aspose.Cells Pdfs
• Font is different and percentage sign is missing in the output PDF file
• Charts have "Axis Title"
• 3D Column charts are not rendered fine in the output PDF file
• Category axis labels are not showing of chart in the output PDF
• Deleting worksheet in XLSM leaves behind a remnant sheet in vba project
• When specific file is saved, the output is corrupted
• Excel documents gets corrupted after Save
• Formula 'DAYS' in Excel tables gets replaced with a NamedRange
• Setting LightAngle value corrupts Excel file
• Inserting rows breaking formulas linking to external workbook
• The table style was changed (The table lines are missing) after re-save in a specific XLS
• Aspose.Cells sorts fine but formulas are converted to values
• Cells range deletion with shift up option does not style on cells
• Workbook gets corrupt after open and save
• Datatable is not being shifted down properly in an XLSX
• Cannot read worksheets of a password protected XLSX file
• Cells.DeleteRange() is not working properly
• Cannot update OleObject.ObjectSourceFullName property
• Cells range deletion with shift up option does not decrease hyperlink count
• Incorrect hyperlinks count when duplicating the single row data in an XLS
• Moving the array in Input2.xlsx results in an unopenable file that crashes Excel on startup
• Reference in the array does not update when the referenced cells are moved in Input.xlsx
• Replace background for shape doesn't work
• The "Locked" attribute of ActiveX control (ComboBox) is not changed while protecting worksheet
• Horizontal scrollbar lost (in Google chrome) in GridWeb
• Big lags (in scrolling, selecting a cell, etc.) when using long list of merged cells
• The alignment of the cells lost when inserting/pasting values into the cells
• Percentage value changes to NaN

Other most recent bug fixes are also included in this release

Overview: Aspose.Cells for .NET

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

More about Aspose.Cells for .NET

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

Import Bitmap Image as New Visio Shape in Visio Drawing & Improved Routing Mechanism using Java

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Diagram for Java 17.4.0. The new version of the API has improved the feature of importing a Bitmap image as a shape in Visio drawing. Developers can also find improvements in routing and building the structure of connectors with a high accuracy rate. All the regular bug fixes are also included. We recommend our clients use the powerful Aspose for Java APIs directly in their Maven Projects with simple configurations.  Aspose.Diagram for Java API has already added support of importing graphics in the Visio drawing. Developers may then export the Visio drawing to any supported format. The new API version 17.4 has enhanced the import of Bitmap image internally without any API change. Developers can now import a Bitmap image even in their complex drawings. Aspose.Diagram for Java API has also made improvements in routing mechanism to address the connections of Visio shapes as well as auto routing of connectors. This helps developers to track the flow of nodes because the clarity is important in drawings. It has also included some important enhancements, such as The connecting lines are not connected while creating a VDX, Missing shapes on converting a VDX to VSDM, The text items are rendered vertically on converting a VDX to VSDM, Connectors are not in the right positions with changing the page layout in VSDX. Aspose team auto port Aspose.Diagram for .NET to Java to give developers perfectly the same features on both platforms, so this version also incorporates the bug fixes and enhancements from its equivalent .NET version. This release includes several enhanced features and bug fixes as listed below

• Add support to import a bitmap image as a shape
• The connecting lines are not connected while creating a VDX
• Missing shapes on converting a VDX to VSDM
• The text items are rendered vertically on converting a VDX to VSDM
• Connectors are not in the right positions with changing the page layout in VSDX

Overview: Aspose.Diagram for Java 

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

More about Aspose.Diagram for Java

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

Rate Control Algorithm Implementation for JPEG2000 & Enhanced SVG to PDF Conversion using Java

What’s new in this release?

Aspose development team is pleased to announce the new release Aspose.Imaging for Java 17.4.0.  The major development in this release is the implementation of rate control algorithm for JPEG2000. The support for improved quality when image get resized has also been included in this release. Some important enhancements are also introduced in this release, such as implementation of rate control algorithm for Aspose.Imaging Jpeg-2000 codec, TIFF images with JPEG compression should support all possible bits per sample combinations, Support for converting SVG to PDF, Converting SVG to raster image (PNG in this case) file is showing blank resultant PNG file, Improve quality of resized image, saving of large PNG images leads to black resulting images and FontSettings.addFontsFolder only loads TTF fonts. The main new and improved features added in this release are listed below

• Implementation of rate control algorithm for Aspose.Imaging Jpeg-2000 codec
• TIFF images with JPEG compression should support all possible bits per sample combinations
• Improve quality when resized
• Converting SVG to raster image (PNG in this case) file is showing blank resultant PNG file
• Support for converting SVG to PDF
• Converting SVG to PNG image is not showing proper shapes in PNG file
• Improve memory usage of DNG file format
• Saving of large PNG images leads to black resulting images
• Stream is unexpectedly closed in multithreaded environment
• Emf image is not converted properly
• FontSettings.addFontsFolder only loads TTF fonts

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.

More about Aspose.Imaging for Java

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

Aspose.Newsletter May 2017: Professional Word Documents Processing in Android Apps & Other News

Aspose Newsletter for May 2017 has now been published that highlights all the newly supported features offered in the recent releases.  It also includes information about It also includes information adding Professional Word Documents Processing capabilities in Android Applications, Aspose Android APIs are Renamed to “Android via Java” and “Android via Xamarin”, Exporting Excel File to Any Supported Format, Apply Checksum Validation on Codabar Coded Barcode in .NET Applications, AutoFit Cells in Worksheet and Set Excel Page Breaks in Cloud Apps, How to Render Microsoft Outlook VCard Contacts to MHTML and many more.
Add Professional Word Documents Processing capabilities in an Android Applications
Read, Create, Edit and Convert Word Document Formats with Aspose.Words Android APIs. Aspose.Words products family is growing! We are pleased to officially launch Aspose.Words for Android via Java – enabling Android developers to perform pro level word document manipulation tasks directly within Android Apps. Whether it is document formatting, reporting, mail merge, rendering or conversion to some other file formats – Aspose.Words processing engine is super-efficient to perform with high-fidelity. Download Free Trial
Aspose Android APIs are Renamed to “Android via Java” and “Android via Xamarin”
Aspose Android APIs are ported from their Java APIs as they are subset components that include all the important and useful features present in their native Java APIs. Aspose.Words, Aspose.Cells and Aspose.Email for Android are following this new product naming structure now (example: If users are building native Android apps using Android Studio, the right product is Aspose.Words for Android via Java and if users are using Xamarin platform, users can use Aspose.Words for Android via Xamarin, to build mobile apps).
Apply Checksum Validation on Codabar Coded Barcode in .NET Applications
Aspose.BarCode for .NET API now exposes the CodabarChecksumMode enumeration to specify the checksum mode. EnableChecksum property of the BarCodeBuilder class is needed to be set to TRUE before setting the checksum mode. Read detailed examples here
AutoFit Cells in Worksheet and Set Excel Page Breaks in Cloud Apps
Process Excel files using Aspose.Cells for Cloud – platform independent REST APIs. Developers can import an Excel file, autofit rows and columns of any worksheet and then save to any supported file format. Continue reading here
How to: Export PowerPoint Presentation to HTML in .NET and Java?
Aspose.Slides for .NET and Java now support converting a PowerPoint presentation to HTML with embedded audio and video data. Access fully functional .NET and Java code snippets here
How to: Render Microsoft Outlook VCard Contacts to MHTML?
Aspose.Email provides support for email threading and conversion of Outlook VCard contact information to MHTML within .NET and Java applications. This can be achieved with MhtFormatOptions.RenderVCardInfo enumerator while saving the message to MHTML. Access .NET and Java code snippets here for quick reference
How to: Permanently Delete Email Messages from PST File in .NET and Java Apps?
Aspose.Email for .NET and Java allows deleting emails from PST files on permanent basis that no other email recovery or forensic tools can retrieve ever. This feature comes handy in some legal matters where private and privileged messages are supposed to be removed prior to access. Check out .NET and Java source code examples for further illustration:
How to: Print Microsoft OneNote Documents From .NET Applications?
Aspose.Note for .NET 17.3 allows programmers to print OneNote documents from within their .NET applications. The Document.Print method allows sending the loaded document to default printer but users can also specify printer settings for printing the document using the PrintOptions class. View the source code here
Updates about new Product Releases

1. Aspose.Total for .NET - a compilation of our latest .NET products.
2. Aspose.Total for Java – a compilation of our latest Java products.
3. Aspose.Total for Android – all the latest versions of our Android APIs.
4. Aspose.Total for SharePoint – a compilation of our latest SharePoint products.
5. Aspose.Total for Reporting Services – a compilation of our latest Reporting Services products
6. Aspose.Total for JasperReports – The latest versions of our JasperReports products.
7. Aspose.Pdf for .NET 17.4.0 – Improved PDF to PDF/A conversion with added text manipulation features.
8. Aspose.Words for .NET 17.4 – Custom formatting of Field Results along with 12 new feature improvements.
9. Aspose.Imaging for Java 17.4 – Improved support of image resizing and rate control algorithm implementation.
10. Aspose.Words for Android via Xamarin 17.4 – Improved support of linear gradients rendering as well as reading of GIF files.
11. Aspose.Tasks for .NET 17.3 – Improved formula value calculations within Microsoft Project files.
12. Aspose.Slides for Reporting Services 17.3 – Support for working in SharePoint 2016 integration mode.
13. Aspose.OCR for Java 17.03 – Improved processing of skewed image to deskewed.
14. Aspose.Slides for Reporting Services 17.3 – Support for working in SharePoint 2016 integration mode.

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

• May 10-12: Microsoft Build 2017 – Seattle – WA, USA
• May 15-18: Visual Studio Live! Austin – Austin – TX, USA

To sponsor a user group? Get in contact at user.groups@aspose.com
Collect a copy of Aspose Newsletter, August 2016 edition

• Collect the English version of this newsletter

Build any Type of 32-Bit & 64-Bit C++ Applications using Aspose.Cells for C++ APIs

What’s new in this release?

Aspose team is pleased to announce the new release of Aspose.Cells for C++ 17.4.0. This release supports both 32-bit and 64-bit versions of Windows for desktop (e.g. XP, Vista, 7, 8, and 10) and server operating systems (e.g. 2003, 2008, 2012), etc. Previously, it only supported 32-bit OS. Developers may use Aspose.Cells for C++ APIs to build any type of 32-bit and 64-bit C++ application. Please take a look over the release notes to get an idea about what is new and what has been enhanced with this revision of Aspose.Cells for C++ API. If users are planning to upgrade the API from an old version, Aspose team recommend to check the Public API Changes section to know what has been changed. Aspose.Cells is a native C++ library that enables developers to create, read, edit & convert Excel spreadsheets programmatically without relying on Office automation or Microsoft Excel application. Aspose APIs are totally independent and are not affiliated with, nor authorized, sponsored, or otherwise approved by Microsoft Corporation. Aspose.Cells for C++ does never need Microsoft Office or Microsoft Excel to be installed on the machine to work with Excel document formats. This release includes several enhanced features and bug fixes as listed below

• Support 64-bit versions of Windows
• Improved performance of writing XLSX file
• Calculate formulas in Excel spreadsheets
• Improved performance in reading XLSX files

Overview: Aspose.Cells for C++

Aspose.Cells is a C++ 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.

More about Aspose.Cells for C++

• Homepage of Aspose.Cells for C++
• Download Aspose.Cells for C++
• Online documentation of Aspose.Cells for C++

3D Models Conversion to Google Draco, Improved Camera Movement & Magnification Support using .NET

What’s new in this release?

Aspose team is pleased to announce the release of Aspose.3D for .NET 17.04.0. The new version of the API adds support of converting 3D models to the Google Draco (.drc) format. Developers can import any supported 3D file, and then export in DRC format. All 3D import formats are listed on this page: Import an Existing 3D File. The Draco saving options of the API allow to specify the compression level. This help topic shows how to specify Draco saving options: Use of the Google Draco (.drc) Save Options. Developers can also encode a Mesh in the Google Draco file. All other regular fixes and improvements are also included. 3D meshes are widely used in computer graphics applications for approximating 3D models. When representing complex shapes in raw data format, meshes consume a large amount of space. Using Aspose.3D for .NET API, developers can retrieve a mesh of any 3D shape, and then encode it in the Google Draco (.drc) file. Using Aspose.3D for .NET API, developers can already place a camera in 3D scene to define a view as narrated in this help topic: Take a Picture of 3D Model from the Camera. Developers can now find improvements in the Camera and Light movements with orthographic projection mode. This release includes plenty of new features as listed below

• Add support of exporting 3D models to Google Draco (.drc) format.
• Improve camera movement in orthographic projection mode.
• Add support to zoom out Camera     

Overview: Aspose.3D for .NET

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

More about Aspose.OCR for .NET

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