Bug 80633 - Search for non-latin symbols is'n work
Summary: Search for non-latin symbols is'n work
Status: RESOLVED DUPLICATE of bug 79860
Alias: None
Product: kmail
Classification: Applications
Component: search (show other bugs)
Version: 1.6.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-29 18:04 UTC by Dmitri Drozdov
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Drozdov 2004-04-29 18:04:53 UTC
Version:           1.6.2 (using KDE KDE 3.2.1)
Installed from:    Unlisted Binary Package
OS:          Linux

If I input any string in Russian in search form (available from Service --> Find_messages menu) there are no messages founded, even though some messages have search string undoubtedly. If I search any English text the result is true.

Some additional information:
1) This effect is not depends on Russian locale for CP1251 and KOI8R locales.
2) It seems to me, that the same effect reveal itself in the official Mandrake 10 distribution.
3) Messages are keeped in maildir format.
Comment 1 Stephan Binner 2004-06-19 11:49:38 UTC
Same as 79860? Does it work in the subject?
Comment 2 Dmitri Drozdov 2004-06-19 12:59:59 UTC
In my opinion those are the same problem. And it's reproduced in KMail 1.6.4 from KDE 3.2.3.

It's very important for the not-Latin-written community to fix this bug as soon as possible. Probably, any non-Latin texts can't be find in the message body, so usability is poor. And we can see now 42 votes.
Comment 3 Dmitri Drozdov 2004-06-19 13:01:44 UTC
Sorry, "1.6.4 from KDE 3.2.3" is mistake, true is "1.6.2 from KDE 3.2.3" 
Comment 4 ru_classic 2004-06-20 07:08:52 UTC
Yes. Search works in a subject of the messages.
As far as I remember, in Kmail 1.5 search worked. 
Comment 5 Till Adam 2004-07-13 16:19:22 UTC
Can you guys test this with current cvs, maybe? It should be fixed there.

*** This bug has been marked as a duplicate of 79860 ***
Comment 6 Dmitri Drozdov 2004-07-16 07:13:48 UTC
Please, see my comment for bug 79860.