Header is not rendered properly for some pages in document. (ECDCTS-8821)

rnara · July 7, 2022, 1:38pm

Hi Team,

In output file header is not rendered properly from page no 30 to page 33.
From pages 1 to 30 are in A4 size and header appears correctly. From page 30, we see header is seen to be shifted left.

I tried the below code to transform the file.

String fileName = "C:\\Input\\WI-000436655 (2).docx";
com.aspose.words.Document document = new com.aspose.words.Document(fileName);
document.save("C:\\output\\WI-000436655 (2).pdf");

I have attached the aspose output file as well office output file in zip.files.zip (6.9 MB)

Thanks,
Arvind

alexey.noskov · July 7, 2022, 2:05pm

@rnara Thank you for reporting this problem to us. For a sake of correction it has been logged as WORDSNET-24091. We will keep you informed and let you know once it is resolved.

rnara · July 8, 2022, 6:15am

Hi Team,

Any update on this issue? Can you please provide us ETA as this issue is critical from customer?

Thanks,
Arvind

alexey.noskov · July 8, 2022, 6:35am

@rnara The issue occurs because incorrect column widths stored in the document are not re-calculated by Aspose.Words.
The problematic table in the header has incorrect column widths stored in tblGrid element. The logic required to re-calculate the table layout is being implemented per WORDSNET-832. Currently the new logic is not applied to auto-fit tables with inline DML shapes inside as inline DML metrics are not considered reliable.
The issue has been postponed until the problematic table is supported by the new logic. Unfortunately, currently there are no estimates when work on new table grid calculation mechanism is finished.

rnara · July 13, 2022, 6:11am

Hi Team,

Could you please explain the below query
“The issue occurs because incorrect column widths stored in the document are not re-calculated by Aspose.Words”

Also, if there is any workaround available for this issue.

Thanks,
Arvind

alexey.noskov · July 13, 2022, 6:27am

@rnara It means that MS Word stores incorrect column widths for the problematic table. Aspose.Words uses these values without recalculation, that causes incorrect table rendering.
Unfortunately, there is no workaround for this issue.

rnara · August 1, 2022, 6:13am

Hi Team,

Any update on this issue or ETA available? Customer is waiting for long. This issue is impacting all the documents and it has became quite a serious issue for them.

Thanks,
Arvind

alexey.noskov · August 1, 2022, 6:41am

@rnara Unfortunately, there is still no news regarding this issue. As I mentioned the issue is blocked by table grid calculation algorithm implementation. We are continuously work on this algorithm implementation and few table rendering improvements has been included into the latest releases of Aspose.Words. But since MS Word behavior is not documented the implementation of the algorithm requires a lot of investigation affords and time. So unfortunately, it is impossible to provide a fast point fix for this issue. Please accept our apologies for your inconvenience.

rnara · August 17, 2022, 6:01am

Hi Team,

Any update on this issue, Customer is waiting for long time?
Can you please provide us ETA?

Thanks,
Arvind

alexey.noskov · August 17, 2022, 6:27am

@rnara Unfortunately, there are no news regarding this issue yet. Please accept our apologies for your inconvenience.

rnara · January 31, 2023, 8:35am

Hi, Any update on this issue? Please share ETA for the fix.

alexey.noskov · January 31, 2023, 8:41am

@rnara Unfortunately, there is still no news regarding this issue. The issue is still postponed until WORDSNET-832 (table grid calculation algorithm implementation) is resolved.