Apose tools

[aspose_seo]

What?s new in this release?

The latest version of Aspose.Pdf for .NET (11.4.0) has been released. It offers some new features as well as enhancements to previously supported functionalities. The capability to add hidden text is one of the major New Features introduced in this release. Furthermore, we also have introduced the capability to use PDF file objects after calling ProcessPragraphs() method which is not possible with earlier release versions. In order to add hidden text, set TextState.Invisible property to ?true? for the added text. TextFragmentAbsorber finds all text that match pattern (if specified). Please note that hidden text in the document will be invisible for end user while viewing the document with PDF reading software (e.g. Acrobat Reader). But it can be found using text search. There are several ways to make text invisible for end user in PDF and we have implemented one of those techniques. However the text added through our approach can be found using TextFragmentAbsorber and we can not guarantee that any hidden text added by third party applications can be found using same approach but in case you encounter any issue, please share the resource file and we can further investigate the scenario. The ProcessPragraphs() method was introduced to calculate objects placed inside PDF file and in case we need to have page count information during PDF file generation, this method can be used as it manipulates file objects and returns the desired information. In earlier release versions, once this method was called, the file objects could not be accessed any further. So if you need to add any new object to existing page instance, it was not possible and you had to have a new Page instance where objects can be placed. Nevertheless, starting this new release, you can utilize same Page objects even after calling the ProcessPragraphs() method. As well as the enhancements and features discussed above, there have been specific improvements regarding PDF to PDF/A, Multi-Column PDF, FootNote rendering, generation of large table objects inside PDF, XFA Form to Standard Acro Form conversion, PDF to Image, PDF to HTML, HTML to PDF conversion, Text replacement and rendering PDF files to XPS format conversion. The list of important new and improved features are given below

- Add and search hidden text in PDF document for post processing
- Using same Page object after ProcessPragraphs() call
- PDF to PDFA conversion throws System.NullReferenceException
ArgumentOutOfRangeException during PDF creation
- Issue checking signature information in PDF file
- Exception when trying to convert PDF to Image
- PDF to PDFA3a: appearance for annotations changed to blue rectangles
- Loading corrupt file with Aspose.Pdf casuses infinite loop
- XFA form to standard PDF form conversion throws internal exception
- PDF -> PDF/A conversion/validation fails with NullReferenceException
- Formatting of header row (repeat row) in table not maintaining formatting
- Right Alignment of Text is not working
- Rotate method is not working for FreeTextAnnotation
- PDF/A - PDF with transparency produces incorrect results
- Unable to embed font in existing PDF file
- VerticalInSamePage property of TableBroken enum issue in nested table
- Footnote larger than a single page drops both page text and footnote from resultant PDF page
- Page number is being truncated from second level of Heading in TOC
- HTML to PDF: Radio buttons are rendering incorreclty
- API throws CrossTableNotFound Exception
- PDF to JPEG: resultant images are distorted
- HTML to PDF: CSS Transform property is not supportd
- PDF (generated by Aspose.Slides) to PDFA3B
- PDF (generated by Aspose.Slides) to PDFA3A
- PDF (generated by Aspose.Cells) to PDFA3A
- PDF (with table) to Image conversion adds white border in resultant image
- API throws NullReferenceException on load a PDF document
- Saving/manipulating PDF document results in corrupt PDF
- Footnote issue in multi-column PDF
- Page Text and Footnote overlap
- PCL to PDF - PCL Line Termination is ignored
- PCL to PDF - Special graphics characters are not being honored
- Unable to save tables with large data in cells
- Add and search hidden text in PDF document for post processing

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#

 

[aspose_seo]

Create Custom Subtotal Labels in Excel Spreadsheet & Access Hyperlink from a GridWeb

What is new in this release?

We are pleased to announce the new release of Aspose.Cells for .NET 16.11.0 . The new release includes some features and other important enhancements with some critical bug fixes. This release has added the support for the creation of custom subtotal labels allowing the application developers to customize the labels according to the region or personal preferences. In order to provide this feature, the latest version of the Aspose.Cells for .NET has exposed the GlobalizationSettings class offering the following 2 methods which can be overridden in a custom class to get desired labels for the Subtotals. The GlobalizationSettings class also offers the GetOtherName method which is useful to give the ?Other? label of Pie charts a custom value. The snippet on blog announcement page defines a custom class and overrides the GetOtherName method to get a custom label based on the system?s regional (culture) settings. It has exposed the CellsFactory class which currently has one method, that is; CreateStyle. The CellsFactory.CreateStyle method can be used to create an instance of Style class without adding it to the pool of workbook styles. It has exposed GetHyperlink method to the GridHyperlinkCollection class that allows to get the instance of GridHyperlink by either passing an instance GridCell or a pair of integers corresponding to the row column indices. Some important enhancements are also part of this release, such as support for MINIFS & MAXIFS functions, ability to manipulate Workbook?s Absolute Path, ability to implement Subtotal or Grand Total labels in other languages, aspose.Cells for .NET formula calculation engine is enhanced, handled and fixed a few exceptions, such as, Stack overflow, NullPointerException, IndexOutOfRangeException and many more. Furthermore, in this release, we have fixed several other issues. For example, issues around reading/writing MS Excel Excel file formats, manipulating and rendering shapes, manipulating PivotTables, copying ranges in the worksheet, rendering to HTML file format, rendering images from Excel worksheets, rendering images files from charts and exporting Excel workbooks to PDF format have been resolved. This release includes several enhanced features and bug fixes as listed below

