<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - evince can not find ü in attached PDF" href="https://bugs.freedesktop.org/show_bug.cgi?id=87215#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - evince can not find ü in attached PDF" href="https://bugs.freedesktop.org/show_bug.cgi?id=87215">bug 87215</a> from <a class="email" href="mailto:jason@aquaticape.us" title="Jason Crain <jason@aquaticape.us>"> Jason Crain</a> <pre>(In reply to Nelson Benitez from <a href="show_bug.cgi?id=87215#c13">comment #13</a>) > Hi Jason, thank you very much for the patch, btw, today I was reading this > pdf: > > <a href="http://www.compsci.hunter.cuny.edu/~sweiss/course_materials/csci493.70/">http://www.compsci.hunter.cuny.edu/~sweiss/course_materials/csci493.70/</a> > lecture_notes/GTK_textview.pdf > > and noticed that lot of words with double f, like 'buffer', are not > found[1] when searching for it, also when copied to gedit it shows the > unicode not found glyph inplace of the 'ff' in the word. > > So, is your patch covering this double f case? No, it does not fix that. That file has a different problem and I don't see a way of fixing it. The PDF creator would need to add some extra information before we could guess that character code 27 should be a double f.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>