We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Differences in the conversion to PDF with Aspose 2

Best regard,

Currently in production environment we are having many problems because we have templates that lawyers want to be identical in the conversion of Word to PDF.

They also have a criterion and that is that the same officials save the file from Microsoft Word and see how the conversion is accurate and complain and are complaining that the conversions we are doing with the Aspose library are not true or identical copies of the document they view from Word and for legal documents it is very important that the conversion is accurate.

We are using the latest version of Aspose released for the Java Platform: aspose-words-18.3-jdk16.jar and Java JDK: jdk1.7.0_75

The source document is appended in Word and the two generated files, one with the conversion of the same Microsoft Word from the “save as” menu and the other document generated with the Aspose.Words for Java library. See attached document DOCS.zip.

Source code used:

package pruebaaspose;

import com.aspose.words.Document;
import static com.aspose.words.SaveFormat.PDF;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.FileOutputStream;
import java.util.logging.Level;
import java.util.logging.Logger;

public class PruebaAspose {

public static void main(String[] args) {

    Document doc;

        com.aspose.words.License license = new com.aspose.words.License();
        doc = new Document(new FileInputStream(new File("Doc_input.docx")));

        FileOutputStream fileOutputStream = new FileOutputStream(new File("Doc_output.pdf"));
        doc.save(fileOutputStream, PDF);

    } catch (FileNotFoundException ex) {
        Logger.getLogger(PruebaAspose.class.getName()).log(Level.SEVERE, null, ex);
    catch (Exception ex) 
            Logger.getLogger(PruebaAspose.class.getName()).log(Level.SEVERE, null, ex);


DOCS.zip (1.0 MB)


Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-16628. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

1 Like

The issues you have found earlier (filed as WORDSNET-16628) have been fixed in this Aspose.Words for .NET 19.12 update and this Aspose.Words for Java 19.12 update.