I’m using Aspose 24.3 to convert a word document to pdf document.
With the recent versions the text alignment has changed.
It doesn’t match the word document layout.
When I switch back to Aspose 23.9 the pdf document is correct.
How can I get the pdf document with the same layout as the word document?
Is there an setting which I need to set?
@cternek
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-26684
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.
@cternek Yes, we have completed analyzing the issue. The issue occurs because table column widths in Aspose.Words layout do not match MS Word, i.e. the current Aspose.Words table layout algorithm does not fully mimics MS Word behavior. The issue is with the ‘new’ table layout logic. It appeared after new logic become applicable to the problematic table. Before 23.10, the table was not handled by the new logic because cells with ‘wrap text’ option turned off were not handled.
Unfortunately, currently we cannot suggest you any workaround. We should investigate MS Word behavior deeper to make Aspose.Words behave the same.
Hey @alexey.noskov
may I ask if there will be a fix for the issue in one of the next versions?
I actually wanted to update to the newer version to provide the new Aspose version to my customers which are urgently waiting for those fixes.
But the issue with the table layout in pdf will affect my customers so I can’t update to the 24.3 version.
@cternek Unfortunately, there are no news regarding the issue yet. It is not likely the issue will be resolved in the next version of Aspose.Words, since release window is closing in a couple of days. Please accept our apologies for your inconvenience.
@cternek Unfortunately, the issue is still not scheduled for development. So currently we cannot provide you any estimates. please accept our apologies for your inconvenience.
we recently noticed that this issue has been postponed.
Many of our customers are using the “wrap text” table option, and we are unsure how many of their documents are affected by this bug.
As a result, we are currently unable to update to the latest version, even though it would resolve other issues.
We have determined that updating to the new version of Aspose is too risky, as it could cause problems for our customers.
However, we are eager to work with a new version of Aspose because our users are waiting for bug fixes, such as WORDSNET-23433, WORDSNET-24805, WORDSNET-24655, WORDSNET-25722, WORDSNET-26229.
Is there any workaround or option we can set in the code to avoid this issue?
Additionally, could you please clarify what “postponed” means in terms of the timeline, and let us know what options are available to expedite this fix?
@cternek I am afraid there is no programmatic workaround we can suggest at the moment. We spent some time on this issue, but could not produce a satisfactory fix.
The issue is with table grid calculation logic. Especially in the method that was introduced in order to imitate MS Word layout and it works correctly for some of the documents.
However, it breaks the computation for the document in this request. Apparently, the logic should be under some condition. We managed to find only a part of the condition, but there must be some other part, and it proved difficult to figure it out. Apparently the logic is related to some glitchy/unstable MS Word behavior as minor and seemingly unrelated changes to the table may trigger it on or off. So we decided to postpone the issue for now as a quick fix did not work out.
Postponed issue status means that no active work is done on the issue right now and the issue is not currently planned for development.
You can try to escalate the problem in the paid support, in this case the issue will be pushed upper in the queue. but still this does not guarantee a quick fix, since the problem is quite tricky.
Please accept our apologies for your inconvenience.