Version: 0.12.2 (compiled from svn) (using KDE KDE 3.5.4) Installed from: Gentoo Packages Compiler: gcc v3.4.6 OS: Linux Searching by any non-english search keywords (russian in my case) in the query in history plugin's search does not work. It just does not show anything but looking at the history itself I can see my keywords there. Search by plain english keywords works fine. PS: my system's native russian encoding is cp1251 while history seems to be stored in utf-8. I'm not sure that this is the case but maybe some kind of codepage detection/conversion should be done on the keywords?
Same problem, different language. (kopete-3.5.5) kopete displays õ ä ö ü OK, but I can not search any words with those letters.
*** Bug 130852 has been marked as a duplicate of this bug. ***
I can't reproduce this with greek in KDE 4.0.99. Searching greek strings in history works fine.
I can't reproduce this with german in KDE 4.1 RC1. Testet with several keywords containing german "umlaute" like äöü. Worked perfectly.
Still doesn't work for me in Kopete 0.60.2, KDE4.1.2. I'm not sure if it's relevant but my system is set up in ru_RU.cp1251 codepage, and Kopete's logs are in UTF8, maybe this difference in encodings causes these problems?
Tested on Kopete 0.80.2 (KDE SC 4.3.4) with words containing special letters (éèàç) and it worked fine. Do you still encounter the problem?
Waiting for feedback
Ive made some tests and discovered even more interesting things, Kopete 0.80.2 (KDE SC 4.3.4) ICQ Protocol: (Windows-1251 as default encoding in protocol settings) - bug still alive as described here - can find English words but cant find anything in Russian Jabber Protocol: cant find anything at all!! search simply doesn't work So it is somehow protocol-dependent. This is kind of funny because it seems all history stored in UTF-8 not dependent on protocol settings.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!