I assumed that the only code that is updating the curFont is TextPage::updateFont. If this is true, from what I understood from the code, the fonts array holds unique FontInfos, so it would be safe to compare pointers instead of FontInfos. So, is this right? If so, and you still want me to rework the patch so it compares the fonts infos instead of the pointers, I won't argue and will update the patch, but I'd appreciate an answer so I can have a better understanding of the code, Thanks
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/39890 Title: characters change when selecting text Status in Poppler: Confirmed Status in “evince” package in Ubuntu: Invalid Status in “poppler” package in Ubuntu: Triaged Bug description: I have problems with the following pdf: www.lacim.uqam.ca/~plouffe/OEIS/citations/MAS-R9821.pdf When marking text some characters change. This happens on many places in this pdf-file. To reproduce the bug just mark some random places in the pdf. In some places the text disappears. In some the characters change totally. In others the italics is removed. I use the latest update of dapper. Evince 0.5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/39890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
