This happens on not-properly-produced .pdf files, with custom encodings but without cmap (toUnicode) entries. Unfortunately, there are a lot of them out there!
When selecting text, evince (erroneously) displays the characters that will be copied to the clipboard, instead of the original glyphs.
Explanation: There is a PDF specification "feature", where one can declare that the character 'A' maps to the glyph 'B'. So if 'A' is written in a pdf text object, it displays as 'B' but it gets copied as 'A'!
My English is poor, so I made a ***minimal*** .pdf that reproduces this bug.
If you open it in Evince and select all the text, the line that contains
BCDΓ
should display
ABC<display artifact>
when selected!
This happens on not-properly- produced .pdf files, with custom encodings but without cmap (toUnicode) entries. Unfortunately, there are a lot of them out there!
When selecting text, evince (erroneously) displays the characters that will be copied to the clipboard, instead of the original glyphs.
Explanation: There is a PDF specification "feature", where one can declare that the character 'A' maps to the glyph 'B'. So if 'A' is written in a pdf text object, it displays as 'B' but it gets copied as 'A'!
My English is poor, so I made a ***minimal*** .pdf that reproduces this bug.
If you open it in Evince and select all the text, the line that contains
BCDΓ
should display
ABC<display artifact>
when selected!
Kind regards,
Alkis Georgopoulos