I have used this on a couple of different programs, and each time the pdf that is generated looks just fine. But when you select the underlying data, say in Acrobat or Reader, and paste it elsewhere, you discover boxes. Further research shows that the codepoints are being assigned the Private Use Area, and given a value FFFE3 codepoints greater than the original encoding (e.g., t becomes U+100057 instead of U+0074). I think this is a problem rooted in the CUPS-PDF machinery, but I do not see how, if at all, it can be rectified. Any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have used this on a couple of different programs, and each time the pdf that is generated looks just fine. But when you select the underlying data, say in Acrobat or Reader, and paste it elsewhere, you discover boxes. Further research shows that the codepoints are being assigned the Private Use Area, and given a value FFFE3 codepoints greater than the original encoding (e.g., t becomes U+100057 instead of U+0074). I think this is a problem rooted in the CUPS-PDF machinery, but I do not see how, if at all, it can be rectified. Any suggestions?