- Support MINIF and MAXIF functions
- Web links on spreadsheet are opened on the same page where GridWeb is loaded
- UpdateLinkedDataSource() doesn't work when Workbook is loaded from stream
- Deprecated .size() function used in acwmain.js
- Mimic MS Excel behavior when "Enter" key is pressed
- Set focus on the formula back when inserting a formula with wrong parameters (invalid formula)
- Performance issue with GetPivotData function
- Issue with SheetRender.PageCount that takes a long time to calculate worksheet pages
- Range.Copy() method freezes for big Excel ranges
- Spreadsheet becomes corrupted when Workbook names is appended to the Named Range
- RTL direction is changed to LTR while converting HTML to Excel
- PivotTable is losing filters after RefreshData call
- Pivot Table fails to refresh after changing data source to a Named Range
- Calling PivotTable.CalculateData() causes a crash when there is 1 data column
- Excel file is corrupt after opening and resaving it
CSS style ignored for column widths, row heights and word wrap, etc. (HTML to Excel)
- Issue with font-weight and text-align in TD and TH cells
- PivotTable contents are not showing correctly in the output PDF
- Culture settings for Workbook does not take effect for Chart DataLabels using Chart.ToImage
- SUMPRODUCT function with external ranges results in '#REF!' error
- Long values in cell renders as '#' string while converting worksheet to image
- Issue with the size of the converted file (Excel to PDF Conversion)
- Considerable increase in the output PDF file size from a relatively smaller Excel file
- Label is missing when a chart is converted into image
- Trendline in the chart is not rendering fine in the output PDF
- SheetRender.ToImage: Chart overlaps the row below it
- Formula gets _xlfn prefix after the calculation of workbook
- Resave operation corrupts the spreadsheet when worksheet name is " or "
- Corrupted output file generated by Aspose.Cells APIs
- The shapes are not in the same order (as per the original shapes' z order position)
- Removing image from header/footer corrupts the document
- Changing background image of a shape corrupts output XLS file
- Line spacing from TextBox is lost with simple re-save
- ThreeDFormat.TopBevelWidth and TopBevelHeight are not getting applied
- Open and Save document creates corrupted file
- Issue with updating External Link's data source and AbsPath
- Font of Chart Data labels and Legend is changed on opening and re-saving source Excel file
- Unable to update address of a GridHyperlink
- Set alternative text for hyperlink if image URL is not correct
- Accessing hyperlink via cell reference is not possible with GridHyperlinkCollection class
- Obsoleted APIs are not identified in Visual Studio
- Width of Auto-Filter's Dropdown is too small to make a selection
- Trendline in the chart is not rendering fine - Aspose.Cells.GridDesktop
- Auto filters are applied to all the columns instead of specific range/columns only
- RowFilteredEvent of GridDesktop never occurs
- Hidden rows due to filter remain hidden after removing the filter
- Certain formatting elements in the template XLSM file are not imported correctly
- GridDesktop.Button click event never fires on 200% zoom
- Aspose.Cells.GridDesktop: Paste is Always inactive in context menu
- GridWeb control, column disappear if drag to left

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

Contact Information
Aspose Pty Ltd,
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Barcode Recognition from BMP Image & Enhanced Processing of Aztec, DataMatrix Barcode

What is new in this release?

The latest version of Aspose.BarCode for .NET 16.12.0 has been released. 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 mechanism of CodabloackF coded barcode recognition with AllSupportedTypes property are top of the list. Processing of rotated DataMatrix barcode has been improved. CodablockF and Coupons coded barcode have been included in Silverlight control. There are some other important improvements included in 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, Aztec barcode recognition and Processing of rotated DataMatrix barcode has been greatly improved. Below is the list of new and improved features supported in this version.

- Barcodes generated from VS2010 and VS2012 are different
- 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
- Not able to recognize code39standard barcode .NET
- 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

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

Overview: Aspose.BarCode for .NET

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

More about Aspose.BarCode for .NET

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

Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
http://www.aspose.com/
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Modify Gradient Fill Data of Visio Shape & Enhanced Visio Diagram Export using .NET

What is new in this release?

We are pleased to announce the new release of Aspose.Diagram for .NET 16.12.0 . The new version of the API allows developers to modify the gradient fill of a shape in the Visio drawing. The gradient fill improves the appearance of shapes. Developers can also find an improvement in exporting Visio drawings with an embedded Excel worksheet to PDFs. The recent version also covers a number of regular bug fixes and enhancements. Visio shape gradients provide a fast way to give shapes a professional look, especially for flowcharts and other diagrams that will be seen by a wide audience. Using Aspose.Diagram API, developers can retrieve and modify the gradient fill data as per their needs. Developers can also get the gradient stops from each gradient fill to set the position, color and transparency. Aspose.Diagram API has support of manipulating the embedded OLE objects. In few reported use cases, clients were converting the source Visio diagrams to PDFs and facing the problem of missing embedded Excel worksheet. We have enhanced the export of Visio diagrams with embedded worksheet. It is now better than previous. This version also addresses the issues of incomplete rendering of the shapes, extra whitespace around the actual drawing, the invisibility of group shapes and the general formatting problems of the diagram. These enhancements and bug fixes improve performance and accuracy of Aspose.Diagram API. Here is the list of important enhancements and bugs fixes in the new version.

- Add support to modify the individual gradient stop.
- The gradient color of the shape is not being preserved on saving in VSDX.
- The gradient color of circle shape is not shown on saving in VSDX.
- Improvement to set the gradient stop properties.
- Incomplete rendering of the circle shape on saving in VDX. - 1
- Incomplete rendering of the circle shape on saving in VDX. - II
- VSD to PDF export - the extra white space is generated on the left side of the drawing.
- VSD to HTML export - the extra white space is generated on the left side of the drawing.
- VSD to SVG export - the background color of container turns into black.
- Can't group shapes second time in a Visio Drawing page.
- The group shape becomes invisible on adding circular shapes in a VSDM.
- Page.AddShape method shows an invalid error on adding a dynamic connector.
- Missing an embedded excel in converting a VSD to PDF. - 1
- Missing an embedded excel in converting a VSD to PDF. -II
- The text items in the bullets are not aligned well on converting a VSD to PDF.

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
- Download Aspose.Diagram for .NET
- Online documentation of Aspose.Diagram for .NET

Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

PDF/A_2U Standard Support, PDF Size Optimization & Rendering XML Stream to PDF

What?s new in this release?

The latest version of Aspose.Pdf for .NET (16.12.0) has been released. A new feature, the support of PDF/A_2U standard along with number of enhancements and improvements are included in this release. Some of the enhancements are improved PDF Optimization and support of XML stream conversion to PDF. It also contains number of fixes of bugs reported in previous versions by Aspose valued customers, that makes it more stable release as compared to previous releases. Some of them are PDF to PPTX conversion issues, PDF to PDFA standard conversion issues along with many other bug fixes. Aspose team has introduced new PDFA standard, PDF/A_2U in this release. It has included a new value PDF_A_2U in PdfFormt enum. This release has also improved the PDF optimization feature with introduction of some new properties in OptimizationOption class. Mainly resizing of the embedded images reduces the PDF file size, ResizeImages and MaxResolution properties for the purpose along with RemovePrivateInfo. Some of customers have requirement to render XML stream to PDF instead file. So Aspose team has introduced a new constructor of BindXml() that support Stream parameter. Recently, Aspose team has introduced a new XML schema of Aspose.Pdf(new generator). XSD includes in MSI installer. It has introduced HTML text support in new XML schema. The list of important new and improved features are given below

- Support PDF/A_2U format New
- PDF optimization size issue
- File Optimization for web size difference between Adobe and Aspose.Pdf
- PDFA Validation error list
- XML to PDF: BindXml constructors with stream
- XML to PDF: Hyperlink text rendering issue
- Exception when setting XmpPdfAExtensionValueType to PDF file
- OutOfMemory exception when using OptimizeResources(..) method
- PDF to PDFA conversion rotates images, but working fine in 11.2.0
- PDF to PDF/A - Images get distorted
- Text Replacement regression issue in 16.10.0
- When PDF is converted to HTML, the resulting HTML file has long scrollbars in Microsoft Edge
- When PDF document is converted to XPS, the second page shows "This page cannot be displayed" message
- Failed to load Tex file from stream
- When PDF is saved as DOCX, System hangs and CPU goes high
- PDF to PDF/A - resultant file size gets 17 times of the original PDF size
- PDF to TIFF - Blank images are not being skipped
- PDF to PDF/A - Resultant file is large size
- PDF to PDF/A - Resultant file contents get corrupted
- PDF to PDF/A - Formatting issues in resultant file
- PDF to HTML: heading text characters render incorrectly
- Non-Searchable PDF is converted to incorrect Searchable PDF
- PDF to PDFA conversion results invalid output
- API throws NullReferenceException upon loading a PDF document
- PDF file is not being optimized
- PDF to PPTX: Space between words increased
- PDF to PPTX: text alignment issue
- PDF to DOCX: text alignment issue in table row
- PDF to DOCX: bullets and associated text alignment issue
- PDF to PPTX - Line spacing is lost and the data is not rendering correctly
- PDF to DOCX: Paragraph indent values are not retained
- PDF to PDF/A - Highlight box hides the image in PDF
- Editing PDF document overlaps text characters
- In evaluation mode only, dispose method throws IndexOutOfRangeException
- API throws ArgumentException while resizing PDF

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

 

[aspose_seo]

Add images & Attachments Data for Microsoft OneNote Online File Formats using .NET

What is new in this release?

We are pleased to announce the release of Aspose.Note for .NET 16.12.0 . This month?s release provides support for images and attachments in Microsoft OneNote Online file format. It also fixes a number of bugs as reported in our last month?s release that further improves the API functionality. provided support for OneNote Online SharePoint file format. Support for this feature enabled the API users process OneNote online file formats without the need of installing Microsoft SharePoint on the machine. However, this feature had few limitations, such as Images from document were not supported and any attachments in documents were also not supported. Resultantly, a document loaded and saved with Aspose.Note API used to lose the images and attachments data contained in the document. This month?s release of Aspose.Note API, however, now removes these limitations and provides support for images and attachments data for Microsoft OneNote Online file formats. With this capability, OneNote Online files can be read as well as saved back without losing the images and attachments data. It has also fixed several bugs in this month?s release that further improves the API functionality. Specifically, the issues were related to the number of pages in the saved document and the loss of images. The list of new and enhanced features added in this release are given below

- Add support for images and attachments in OneNote Online files.
- Number of pages in Aspose.Note Document does not match original amount in *.one file.
- Saving OneNote document loses images.

Newly added documentation pages and articles

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

- Insert an Image on a OneNote Document Page
- Working with 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.

More about Aspose.Note for .NET

- Homepage of Aspose.Email for .NET
- Download Aspose.Note for .NET
- Online documentation of Aspose.Note for .NET

Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Export Images in Multi-Threaded Environment & Converting EMF to WMF Format using .NET

What is new in this release?

We are pleased to announce the new release of Aspose.Imaging for .NET 16.12.0 . The major development in this release is support for exporting images in multi-threaded environment. This release supports converting EMF metafile to WMF format. Support for DNG format has also been incorporated in this release. It now supports exporting images in multi-threaded environment. Aspose.Imaging for .Net ensure the optimized performance of operations during execution of code in multi-threaded environment. All imaging option classes (e.g. BmpOptions, TiffOptions, JpegOptions, etc.) in the Aspose.Imaging for .Net now implement IDisposable interface. Therefore it is a must that developer properly dispose off the imaging options class object in case Source property is set. Aspose.Imaging now supports SyncRoot property while working in multi-threaded environment. Developer can use this property to synchronize access to the source stream. Developers can convert EMF to WMF format using this release. Moreover, it also supports the DNG (Digital Negative) image format (.dng). It is a publicly available archival format for the raw files generated by digital cameras. DNG helps ensure that photographers will be able to access their files in the future. Aspose.Imaging for .Net provides the DngImage class to load DNG files and same can be used to convert the DNG to raster formats. It also enhanced reading PSD layers, processing of JPEG format images, Processing of Dicom format images, functionality to convert WMF to PNG format, rendering images in PSD file, saving TIFF frames, Compatibility of image saved using Aspose.Imaging on MS Windows 8 and reading JPEG pixels has been greatly improved. The main new and improved features added in this release are listed below

- Convert EMF to WMF
- ThreadSafe API support stage 1
- DNG format support
- Thread safe API for TIFF images
- Could not read layers in PSD file.
- JPEG format performance improvents
- Remove Imaging Drawing engine
- Iamprovements of performance and memory usage for Dicom
- Converting WMF to PNG format is not showing correct output [.Net]
- Exception when opening image in separate thread
- Improve performance of jpeg file format
- Aspose.Imaging is not showing correct resolution of PSD image
- License as Embedded resource is not working
- Incorrect saving result while using Image.Save(string path, ImageOptionsBase options, Rectangle boundsRectangle).
- Unify Metered API usage. Enable COMPACT configuration for Dynabic.Metering module.
- Can't do subsequent resizing of rotated WEBP image
- Converting WMF to PNG format destroying vertical text on Y-axis
- Exception in PNG encoder
- Jpeg pixels read by Aspose.Imaging differs from pixels read by System.Drawing
- Saved jpeg is displayed incorrectly on Windows 8
- Random ImageSaveException: Cannot decode strip 0. Details:, at TiffFrame.Save

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 for Aspose.Imaging for .NET
- Download Aspose.Imaging for .NET
- Online documentation of Aspose.Email for .NET

Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

What is new in this release?

We are pleased to announce the new release of Aspose.Diagram for .NET 17.1.0 . The new version of the API allows developers to export the Visio drawing with selective shapes into any other supported format. Aspose team is constantly improving Aspose.Diagram API for better performance and quality. Recently, it has improved the export quality of Visio drawings. The recent version also covers a number of regular bug fixes and enhancements. Using Aspose.Diagram API, developers can already convert Visio drawings to other supported formats. All these formats are listed in the documentation section known as Save Visio Diagram. Using the latest version or higher, developers can now select specific shapes, and then save the Visio drawing into any other supported format. The output drawing keeps only the selected shapes, since this feature adds more control over the way of exporting Visio drawings. This version also incorporates the fixes of injecting additional shapes in the Visio drawing, partial rendering of shapes, duplicate hyperlinks, and the general formatting problems of the diagram. These enhancements and bug fixes improve performance and accuracy of Aspose.Diagram API. Here is the list of important enhancements and bugs fixes in the new version.

- Save only the area of visible shapes not the whole page.
- Export only selective Visio shapes to the SVG format.
- VSD to PDF conversion, incorrect date format in the title shape.
- The background color of the tables is black on saving VSDX to PDF.
- The transparent background of images turns into white color on converting VSD to PNG.
- The color of shapes is not being preserved on converting a VSDX to PDF.
- The formatting of rectangle shape is missing on converting a VSDX to PNG.
- The shadow of shapes is not being rendered properly on converting a VSD to SVG.
- The color of callouts and text is not being preserved on converting a VSDX to PNG.
- A Microsoft Sharepoint Workflow shape is missing on converting a VSDX to PNG.
- Missing text items on converting a VSDX to PNG.
- Can't retrieve the fill color of rectangle shape from a VSDX diagram.
- Incomplete rendering of the dynamic connectors on converting a VSD to HTML.
- The rounded rectangle shapes are changed on converting a VSDX to PNG.
- The text items are displaced on converting a VSD to PDF.
- The functions of the cross-functional flowchart are missing on loading and saving a VSDX.
- Set custom property does not work.
- Duplicate hyperlinks are being added while converting a VSD to PDF.

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
- Download Aspose.Diagram for .NET
- Online documentation of Aspose.Diagram for .NET

Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Add Text inside Graph Object & Reference Single Image Multiple Times in PDF Files usi

What?s new in this release?

The latest version of Aspose.Pdf for .NET (17.1.0) has been released. This month release introduces some new features. Some of these are to add reference of an image for multiple times, break text for a table broken across the pages and to set different TabLeaderType for different TOC levels along with an enhancement to add text inside the Graph Object. This release also contains the fixes of bugs reported in previous versions by Aspose valued customers that improve the API functionality. Some of Aspose customers have requirement to use same image reference for multiple times in a PDF, it helps to reduce the PDF document file size. Aspose team has introduced XImageCollection.Add(Ximage) method in this release. It helps to refer existing image instance in the PDF document instead new Image. Previously, it has to use a single TabLeaderType for all the TOC entries. With the release of current version, now users can set different TabLeaderType for different TOC Levels. For this functionality, This release can set LineDash property of TOC Level with required value of TabLeaderType enum.In legacy generator (Aspose.Pdf.Generator), it has supported table break text to set some text string at the end of the page for the Table broken in two pages. This release, has implemented same feature in new generator (Aspsoe.Pdf). A customer requested an enhancement to add text inside a Graph object, for his business need. This release has added a text property in Graph object to add text inside the shape. The list of important new and improved features are given below

- Referencing XObjects for multiple times
- Add a row containing some text at the end of page if table is broken in two pages
- Set different TabLeaderType for different TOC Level
- Multiple reference to same image
- Add text inside Rectangle object
- Alignment of radio button text and checkbox text is not proper
- doc.Pages[1].Resources.Images.Names and - doc.Pages[1].Resources.Images[0].Name returns different names for same image.
- Jumbling words when converting Pdf to Html with UseZOrder = true
- Pdf file is not compilant with PDF/A-1a format (transparency and missing objects)
- Pdf file is not compilant with PDF/A-1a format (transparency)
- PDF to HTML - Links are converted into plain text
- PDF to HTML- Text Selection flickers
- PDF to HTML - Missing characters and invalid format of resultant file
- PDF to HTML - Missing characters and invalid format of resultant file
- Load single image instance for multiple times
- Stamp text alignment issue
- When PDF is converted to DOCX, the text formatting changes.
- XFA form conversion failure
- PDF to PDF/A - Formatting issues in resultant file
- DPDF to PDFA: transparent background is being rendered as black
- PDF to PDF/A - Resultant file is not correct
- PDF to PPTX - Text on first page is absent
- HTML/PDF to PPTX conversion issue
- HTML to PPTX: Missing white Text form HTML to PPTX
- Text position of TextFragment
- PDF to PDFA: compliance fails (soft mask in image)
- PDF to JPEG - Some characters rendered wrongly

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

Contact Information
Aspose Pty Ltd, Suite 163,
79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Metered Licensing Mechanism & Enhanced Conversion of AutoCAD DWG to PDF & PNG in .NET

What is new in this release?

Aspose development team is pleased to announce the release of Aspose.CAD for .NET 16.12.1 . The major development in this release is support for metered license mechanism. The new licensing mechanism will be used along with existing licensing method. Those customers who want to be billed based on the usage of the API features can use the metered licensing. Aspose.CAD for .NET provides the functionality to use metered licensing mechanism. It has introduced Metered class in API to accomplish this job. Sample code is provided that will demonstrate how to calculate the consumed CAD API requests. There are some important enhancements part of this release, such as Process of converting DWG to PDF format and converting DWG to PNG format in multithreading has been improved. The main new features added in this release are listed below

- Update Dynabic.Metered functionality
- Implement Underlay Flags for DWG format
- Implement drawing of DGN format as a part of DWG
- Converting DWG to PDF is showing incorrect results
- Implement reading insert coordinate and rotation angle for DGN underlay.
- Converting DWG to PNG in multithread is throwing exception

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 for Aspose.CAD for .NET
- Download Aspose.CAD for .NET
- Online documentation of Aspose.CAD for .NET

Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Add/Update Layers in PSD File & Convert PSD Layer to PNG Format inside .NET Apps

What is new in this release?

We are pleased to announce the new release of Aspose.Imaging for .NET 17.1.0 . The major development in this release is the enhancements incorporated in Aspose.Imaging to improve the overall performance of the API. This release has improved process of adding PSD layer & Support for JPEG lossless decoder has also been incorporated in this release. Some important enhancements are also part of this release, such as process of updating PSD text layer has been improved, Processing of updating PSD text layer with non-English characters has been improved, Processing of converting PSD layer to PNG format has been improved and functionality to add layers in PSD file has been improved. The main new and improved features added in this release are listed below

- Unable to add layers to PSD file
- Implement JPEG lossless decoder
- Converting PSD layer to PNG have lager font size then a PNG saved through Photoshop natively .Net
- Updating text layer with many more characters than the source is showing incorrect results .Net
- Updating text layer with non-English characters using Aspose, the characters are replaced by box .Net

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 for Aspose.Imaging for .NET
- Download Aspose.Imaging for .NET
- Online documentation of Aspose.Email for .NET


Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Add Extended Attribute Definition to a Project & Improved MPP Loading using .NET

What is new in this release?

We are happy to announce the release of revamped version of Aspose.Tasks for .NET 17.1.0 . This month?s release brings improvement to the public API for working with custom fields of a project. The new implementation makes it simple for creating extended attributes. This release also fixes a number of bugs reported with earlier version of the API. This release has improved the public API for working with custom fields i.e. Tasks as well as Resources. The improved version of this API simplifies adding an extended attribute definition to project and create extended attribute from this definition. The new implementation provides individual implementations for working with plain and lookup custom fields. The static methods of ExtendedAttributeDefinition class allow the creation of each type of extended attribute, such as Create Task Definition, CreationResourceDefinition, CreateLookupTaskDefinition and CreateLookupResourceDefinition. The sample code on the blog announcement page shows a basic illustration of this improved implementation for creating a Task lookup extended attribute. This month?s release also fixes several bugs that improve the overall API functionality, such as working with Extended Attributes of the API, lookup values error while assigning to task, large file size after creating task baseline and Saving Extended Task Attributes to output MPP. This release includes plenty of new features as listed below

- Improve public API to simplify working with Custom Fields.
- Extended attribute lookup table is not showed in XML format.
- MPP cannot be loaded into Project object
- False lookup table attached with an extended attribute while adding lookup with another extended attribute
- Wrong %Complete and ActualDuration calculated in MPP as compared to XML (.NET)
- Huge file size after setting baseline
- Extended attribute cannot be added to MPX
- Marking Tasks As Complete - Task Complete Indicator Not Displayed
- Extended attribute not saved properly to MPP file

Other most recent bug fixes are also included in this release

Overview: Aspose.Tasks for .NET

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

More about Aspose.Tasks for .NET

-Homepage of Aspose.Tasks for .NET
- Download Aspose.Tasks for .NET
- Online documentation of Aspose.Tasks for .NET

Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - The .NET and Java component publisher
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Import DirectX Files & Convert DirectX 3D Model to 3D Supported Formats inside .NET A

What is new in this release?

Aspose team is pleased to announce the release of Aspose.3D for .NET 17.02.0 . The new version adds support of importing DirectX (.x) files. Developers can import DirectX (.x) files (ASCII and Binary) into the Aspose.3D API, and then export them in any supported 3D format. Developers can install Aspose.3D Nuget package in their .NET applications because we publish each version as a NuGet package on the NuGet gallery. The X file format refers to files with the .x file name extension. The DirectX (.x) format is a template-driven format which can accommodate all your 3D gaming needs, from simple mesh?s to complete bone animation characters. Using Aspose.3D API, developers can convert a DirectX (.x) 3D model to 3D supported formats. All supported 3D formats are listed on this page: Save a 3D Document. These help topics will help to know the way of importing an existing X file, Reading a 3D Scene and Specify Load Options of 3D DirectX .x File. This release includes plenty of new features as listed below

- Add support of importing the X (binary and ASCII) files.
- Enhanced Reading a 3D Scene
- Import an Existing PLY File into the Aspose.3D API
- Add support of importing the DXF.

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 Aspose.3D for .NET
- Download Aspose.3D for .NET
- Online documentation of Aspose.3D for .NET

Contact Information
Aspose Pty Ltd, Suite 163,
79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Adjust CAD Drawing Size, DWG 2007 Format Support & Enhanced DWG to PDF Conversion

What is new in this release?

Aspose development team is pleased to announce the release of Aspose.CAD for .NET 17.2.0 . The major development in this release is the support for DWG 2007(AC1021) Format. This release supports determining the DWG external references and their file paths. The support for adjusting CAD drawing size has also been incorporated in this release. Aspose.CAD for .Net provides the UnitType enumeration to adjust the size of drawing during conversion of the CAD format. There are two ways to adjust the drawing size, firstly Automatic adjust size or Adjust size using UnitType enumeration. UnitType enumeration gives the ability to adjust scaling when Width and Height properties are not set. There are some important enhancements also part of this release, such as processing of entity order for DWG format, converting DWG to PDF format and Process of exporting external raster images linked with DWG file has been greatly improved. The main new features added in this release are listed below

- Normalize drawing size to absolute metrics
- Add support for clipping of raster images
- Determine the external references for a dwg and their filepaths
- Support for DWG 2007(AC1021) Format
- Implement right entity order for dwg format
- Converting DWG to PDF format is producing incorrect PDF file of 1kb size
- Converting DWG to PDF file is throwing exception
- Converting DWG to PDF is not exporting external raster images linked with DWG file

Overview: Aspose.CAD for .NET

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

More about Aspose.CAD for .NET

- Homepage for Aspose.CAD for .NET
- Download Aspose.CAD for .NET
- Online documentation of Aspose.CAD for .NET
Contact Information

Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Compare PPT/PPTX Presentation Slides & Identifying Merged Cells in a Table using .NET

What?s new in this release?

The long awaited version of Aspose.Slides for .NET 17.2.0 has been released. This release has some new features in this release along with resolution issues incurring in API. At times, one need to compare two slides if they are identical or not. Now, users can compare the two slides based on all shapes, styles, texts, animation and other settings. If slides are equal, true will be returned. For more details, please visit documentation article, Compare two slides. Aspose team has also included the support for identifying merged cells inside table as well. Please visit documentation article, Identify Merged Table Cells. It has rectified the issues related to charts and Ole frame data failing to get opened in edit mode inside PowerPoint for generated presentation. The issues related to URL formatting and tooltip text inside hyperlinks has also been addressed in this release. It has also addressed issues related to improper text rendering including bolding effects, improper color and improper gradient effects. It has resolved the issues related to presentation access and saving which earlier resulted in exceptions including ArgumentException, NullReferenceException and PptxReadException in previous releases. This release has improved the presentation rendering support and has resolved certain issues related to missing or improper text rendering, missing images, missing charts and its entities in generated PDF, HTML and slide thumbnails outputs. This list of new, improved and bug fixes in this release are given below

- Check whether presentations master slides are identical
- Identifying the merged cells in Table
- Refactor charts implementation
- Insufficient header length error
- Unable to edit data in chart after just opening and saving presentation (without modification)
- Exception on converting pptx to pdf
- Presentation file not converted properly to pdf
- Exception on loading presentation
- Footer is changed after saving ppt
- Cloning a chart object creates a corrupted chart
- Ole frame un-editable when saving presentation
- Problem while converting ppt to pdf
- System.ArgumentException on saving PPTX to PDF
- When PPT is loaded and saved, the date format is changed
After load and save of PPT file, the footer disappears.
Exception on saving ppt
- Footer text color and font changed after saving
- Exception on saving ppt
- Pptx not properly converted to pdf
- Hyperlink and tool tip text change for hyperlink on saving presentation
- Bold effect not applied
- Pptx not properly converted to pdf
- ReadWorkbookStream method returns empty workbook
Exception on loading presentation
Hyperlink Value changed for portion text
Animation effect gets corrupt on changing paragraph text
- Ppt changed after saving
- External Hyperlink is not getting set for text
- Vector images background changed
- Ppt changed after saving
- Hyperlink (URLs) with Unicode text becomes with duplicates characters
- Font looks bold on rendering
- Instead of some images "no image" placeholder rendered for x86 build
- Incorrect link detection
- Shaped removed after saving ppt
- Argument exception on loading the presentation
- Text color changed after saving presentation.
- Protected view message thrown on opening saved presentation
- Conversion to PPT fails with exception PPT presentation can't contains more than 8 placeholders in one slide.
- Empty pages generated when converting ODP to PDF
- Hyperlink to absolute file path doesn't work for PowerPoint 2007
- Category axis labels are missing or improperly rendered in generated PDF
- Error on opening the generated PDF file from PPT file
- StringIndexOutOfBoundsException on reading Hyperlink text
- Improper gradient rendering in generated PDF
- Font Rotation does not set the value for rotated font

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.

More about Aspose.Slides for .NET

- Homepage of Aspose.Slides for .NET
- Download Aspose.Slides for .NET
- Online documentation of Aspose.Slides for .NET

Contact Information

Aspose Pty Ltd, Suite 163,
79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose ? Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465

 

[aspose_seo]

Word 2013 Documents Provision & Variables Support in LINQ Reporting Engine using .NET

What is new in this release?

Aspose development team is happy to announce the monthly release of Aspose.Words for Java &.NET 17.3.0 . This month?s release contains over 67 useful new features, enhancements and bug fixes. Please see the release notes for more detail. Here is a look at just a few of the biggest features and API changes in this month?s release; Full support for Word 2013 documents (roundtrip to/from DOCX), variables support and more new features are introduced in LINQ Reporting Engine, New Public OfficeMath properties: MathObjectType, Justification, DisplayType, Font substitution mechanism improved. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources, Asian font rendering improved (more precise metrics calculation), Stroke weight is now taken into account while rendering auto-sized Textboxes, Implemented next round of improvements in table grid algorithm, Improved table breaking logic in compatibility mode for tables with header rows, Improved table breaking logic for tables with nested tables in a cell with bottom margin set, Improved tables breaking logic for tables with vertically merged cells having horizontal borders and Implemented fitText option for table cells. Starting from this release, Aspose team has added the full support of MS Word 2013 documents. The full support of roundtrip to/from DOCX is available in this Aspose.Words version. Previously, Aspose.Words performed font substitution only in cases when FontInfo in the document for the missing font doesn?t contain the PANOSE. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources. In case of font substitution the warning is issued with text. Please note that now font substitution mechanism will override the FontSettings.DefaultFontName in cases when FontInfo for the missing font is available in the document. FontSettings.DefaultFontName will be used only in cases when there are no FontInfo for the missing font. Moreover, please note that font substitution algorithm in MS Word is not documented so, the result of Aspose.Words font substitution may not match MS Word choice. Aspose team has introduced new property in this release that allows user to get type MathObjectType of this Office Math object. The MathObjectType enumeration is added in Aspose.Words 17.3 to specify type of an Office Math object. It has introduced new option in that removes empty rows that contain mail merge regions from the document. It has also added new public properties Justification and DisplayType into the OfficeMath class. It has also added new public property Field.LocaleId in this release that allows user to get/set field?s locale. It has also added new paramerter -fitSizeLim for image tag to change the size of the textbox according to the size of the image without increasing the size of the textbox. It has also added support for variables in Aspose.Words 17.3 LINQ Reporting Engine that enables users to use variables in template documents. Variables are useful when users need to calculate an expensive value just once and access it multiple times in a template. The list of new and improved features added in this release are given below

- New public OfficeMath properties: MathObjectType, Justification, DisplayType
- Full support for Word 2013 documents (roundtrip to/from DOCX)
- Variables support and more new features are introduced in LINQ Reporting Engine.
- Font substitution mechanism improved. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources.
- Asian font rendering improved (more precise metrics calculation).
- Stroke weight is now taken into account while rendering auto-sized Textboxes.
- Implemented next round of improvements in table grid algorithm.
- Improved table breaking logic in compatibility mode for tables with header rows.
- Improved table breaking logic for tables with nested tables in a cell with bottom margin set.
- Improved tables breaking logic for tables with vertically merged cells having horizontal borders.
- Implemented fitText option for table cells.
- Add MailMergeCleanupOptions option to remove empty row
- Cell's content are warped incorrectly in output Pdf
- PDF output is incorrect for 2 text columns
- Add feature to set background color of table row using Linq Reporting Engine
- Insert image dynamically using Linq without change size of textbox
- Justification of OfficeMath object
- Obtain type of the MathObject
- Add feature to define variables in LINQ Reporting template
- Provide ability to specify locale at Field level
- Implement reading of themes for RTF format.
- Support of MS Word 2013 documents (WORDSNET-7741 and WORDSNET-7964)
- /table grid/ Cell's content is rendering a few inches to the right in PDF
- Table header should be pushed to the next page if no rows fit below header in 2013 mode
- Table header row orphaned in 2013 mode
- Mail Recipient is lost after re-saving Doc
- Add/remove document settings if OptimizeFor is called for a document
- Incorrect Asian font metrics
- Saving resources when converting Words documents to HTML
- Fonts substitution // Improve font substitution rules.
- Paragraph formatting is lost after re-saving Docx
- Underline/strikethrough formatting is applied to revisions imported from HTML
- Compare and Reject feature do not mimic Microsoft Word's behavior
- /nested row break height/Text moves to previous pages after conversion from Docx to Pdf
- /fitText/ Chinese text render on next line in HtmlFixed
- /table break header row/ Converting from .docx to .pdf loses table header
- /table break header row/ Table is rendered on previous page after conversion form Docx to Pdf
- Table header moves to previous page bottom in PDF
- EndnoteOptions are not saved if the document does contain endnotes
- /table break/ All pages show some content from next page at bottom in PDF
- Paragraph's spacing is changed when InsertDocument is used with UseDestinationStyles mode
- Hebrew date field renders incorrectly in Pdf
- Incorrect formatting of 'Normal (Web)' after import from another document
- Text in image is missing when exporting to HTML
- More vertical spacing between lines added when exporting to HTML
- Output Docx is not opened in MS Word after performing mail merge
- Bookmark entries are not entirely merged after mail merge
- Z-order is incorrect after conversion docx to odt.
- Some table rows render on the previous page of PDF
- Bullet list is changed to numbered list after conversion from bytes to Docx
- ShapeAttr.LineFillBlipName attribute returns invalid value
- A strange Box appears near certain images in PDF
- TTFontMetrics.BoldSimulationScale is not too accurate for MS Gothic
- Hyperlink encoded twice in PDF
- Aspose.Words ignores stroke weight for autosized textboxes
- Shape with caps is not rendered correctly
- Docx to Pdf conversion issue with StructuredDocumentTag rendering
- List label size differs in layout.
- Content of StructuredDocumentTag is lost in output Pdf/Doc
- Docx to Html conversion issue with chart's axis bounds
- Ref field generates error code after conversion from FlatOpc to Doc
- TOC update does not see format revision changes.
- Position of AutoShape is changed after Appending.
- Fonts substitution // Measurements: Spacing of text lines in PDF is different to when viewed in MS Word
- Fonts substitution // Incorrect fonts rendering.
- Docx to HtmlFixed conversion issue with fonts
- /advanced typography/ Arabic text is incorrectly rendered to PDF
- WordArt // Multiline // Watermark shape is not rendering correctly in PDF
- Contents position is changed after conversion from Doc to Pdf
- Table's contents move to next page after conversion from Doc to Pdf

Other most recent bug fixes are also included in this release

Overview: Aspose.Words

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

More about Aspose.Words

- Homepage of Aspose.Words for .NET
- Download Aspose.Words for .NET
- Online documentation of Aspose.Words for .NET

Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465