GNOME Bugzilla – Bug 133887
searching backwards highlights wrong text in files with non-ascii characters
Last modified: 2004-12-22 21:47:04 UTC
The wrong allocation, the found text
Created attachment 24231 [details] The wrong allocation, the found text
I'm changing the description to something IMHO clearer feel free to point out if I misunderstood your report. Beside can you tell us which version of gedit and gtksourceview are you running? I see that you chose GNOMEVER2.5 but the screenshot does look like a slightly older version. I'm also moving this bug to gtksourceview since it's where the search code is.
gtksourceview-0.8
hmmm... are you able to reproduce it using "case sensitive" search?
sory bad english, automatic translation. I shall check up, the result will be tomorrow.
The mistake repeats only by search not an English word. Only by return search and switched - off option Case Sensitive.
gtksourceview-0.8.0 (pkgconfig)
I can confirm this bug. It happens searching backwards on files with certain UTF-8 characters. I still can't figure out exactly what triggers this. But it can be easily reproduced: open yelp.desktop for example and search backwards for "Name". Changing the summary for clarity. Searching forward works fine. Case sensitive forward and backward searches work fine too.
Removed the TARGET2.6.0 keyword- that's a totally cross-gnome showstopper keyword. Paolo, if you want to get a target milestone added for just gtksourceview, please email bugmaster@gnome.org and we can do it. [I already did it for gedit and moved some bugs there.]
Fixed in CVS. But at the same time found #135163 (sigh).