Bug 17256 - doesn't search for Russian text in pages
Summary: doesn't search for Russian text in pages
Status: CLOSED WONTFIX
Alias: None
Product: Sisyphus
Classification: Development
Component: skipstone (show other bugs)
Version: unstable
Hardware: all Linux
: P2 major
Assignee: Nobody's working on this, feel free to take it
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-21 21:49 MSD by Ivan Zakharyaschev
Modified: 2015-08-14 10:15 MSK (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Zakharyaschev 2008-09-21 21:49:37 MSD 
skipstone-1.0.0-alt2

How to reproduce:
Open a page with Russian content, for example, http://sisyphus.ru/ . Try to search in the page for a Russian word: in menu "File" > "Найти", enter "ежедневно" and press "Найти". Result: "Expression was no found!".

Expected result: it finds this word.

It works OK for words in Latin script, say, in that page it finds successfully the word "Sisyphus".
Comment 1 Michael Shigorin 2008-09-22 12:17:18 MSD 
I don't really use this package (as already mentioned); may I respectfully suggest passing maintainership to you as obviously the more interested person?
Comment 2 Ivan Zakharyaschev 2008-09-22 23:17:51 MSD 
(In reply to comment #1)
> I don't really use this package (as already mentioned); may I respectfully suggest passing maintainership to you as obviously the more
> interested person?

After writing down the discovered bugs to this bugzilla, I don't have enough energy for fixing them or reporting upstream...
Comment 3 Michael Shigorin 2008-09-23 00:48:58 MSD 
:-(

Maybe next time?..

Anyways, it makes no real sense to accurately file tons of similar bugs after filing the "root" one on firefox since that's where these are going to be (not) fixed in the first place.  Other packages using gtkembedmoz might just get magically fixed when such bug is fixed in the engine itself.

Not this one, obviously.
Comment 4 Ivan Zakharyaschev 2008-09-23 05:12:58 MSD 
(In reply to comment #3)

> Anyways, it makes no real sense to accurately file tons of similar bugs after filing the "root" one on firefox since that's where these are
> going to be (not) fixed in the first place.  Other packages using gtkembedmoz 

It makes sense as a kind of bookkeeping: make a note that there was a problem in that particular program in that configuration; after some time, read the note and check whether it got fixed or consider fixing it. Otherwise the discovered bugs will stay forever there in the numerous packages, without an accessible method to test for them once again.

I have a slight interest in it being fixed in all browsers I occasionally use, but I don't want to keep this in my memory. So I write it down. As for the Indic text, it depends on the build options probably, so even if it is fixed in Firefox, it isn't automatically fixed in other browsers.

might just get magically fixed when such bug is fixed in the
> engine itself.
Comment 5 Michael Shigorin 2011-09-18 00:43:29 MSK 
Well, 1.0.1-alt2 @webkit didn't fix this, maybe even made things worse: Alt-I (File > Find) doesn't look like it would search for latin or numeric symbols either...
Comment 6 Michael Shigorin 2015-08-14 10:15:28 MSK 
С 2008 года сдвигов относительно skipstone-1.0.1 не произошло, рекомендую пользоваться другими легковесными браузерами (midori, qupzilla...).