Contents getting moved to different (what's in source) pages during PDF conversion


#1

We are using PDF conversion functionality. However, we are noticing that the contents are getting moved to different pages than what’s in the source document. I am attaching the attached source and converted snapshots. We are using the default save PDF method like this

doc.save(fileName + “.ASPOS.pdf”, SaveFormat.PDF);

Source:ConvertedPage3.JPG (96.3 KB)
ConvertedPage4.JPG (120.7 KB)
SourcePage4.JPG (61.0 KB)


#2

@nirupamc

Would you please share that from which file format you are generating PDF document? Please share input/output files along with sample code snippet which you are using. We will test the scenario in our environment and address it accordingly.


#3

Hi Asad,

We are trying to convert a word document to PDF. Unfortunately, the forum is not allowing me to upload the doc file. Is there any other way I can send the source file?

This is the code snippet that we are using

public static void createPDF(String fileName) throws Exception{
	
    Document doc = new Document(fileName);
    doc.save(fileName + ".ASPOS.pdf", SaveFormat.PDF);
    System.out.println("Created PDF successfully for " + fileName);
}

Please find the output files

Iccba6710d95011e9ab71ab201e7009a5.doc.ASPOS.pdf (185.5 KB)


#4

@nirupamc

Please ZIP the source word document and attach it here so that we may proceed further.


#5

Attaching the zip that contains the source and the converted PDF.

The page breaks start to differ at page 12.

Please let us know how to fix that since it’s a showstopper issue.

Thanks,

Nirupam

conversion_issue.zip (235.4 KB)


#6

@nirupamc,

We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-19498. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.


#7

Can the development team narrow this defect to a specific use case? In other words, in which scenarios the converted output differs from the source? That will help us to mitigate this issue better on our end until a fix is available.


#8

@nirupamc,

The problem (WORDSNET-19498) actually requires us to implement a new feature in Aspose.Words API and we regret to share with you that the implementation of this issue has been postponed for now. There are no estimates/workarounds available at the moment. However, the fix of this problem may definitely come onto the product roadmap in the future. You will be notified via this thread as soon as the linked issue is resolved. We apologize for your inconvenience.