Why copied PDF text comes out garbled
The page looks perfect. You copy a sentence, paste it, and get nonsense. Nothing is broken on screen — the file simply never recorded what its characters mean.
What the file actually stores
A PDF draws text by number, not by letter. Each byte in a text instruction is an index into a font, and the font turns that index into a shape. Nothing in that process needs to know that the shape is a capital R.
For text to be copied, the file has to carry a separate table saying which character each index represents. When that table is missing or incomplete, the viewer has to guess — and its guess is what lands on your clipboard.
Why it is often missing
Some producers omit it because the document was only ever meant to be printed. Fonts using an identity encoding expose raw glyph identifiers, which a viewer may read as though they were ordinary characters. And a glyph taken from a symbol face — a bullet, an arrow, a mathematical sign — frequently has no sensible character to map to at all, which is why a single stray backslash or brace often appears in otherwise clean text.
What this editor does with it
The proportion matters, so it is measured rather than treated as all-or-nothing. A block where a fifth or more of the glyphs are unreadable is marked unsupported and left alone. A block with one or two unreadable glyphs stays editable and is flagged, because a dropped ligature should not cost you a whole paragraph.
Why refusing is the right behaviour
An editor that guessed would be replacing characters you cannot see with characters it invented. The result would look plausible, export cleanly, and be wrong — the worst combination available. Refusing to edit a block whose text is unknowable is the only honest option.
It also means this is not something the tool can fix. The information was not written into the file, and no amount of processing recovers it.
Related: the five reasons a PDF’s text will not edit, how PDF text editing works.