Hello Tim,

Thank you for the detailed feedback and for confirming that the fix in 2026.3.923 resolves the original mid-word text wrapping issue. We're glad to hear that the behavior is now back to what you were seeing in 2026.3.810 for that scenario.

At the same time, we're sorry to hear that you're still encountering a related issue in your production reports. We appreciate you taking the time to investigate the behavior and provide such a thorough description of the remaining problem.

We also appreciate the effort you've put into preparing a reproducible sample and the side-by-side comparisons between the different versions. Unfortunately, I'm not able to see the updated project attachment you referenced in your message. Could you please reattach the sample so we can review it?

Additionally, we would recommend opening a separate support ticket for this issue. Although it appears to be related to the original regression, it represents a distinct behavior that will be easier to track, investigate, and communicate about in its own thread. Keeping the discussions separate also helps avoid very long conversations where multiple issues become mixed together, which can sometimes lead to confusion during the investigation process.

One other important point is that the current discussion is attached to a public Feedback Portal item. Any files or other resources shared here may be publicly visible. For that reason as well, we recommend opening a new support ticket and attaching the project there, where the files can be reviewed privately by our team.

Once you've created the new ticket and attached the sample, we'll be happy to take a closer look at the remaining behavior and continue the investigation there.

Thank you again for the detailed report and for helping us improve the product.

Regards,
Yoan
Progress Telerik

Hello Tim,

We completely understand the setbacks and inconvenience that regressions can cause, especially when they impact an important part of a customer's workflow. We take regressions very seriously, and our process specifically treats them with the highest priority to ensure they are addressed as quickly as possible.

With that in mind, I would like to inform you that the issue is already under development, and we plan to introduce the fix in our next Document Processing release.

We also agree that it is important for customers to have publicly available information about known regressions. This is one of the main purposes of our Public Feedback Portal, where reported issues are tracked and logged so that customers can stay informed about their status and any relevant workarounds or affected versions.

I have gone ahead and updated the public page for the reported issue to explicitly flag it as a regression and, importantly, to identify the exact version in which the regression was introduced. This gives customers visibility into the issue and allows them to make an informed decision about which version to use if they need to avoid it.

In parallel, the regression itself is being handled through our normal regression process, where it receives the highest priority. We appreciate you bringing this to our attention and understand the importance of getting the fix in place as soon as possible.

Regards,
Yoan
Progress Telerik