Support of CMX Format

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Corel Metafile Exchange (CMX) is a metafile format that supports bitmap and vector information and the full range of PANTONE, RGB and CMYK colors. This format is used for data exchange in programs that work with vector graphics. It contains image data and also the metadata that describes it. The purpose of this post is to demonstrate how you can export existing CMX file to other formats (PNG, JPEG, BMP, TIFF) using Aspose.Imaging.

Convert CMX to PNG

Using Aspose.Imaging.ImageOptions.PngOptions class you can export existing CMX file to PNG format. CmxRasterizationOptions class is used to set different properties as per requirement.

Using CmxRasterizationOptions.Positioning parameter, you can set Positioning and size types of a graphics scene. CmxRasterizationOptions.Positioning parameter can take one of the following three values.

ValueDescription
DefinedByDocumentThe absolute positioning on the page that is defined by document page settings.

DefinedByOptionsThe absolute positioning on the page that is defined by options page settings.

RelativeThe relative positioning and size. Determined by the boundary of all graphics objects.

CmxRasterizationOptions.SmoothingMode parameter specifies whether smoothing (antialiasing) is applied to lines and curves and the edges of filled areas. CmxRasterizationOptions.SmoothingMode parameter can take one of the following six values.

ValueDescription
InvalidSpecifies an invalid mode.

DefaultSpecifies no antialiasing.

HighSpeedSpecifies no antialiasing.

NoneSpecifies no antialiasing

AntiAliasSpecifies antialiased rendering.

HighQualitySpecifies antialiased rendering.

The following code is loading existing CMX files using Image class and setting Positioning to DefinedByDocument and SmoothingMode to AntiAlias and exporting loaded CMX file to PNG.

Finally, after exporting the CMX file to PNG, the output PNG looks as follows:

The complete code of this post is available on GitHub.

Posted in Aspose.Imaging Product Family | Leave a comment

Create Tagged PDFs using Aspose.PDF for Java 19.2

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

PDF files contain text, images and other element of content that are combined together to make up an electronic document. In addition, there is a set of instructions which defines the logic of binding the content together known as Structure. The structure defines the correct reading order of a PDF file.

In a PDF file, the structure is known as Tags. These tags are the hierarchy of containers describing the semantics of the content inside them and are represented in an invisible layer behind the visible PDF content. A well-structured or well-tagged PDF document can help screen-reading applications, read the content easily. Furthermore, tagged PDFs can make a document accessible to Visually Impaired Individuals. These individuals can understand the content inside a PDF document using a screen reading application. Imagine using your computer with the screen turned off and you’ll get some idea of how important logical text-flow is. Similarly,
you’ll get some idea of how important well-structured tagged PDF document is for people who need screen-readers to read your PDF document.

Tags may be generated automatically for any PDF file using Acrobat Reader if the document is a very simple one. Otherwise, automated tagging does not produce correct results. In order to understand the automated tagging, we can go back to a quote from the movie Forrest Gump:

“My mama always said, life is like a box of chocolates, you never know what you’re going to get”.

Here – life is a user, the box is the PDF document and the chocolates are the Tags – you never know what tag you are going to get with the automated tagging.

This is where Aspose.PDF for Java API comes handy. The API offers functionality to create Tagged PDFs from scratch with high fidelity. ITaggedContent interface in the API helps defining the content properly and is the entry point for creating Tagged PDF Documents.

Aspose.PDF TaggedPDF Features

Following documentation articles demonstrate the functionality to create Tagged PDFs using Aspose.PDF for Java:

With Aspose.PDF for Java, you can also get content and structure of Tagged PDFs. Following articles shows the functionality along with sample code snippet(s):

Posted in Aspose.PDF Product Family | Tagged , , , | Leave a comment

Improved API Performance with Aspose.Email for Android via Java 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-email-for-android-via-javaWe are pleased to announce the release of Aspose.Email for Android via Java 19.1. This release includes enhancements and bug fixes which improve the overall functionality of the API. For a detailed note on what is new and fixed, you may visit the release notes section in the API documentation.

Enhancements in Aspose.Email for Android via Java 19.1

This release includes enhancements to the functionality of the API. These enhancements include reading OLM, MBOX, and MSG files.

Other Improvements

There are a lot more improvements made in this release. Following is a list of improvements included in this month’s release.

  • The formatting of HtmlBodyText in the output has been improved.
  • The ability to update the date in the header by using the MapiMessage class.
  • Improved MailMessage and MapiMessage classes.
  • Improved working with appointments.
  • MapiTask functionality has been improved.
  • The following conversions have been improved
    • MSG to MHTML
    • VCF to MSG
    • PST to MBOX

API Resources

Aspose.Email for Android via Java documentation section is your one-stop for learning all about the API. You can visit the documentation page of the API to know more about the API. For any of your queries, feel free to write to us over Aspose.Email forum.

Posted in Aspose.Email Product Family | Leave a comment

Improved API Performance with Aspose.Email for Java 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-email-for-javaWe are pleased to announce the release of Aspose.Email for Java 19.1. This release includes enhancements and bug fixes which improve the overall functionality of the API. For a detailed note on what is new and fixed, you may visit the release notes section of API.

