Working on imported and exporting PDF through PdfFormatProvider makes it visually broken

[Bilal]

Hi,

we have editable PDFs which are stored in a database. We used to be able to pull the PDFs, import them through the Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider to get a RadFixedDocument, iterate through the fields of this document and fill them with data. Afterwards, we exported the PDF through the PdfFormatProvider and wrote them to a file. This gave us the original PDF but filled with the required data.

This does not work anymore, as the resulting exported PDF is visually broken. We have no clue why that happens, maybe you can help us fix this.

I attached a small sample project with our work flow including one of the PDFs we try to fill out and the resulting PDF for you to analyze.

Thanks a lot in advance.

[Yoan]

Hello Bilal,

Thank you for the provided resources and detailed description of the case.

Please accept my apologies for the inconvenience. I was able to reproduce the same results on my end and it appears that you are encountering an issue on our part that stems from a functionality introduced in our latest Q4 2024 official release.

We already have this issue under development and we plan on introducing the fix with our next upcoming Document Processing Q1 2025 official release, scheduled for mid-February - PdfProcessing: Missing Text with specific cultures (e.g. German). If you are interested in this task, please know that you can subscribe to it so you can track its progress by receiving notifications about future status updates.

That said, because the issue has to do with the currently set culture, I can confirm that as a workaround you can try explicitly changing it to "English (en-US)" at the start of the application which should produce the expected results:

Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");

I hope this helps. Please know that I remain at your disposal in the meantime.

Regards,
Yoan
Progress Telerik

[Bilal]

Thanks, i can confirm it is fixed with the Q1 2025 update. :)