<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - evince can not find ü in attached PDF"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87215#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - evince can not find ü in attached PDF"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87215">bug 87215</a>
from <span class="vcard"><a class="email" href="mailto:carlosgc@gnome.org" title="Carlos Garcia Campos <carlosgc@gnome.org>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to Jason Crain from <a href="show_bug.cgi?id=87215#c6">comment #6</a>)
<span class="quote">> I suppose if I add an option to findText, I should also add a flag
> (POPPLER_FIND_IGNORE_COMBINING?) to PopplerFindFlags, for the glib front
> end's poppler_page_find_text_with_options(). It would be nice if someone
> could confirm that evince would actually use this option.</span >
I don't see a reason why someone might want to search for ü and not find a word
containing ü. So, if there are two methods in poppler core, I would change the
glib bindings to use the one correctly finding combining characters.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>