GNOME Bugzilla – Bug 556598
searching for two or more words upside down
Last modified: 2013-11-18 19:20:47 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/evince/+bug/282574 "On searching for two or more words, then evince doesn't find the words separated by new line in the text. Let's say that we are searching for "find next" in the text under Find next bla bla bla bla find next First occurrence of "find next" in this text will be found but second occurrence will not be found and listed since "find" and "next" are separated by a new line." Thanks,
I can confirm this also using Ubuntu 9.04 with Gnome 2.26.1 Not sure about the flagged importance of the bug. I understand it does not renders the program unusable but for me, it's the reason behind starting using Adobe Acrobat.
Created attachment 148648 [details] Test case showing that you can't search across line wraps
Confirmed still present in 9.10 (Evince 2.28.1). Test case attached above. Try and find the string "line boundaries" (sans quotes). Fails. This is more than a year old, with no comment from developers. This bug is harmful because you might not know that it happens, and you can't work around it. The bug summary is inaccurate, though
I just got bitten by this nasty bug, with Evince 3.10.0 (Ubuntu 13.10). What would it take to move from UNCONFIRMED to CONFIRMED?
I'm guessing here, but it looks like evince is relying on libpoppler to do the searching. I'm going to dig a little deeper and see if I can find where the actual searching happens - and I'm currently in libpoppler43/src/poppler/TextOutputDev.cc which has the takeText function used to return the object with findText. But I have really poor tools for this so it's taking me "forever" with vim. :-)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Fredrik Wendt, if you are interested in work on this bug, the relevant bug is https://bugs.freedesktop.org/show_bug.cgi?id=61104 *** This bug has been marked as a duplicate of bug 622160 ***
And this is what I've found: for (line = blk->lines; line; line = line->next) { I also found https://bugzilla.gnome.org/show_bug.cgi?id=408299 which I think is the underlying bug here.
(In reply to comment #7) > And this is what I've found: > for (line = blk->lines; line; line = line->next) { > > I also found https://bugzilla.gnome.org/show_bug.cgi?id=408299 which I think is > the underlying bug here. Thanks for pointing out. https://bugs.freedesktop.org/show_bug.cgi?id=11381 is the relevant bug.