Enhancements in Aspose.Email for Java 19.1

This release includes enhancements to the functionality of the API. The components improved in this release include Pop3Client, EWSClient, and ImapClient. MailMessage and MapiMessage classes have also been improved.

Other Improvements

There are a lot more improvements made in this release. Following is a list of improvements included in this month’s release.

  • The formatting of HtmlBodyText in the output has been improved.
  • The ability to update the date in the header by using the MapiMessage class.
  • Improved working with signed MSG files.
  • Improved working with MBOX files.
  • MapiTask functionality has been improved.
  • The following conversions have been improved
    • MSG to MHTML
    • VCF to MSG
    • PST to MBOX

API Resources

We have detailed information available online for getting started with the Aspose.Email for Java API. These are:

Posted in Aspose.Email Product Family | Leave a comment

Improved Font Substitution Process, Supported Inline Syntax Error Messages, and Improved Warnings for Image Processing

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Words for .NET logoWe are pleased to announce our next version Aspose.Words for .NET 19.2. This month’s release contains over 69 useful new features, enhancements and bug fixes. Please check the release notes to get an idea about all new features, enhancements and fixes made in this release. If you are planning to upgrade from older version of Aspose.Words to the current version, we would strongly suggest you to check the Public API and Backward Incompatible Changes section to know what APIs are changed so far.

 

Improved Font Substitution Process When Rendering Documents

Aspose.Words requires TrueType fonts when rendering documents to fixed-page formats (PDF, XPS or TIFF). However, there are situations when the exact font cannot be found and Aspose.Words must substitute a similar font instead. We have improved the font substitution process in this release of Aspose.Words. Please read the complete detail from following article.

Font Availability and Substitution

Supported Inline Syntax Error Messages into Template for LINQ Reporting Engine

By default, LINQ Reporting Engine throws an exception when encounters a template syntax error. To make things easier, the engine supports the ReportBuildOptions.InlineErrorMessages option that enables inline syntax error message into a template document at an exact position where the error occurs during runtime. For more detail, please read the following article.

Inline Syntax Error Messages into Templates

Improved Warnings for Image Processing Issues When Saving to PDF

Previously there was one generic warning with text “Unsupported image format.”. Now there are a specific warning for OutOfMemoryException with text “Not enough memory to load the image.” and a generic warning with text “Image cannot be processed. Possibly unsupported image format.”.

Removed Deprecated Public Property TxtSaveOptions.ExportHeadersFooters

We have removed deprecated public property TxtSaveOptions.ExportHeadersFooters from Aspose.Words API. Please use TxtSaveOptions.ExportHeadersFootersMode property instead. Please read the following article.

Export Header and Footer in Output TXT

Other Improvements

There are 69 improvements and fixes in this regular monthly release. The most notable are:

  • Supported inline syntax error messages into templates instead of exception throwing for LINQ Reporting Engine.
  • Improved font fetching and substitution mechanism with corresponding API changes.
  • Improved warnings for image processing issues when rendering to PDF.
  • Improved font fallback rendering for full-width character Unicode ranges.
  • Metafiles with “HeaderPlaceable” structure is now rendering regardless of structure checksum. (MS Word behavior).
  • The width of the DrawingML outline is now normalized if it is below the minimum value while rendering. (MS Word behavior).
  • Fixed a bug with incorrect calculation of DrawingML TextBox shape bounds.
  • Fixed a bug with the calculation of the shape boundaries if the document contains the attribute.ShapeLayoutLikeWW8 (the behavior of MS WORD 97 should be emulated).
  • Fixed a bug that caused an exception when rendering ultra-small text boxes in GDI+.
  • Fixed a bug with the distorted filling of the DrawingML shape outline when rendering grouped shapes.
  • Fixed a bug causing creation of blank images with zero size while rendering into HTML.
  • Improved ordering of number in RTL list labels.
  • Improved check box size calculation when active form fields are exported to PDF.
  • Fixed issue when document has “printer metrics” enabled and Windows has no printer driver installed.
  • Fixed hang when table cell is broken across pages when there is a floating shape anchor in it.
  • Fixed issue when text which has borders is wrapped around a shape and does not fit.

Aspose.Words for .NET Resources

The following resources will help you work with Aspose.Words for .NET:

    • Home page of .NET API.
    • Install using NuGet Package
    • Documentation – up-to-date documentation containing Programmer’s Guide, Knowledge Base and much more.
    • API Reference Guide – detailing the publicly exposed classes, methods, properties, constants & interfaces.
    • Aspose.Words Product Family Forum – post your technical questions and queries, or any other problem you are facing while working with Aspose.Words APIs.
    • Enable Blog Subscription – do not limit yourself, you can keep yourself updated with the latest news on Aspose.Words APIs, new features, fixes and other API related topics by subscribing to Aspose.Words blog.
    • Examples – we have published our code examples on the social coding website GitHub.com. Anyone could explore the code examples for learning purposes.
Posted in Aspose.Words Product Family | Leave a comment

