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

Free Support Forum - aspose.com

Document renders differently when saved to pdf

documentRendersDifferentlyToPDF.zip (75.5 KB)
Hello,

I have attached example template - we have some issue with the document rendering - there are differences between the same template saved to pdf and doc/docx.

Please not that attached example is a simplified version of the template sent to us by our Client and we can’t modify it in any way.
We expect that saving document to pdf would have the same result as saving it to doc.

Could you please take a look and let me know what might be the issue?

Thanks
Aga

@acturisaspose,

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-16891. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Is there any update on this ticker? Any time estimates?
thanks,
Marcin

@acturisaspose,

Thanks for your inquiry. Currently, your issue is under analysis phase. Once we complete the analysis of your issue, we will then be able to provide you an estimate. Thanks for your patience.

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

Hi Tahir,

I can see that the original templates we’ve attached are working fine now, however we still can replicate the issue with original document. I’ve prepared new test case for you where the same issue is still replicable.

static void Main(string[] args)
        {
            var document = new Document("FileLocation");
            document.Save("Out.docx");
            document.Save("Out.pdf");
        }

AsposePdfIssue.zip (104.4 KB)

Input, expected output (in docx) and incorrect output (pdf) attached. Please let me know if you need any more info.

Thanks,
Mateusz

@acturisaspose,

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-18213 . You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

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