FAQ

This page contains answers to the most frequently asked questions. Please learn the current page – perhaps this will allow you to solve your problem quickly.

If you have not found the answer to your question, you can ask on the support forum. For information on how to properly report your question or problem, see the “Technical Support” page.

General

Q: What is Aspose.Words?

Aspose.Words for Java is a class library that enables your applications to perform a wide variety of document processing tasks. With Aspose.Words for Java, you can generate, modify, convert, render, and print documents without third-party applications.

Details can be found in our documentation.


Q: What does it mean “Aspose.Words does not require third-party applications”?

Aspose.Words for Java does not need to install any third-party applications or additional software packages to work. Just download and install Aspose.Words as described in the ”Installation” article and get started.


Q: What platforms does Aspose.Words support?

Aspose.Words for Java covers most of the popular development environments and deployment platforms. Its API can be used to develop applications for a wide range of operating systems such as Windows, Linux, and Mac OS, and various platforms.

For details, see the “Product Overview” page and the “Platforms and Interoperability” section.


Q: What document formats does Aspose.Words support?

Aspose.Words for Java supports most of the popular document formats such as DOC, DOCX, HTML, Markdown, PDF, XML, and others.

You can see the complete list of supported formats on the “Supported Document Formats” page.


Q: How can I try Aspose.Words free?

You can do this in two ways – using the Trial version or a 30-day Temporary License. The Trial version is the same as the purchased one, it provides full product functionality but adds an evaluative watermark at the top of the document when loading and saving and limits the maximum document size to multiple hundred paragraphs. A Temporary License enables you to test Aspose.Words without Trial restrictions for 30 days.

See the “Licensing and Subscription” page for more information.


Q: How can I buy Aspose.Words?

To buy an Aspose.Words license, you need to go to the Purchase page, select the “Aspose.Words” product and the type of license that suits you. Then add the license to your cart and follow the Shopping Cart instructions.

After purchasing, apply for the license as described in the “Purchased License” section.

Details on how to install Aspose.Words can be read on the “Installation” page.


Q: How can I get support?

Use the free technical support forum. For details on how to properly report a problem and what needs to be done before contacting the forum, see the “Technical Support” page.

Rendering a Document

Q: Why are the layout and fonts in the output document different from the original?

The font may not be available, or the font format is supported by Microsoft Word but not supported by Aspose.Words. Aspose.Words will perform font substitution.

To check if the font is missing:

  • In Aspose.Words use the Font substitution warnings (for details, see the “How to Recognize That the Font Was Replaced” section of the “Manipulate and Substitute TrueType Fonts” article).
  • In Microsoft Word open the “Font Substitution” dialog box (File → Options → Advanced → Font Substitution).

Q: Why does not the font fallback work on non-Windows platforms and Unicode characters are replaced with the .notdef glyph?

We can often see the .notdef glyph instead of some Unicode character. This is usually a box or a question glyph.

This is because Microsoft Office fallback settings are selected by default, and Microsoft Office fonts are not available. Users have to install Microsoft Office fonts or alter fallback settings.


Q: Why might complex script text, such as Thai or Hebrew, be displayed inaccurately for some reason, such as the wrong position for diacritics or inaccurate ligatures?

Some complex script fonts require the Advanced Typography features to be processed in order to display them correctly. Advanced Typography is disabled in Aspose.Words by default. Users have to enable Advanced Typography with TextShaperFactory.


Q: Do I need license files for the fonts I use?

Yes, you do. Therefore, when copying fonts, keep in mind that most fonts are copyrighted. Locate font licences beforehand and verify that they can be freely transferred to another machine.

Nested Mail Merge

Q: Why are there no merged fields in the generated output?

The original name of the merge field stays the same without being replaced by the required data from the data source, then:

  • Check the data is being loaded properly into tables: set the TableName correctly with all required primary keys and relationships.
  • Check that the merge fields are named properly. Use the GetFieldNames method to get all merge fields names and ensure that the name of merge fields in your template matches the one in your data source.

Q: Why does the output of nested merging not display data from the child table for the first entry in the parent table but display all items for the last entry in the parent table, even ones that are not actually linked to it?

This is because the merge regions in the template are not correctly formed, which can make all nested mail merge regions to stop displaying anything at all. The StartTable opening tag and the EndTable closing tag must match and be in the same row or cell. For example, if you start nesting merge regions in a cell of a table, you must end the merge region in the same row as the first cell.


Q: Why does each entry from the parent table display every item in the child table, even ones that are not actually linked to it?

This is because the relationship between the parent and child tables are not set up or they are incorrectly set up. It is necessary to:

  • Ensure data integrity within your DataSet and use the DataRelation object to represent the parent-child relationship between related data tables.
  • Check the section “How to Set Up Data Relations in Nested Mail Merge with Regions” in the article “Nested Mail Merge with Regions”.

Q: Why is an exception: “System.ArgumentException: This constraint cannot be enabled as not all values have corresponding parent values” while executing nested mail merge?

This happens because not every parent record has a child record so your data source does not match the following criteria: every row in the parent table should have a one-to-one relationship with the rows of the child table based on the primary and foreign keys.

Disable foreign key constraints when you create a DataRelation.

Append or Insert a Document

Q: Why does not content appended to a document appear on the same page?

The append result appears on a separate page because of a difference in PageSetup settings for the sections where the documents are appended together. Make identical PageSetup settings for the sections where the documents are appended together.

Convert a Document

Q: How to convert DOCX to PDF?

It is very easy as well, just load a document to the model and save it to any supported format.

The following code example shows the process of converting a DOCX file to PDF:

// Open the source DOCX document.
Document doc = new Document(dataDir + "Input.docx");

// Save the document to PDF format.
doc.save(dataDir + "output.pdf", SaveFormat.Pdf);

Manipulate with a Document

Q: How to split a document page by page?

Aspose.Words enables you to split a multi-page document page by page.

The following code example demonstrates how to divide a document and save each page as a separate document:

Document doc = new Document(dataDir + "TestFile (Split).docx");

int pageCount = doc.getPageCount();

// Save each page as a separate document.
for (int page = 0; page <= pageCount; page++)
{
	Document extractedPage = doc.extractPages(page, 1);
	extractedPage.save(dataDir + "SplitDocumentPageByPageOut_" + (page + 1) + ".docx");
}

Q: How to open an encrypted document?

You can try to open an encrypted document without a password, which should lead to an exception.

The following code example shows how to open an encrypted document with a password:

// Create a document.
Document doc = new Document();
DocumentBuilder builder = new DocumentBuilder(doc);
builder.write("Hello world!");

//OoxmlSaveOptions only applies to Docx, Docm, Dotx, Dotm, or FlatOpc formats.
OoxmlSaveOptions options = new OoxmlSaveOptions(SaveFormat.DOCX);

// Set a password with which the document will be encrypted, and which will be required to open it.
options.setPassword("MyPassword");
doc.save(getArtifactsDir() + "OoxmlSaveOptions.SaveAsDocx.docx", options);

// We will not be able to open this document with Microsoft Word or
// Aspose.Words without providing the correct password.
try
{
    doc = new Document(getArtifactsDir() + "OoxmlSaveOptions.Password.docx"));
}
catch (Exception e)
{
    Assert.assertTrue(e instanceof IncorrectPasswordException);
}

Q: How to print a document?

For a detailed answer, learn the article “Printing a Document Programmatically or Using Dialogs”.