The result of comparing two docs gets cut off on the right side when converted to PDF

Hello, I’m trying to compare two documents with Aspose Word and save the result as pdf.
However, when I convert it to pdf, the right side of pages gets cut off and I’m not sure how to solve it.

I tried with/without Autofit but it seems it isn’t really helpful.

original_doc = aw.Document("original.docx")
modified_doc = aw.Document("modified.docx")

original_doc.compare(modified_doc, "AuthorName", date_time=datetime(2024,10,6))

table = original_doc.get_child(aw.NodeType.TABLE, 0, True).as_table()
table.auto_fit(aw.tables.AutoFitBehavior.AUTO_FIT_TO_WINDOW)
    
original_doc.save("compare.pdf")

original.docx (18.6 KB)
modified.docx (18.4 KB)

If this can’t be fixed right now, I’m wondering if there is any workaround.
(I’m using this feature in my prod so it needs to be fixed anytime soon)

@Young0528
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-27446

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

WIll this issue be handled for Java as well? I’m using Java & Python and I’m seeing this issue for both

@Young0528 Yes, the issue will be resolved in all versions of Aspose.Words.

Thank you so much! One more question, in the meantime, is there any workaround to fit the result onto the page?

@Young0528 Unfortunately, there is no workaround of the issue. The issue occurs because table column widths are not re-calculated for a table with revisions.

1 Like

Okay, thank you for your prompt response Alexey. Have a good day!

1 Like

Hello Alexey,

I was wondering if there’s a timeline for resolving this issue? My team purchased the license few years ago, and we’re planning to upgrade to the latest version next year. However, we can only proceed with the purchase if this issue is resolved, as we’ve been receiving feedback about it from our customers.

@Young0528 Unfortunately, the issue has been postponed and is not yet scheduled for development. Please accept our apologies for your inconvenience.

1 Like