Aspose.Words

Known Issues in Aspose.Words for Java

The table below lists known issues and features that are not yet available in Aspose.Words for Java. These mainly affect rendering and will be addressed in the next few releases. Each issue is listed by component with a description of the missing feature and estimated date of fix.

Issue

Description

Planned

Rendering of document pages to EMF is not available.

Not implemented yet.

These methods are not provided in the public API.

TBA

Brightness, contrast, grayscale are not supported when rendering images.

Color transformations not implemented yet.

Image will output without color transformations.

2011

Some images will not render to PDF, XPS and SWF.

These types of images will render as red crosses:

·          JPEG images with CMYK color model.

·          Some "new" bitmap formats e.g. 48bpp.

·          Some TIFF images in unusual formats.

 

TBA

WordArt text is rendered in a simplified way.

Complex text path and some gradient fills are ignored.

TBA

Digitally signing PDF documents is not supported.

Certificates are not yet implemented.

These methods are not provided in the public API.

2011

Verification of DOC, DOCX and ODT digital signatures is not supported.

Detection of digitial signature is supported, but verification is not supported.

These methods are not provided in the public API.

2011

Field Update Engine number and date parsing differences.

In Aspose.Words for .NET and Aspose.Words for Java we rely on the parsing methods provided by each platform. They can differ slightly when using various locales.

Java parsing is stricter and this could cause some numbers and currency amounts in formula fields failing to parse on Java, they will parse on .NET.

TBA

Loading encrypted ODT documents is not supported on Java

The Java zip library seems to have a problem with loading this type of document.

When loading an encrypted ODT document an exception will be thrown.

TBA

High memory usage for large documents.

Large documents might take long to process or require more memory during processing.

2011

No hyperlinks from Programmers Guide to the API Reference.

Topics in this documentation mention classes and methods, but they are not linked to the appropriate pages in the API Reference.

2011