Faolind

I'm afraid your conclusion is wrong. As I stated, that is a snippet via "Print to PDF" which "prints" the displayed PDF page as a series of images. as I stated- but I don't have another way to snip out a non-sensitive page from the rest of the sensitive material. So, While I appreciate your help, your conclusion is misinformed.

Is there a way to fix this? Calibri shouldn't have this sort of problem, right? Also is there a way to verify this is the issue, by checking my font files, for example?

All fonts are installed, I've just checked. One of the fonts in question is Calibri, another is Papyrus. As calibri is ubiquitous, I didn't think to check. The document itself is business-sensitive. However, let me see if I can find an unobtrusive page... Attached- "Page 7" is the altered page, exported by Affinity. "Page 7 (Original)" is the original text, exported via Reader as Print To PDF (I don't have access at current to another export method outside of Affinity, so while this erases the original encoding, it is the best I have for comparison). You may note a couple small errors similar to the Affinity export, this is because this has happened multiple times, and the first time we simply tried to correct it manually, clearly we missed some on that first pass. Page 7.pdf Page 7 (original).pdf

Tiny bump because this post was invisible a long while while it got approved.

I am having an issue when loading a PDF document. The document is read properly when loaded in Adobe Reader, but when processed intro Affinity the following Text errors occur- "ti" becomes "I " (space intentional) or "Ł " or "È" "ti" (bold intentional) becomes "Ĉ" "tt" becomes "N" "ft" becomes "J " (space intentional) I may have missed some examples. Whats also interesting is that this error is not consistent, some words are corrupted, others are not, and there doesn't seem to be a pattern as to which are corrupted or not. The error becomes permanent if saved as a pdf from affinity (that is, Adobe reads the text error and not the intended text after Affinity creates a new PDF save file), however, simply closing the document without saving and opening it in Reader shows no error. This issue has appeared on versions of Affinity both 1 year old and current. I have searched and not found anyone else discussing this issue. I am using Win10 64bit, and when loading into affinity I select "Load All Pages" Estimate/Estimate, and "Group lines of text into text frame." Affinity claims all fonts used by the document are available, in the options dialog box. I am really not sure what to do, but as you can imagine, with over 100 pages of text, the rate of typos is far too much to simply address each time I have to reload a PDF file into Affinity. Edit- I am using only Affinity Publisher, and also I have tried checking "Favor Editable Text over Fidelity" (It didn't help).