Re: Table width in percent is not honored when converted from DOCX to XPS

Aspose.Words Product Family
1

The same problem is faced with wordml to Pdf conversion, with aspose-words-16.2.0-java

2
Hi Vishal,

Thanks for your inquiry. Could you please attach your input WordML document and output PDF file showing the undesired behavior here for testing? We will investigate the issue on our end and provide you more information.

Best regards,
3

Hi,

Attached is the WML that has the problem.
4
Hi Vishal,

Thanks for your inquiry. 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 as WORDSNET-13405. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.

Best regards,
5

Hello Awais,

Thanks a lot for the response.

We have plans to introduce and procure Aspose for our upcoming major release.

With this open issue, it would be very hard for us to proceed, as this has an impact in almost 2298 instances considering all our WML files. And it would be a big change, if we have to consider giving this some fix.

Can you please help expedite this and let us know your plans in addressing this?

Thanks a lot. Awaiting your response!

Best Regards
6

Hi Vishal,


Thanks for your inquiry.

Unfortunately, your issue is not resolved yet and there are no estimates available. Our product team has completed the analysis and the root cause of this issue has been identified. However, because of complexity, the implementation of the fix of this issue has been postponed till a later date. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

The issue occurs because a missing table grid in the document is not calculated correctly.

The issue is to be addressed by the new table grid calculation implemented per WORDSNET-832. However, currently the new algorithm is not applied to WML input because of issues with some of the documents.

We are postponing it until WML input is handled by the new algorithm.

Best regards,
7

The issues you have found earlier (filed as WORDSNET-13405) have been fixed in this Aspose.Words for .NET 22.5 update also available on NuGet.