input and output file screenshots
original file:
inequality_R1.docx (45.3 KB)
<dependency>
<groupId>com.aspose</groupId>
<artifactId>aspose-total</artifactId>
<version>23.8</version>
<type>pom</type>
</dependency>
input and output file screenshots
original file:
inequality_R1.docx (45.3 KB)
<dependency>
<groupId>com.aspose</groupId>
<artifactId>aspose-total</artifactId>
<version>23.8</version>
<type>pom</type>
</dependency>
@TandFSP
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-26093
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.
HI, what does postponed mean, will this be resolved?
@TandFSP We have completed analyzing the issue. The issue occurs table “new” layout algorithm logic is not applied to the problematic table because of an inline oMath
element inside: oMath
element metrics are not considered reliable. Aspose.Words falls back to older approach which does not handle the table correctly.
Postponing until the problematic table is supported by the new logic. Unfortunately, there are no estimates at the moment.