Render documents using enhanced splitting algorithms in Aspose.HTML for .NET

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We are pleased to announce February release of Aspose.HTML for .NET 19.2 which can be downloaded from NuGet Gallery to be used in your .NET Applications. This version is basically a maintenance release which includes few internal improvements along with some bug fixes. We have improved page splitting algorithms which results in enhanced rendering of supported format documents. Few exceptions including ArgumentException and ApplicationException have also been resolved in latest version of the API. An overview of public API changes and improvements can be found in Release Notes of the API.

Aspose.HTML for .NET Resources

Please visit the following links for information regarding Aspose.HTML for .NET 19.2 and Release Notes section.

Posted in Aspose.HTML Product Family | Leave a comment

Create Barcodes with parenthesis in CodeText with Aspose.BarCode for Android via Java 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We are pleased to announce the release of Aspose.BarCode for Android via Java 19.1. This release enhanced the BarCodeGenerator API to support parenthesis in the CodeText. For a detailed note on what is new and fixed, please visit the release notes page for information of API documentation.

Support for parenthesis in CodeText

This release of Aspose.BarCode enhanced the BarCodeGenerator API to allow the CodeText to contain parenthesis. You may generate barcodes with parenthesis in the CodeText as shown below in the code example. 

com.aspose.barcode.generation.BarCodeGenerator generator = 
new com.aspose.barcode.generation.BarCodeGenerator(EncodeTypes.PDF_417);

generator.setCodeText("Sample.Code.Text(Example).20181203_150435");
generator.save(TestDirectory + "barcodeTest2.png", BarCodeImageFormat.PNG);

Aspose.BarCode for Android via Java Resources

As Aspose.Barcode for Android via Java is based on Aspose.BarCode for Java, the following API resources can be of help to you in getting started with Aspose.BarCode:

Posted in Aspose.BarCode Product Family | Leave a comment

Create Barcodes with parenthesis in CodeText with Aspose.BarCode for JasperReports 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.BarCode for JasperReports We are pleased to announce the release of Aspose.BarCode for JasperReports 19.1. This release enhanced the BarCodeGenerator API to support parenthesis in the CodeText. To view a complete list of fixes, please visit Aspose.Barcode for JasperReport 19.1 release notes page.

Support for parenthesis in CodeText

This release of Aspose.BarCode enhanced the BarCodeGenerator API to allow the CodeText to contain parenthesis. You may generate barcodes with parenthesis in the CodeText similar to the string given below. 

"Sample.Code.Text(Example).20181203_150435"

You can download the latest release of Aspose.BarCode for JasperReports from the following link: Download Aspose.BarCode for JasperReports 19.1.

Aspose.BarCode for JasperReports Resources

The following API resources can be of help to you in getting started:

Posted in Aspose.BarCode Product Family | Leave a comment

Create Barcodes with parenthesis in CodeText with Aspose.BarCode for Reporting Services 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We are pleased to announce the release of Aspose.Barcode for Reporting Services 19.1. This release enhanced the BarCodeGenerator API to support parenthesis in the CodeText. For a detailed note on what is new and fixed, please visit the release notes page for information of the API documentation.

Support for parenthesis in CodeText

This release of Aspose.BarCode enhanced the BarCodeGenerator API to allow the CodeText to contain parenthesis. You may generate barcodes with parenthesis in the CodeText as shown below in the code example. 

Aspose.BarCode.Generation.BarCodeGenerator generator = new
Aspose.BarCode.Generation.BarCodeGenerator(
Aspose.BarCode.Generation.EncodeTypes.Pdf417);

generator.CodeText = "Sample.Code.Text(Example).20181203_150435";

generator.Save(TestDirectory + "barcodeTest.png", BarCodeImageFormat.Png);

You can download the latest version of Aspose.BarCode for Reporting Services by visiting the Aspose.BarCode for Reporting Services 19.1 page in the downloads section.

Aspose.BarCode for Reporting Services Resources

You can get started with Aspose.BarCode for Reporting Services by making use of information available in the following:

Posted in Aspose.BarCode Product Family | Leave a comment

Create Barcodes with parenthesis in CodeText with Aspose.BarCode for Java 19.1

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We are pleased to announce the release of Aspose.BarCode for Java 19.1. This release enhanced the BarCodeGenerator API to support parenthesis in the CodeText. For a detailed note on what is new and fixed, please visit the release notes page of API documentation.

Support for parenthesis in CodeText

This release of Aspose.BarCode enhanced the BarCodeGenerator API to allow the CodeText to contain parenthesis. You may generate barcodes with parenthesis in the CodeText as shown below in the code example. 

com.aspose.barcode.generation.BarCodeGenerator generator = 
new com.aspose.barcode.generation.BarCodeGenerator(EncodeTypes.PDF_417);

generator.setCodeText("Sample.Code.Text(Example).20181203_150435");
generator.save(TestDirectory + "barcodeTest2.png", BarCodeImageFormat.PNG);

Aspose.BarCode for Java Resources

The following API resources can be of help to you in getting started with Aspose.BarCode:

Posted in Aspose.BarCode Product Family | Leave a comment