Bug 277537 - File indexing works wrong with Cyrillic symbols
Summary: File indexing works wrong with Cyrillic symbols
Status: RESOLVED DUPLICATE of bug 271664
Alias: None
Product: dolphin
Classification: Applications
Component: search (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-11 11:29 UTC by Aleksey
Modified: 2011-09-29 07:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksey 2011-07-11 11:29:13 UTC
Version:           4.6 (using KDE 4.6.4) 
OS:                Linux

Desktop search results always empty is the search keyword contains Cyrillic symbols both for name search and for content search.

Also, if I make some comments to file (in Dolphin), after reopening these comments I see "?" instead of Cyrillic symbols.

The search by Latin-symbols keywords work right. The comments to files written in Latin symbols are displayed properly.

Reproducible: Always

Steps to Reproduce:
1. Make a file with text containing Cyrillic symbols/words.
2. Give strigi to index it.
3. Try the search with the keyword containing Cyrillic symbols/words.
OR
1. Enter Dolphin
2. Leave comments to file. Comments must contain Cyrillic symbols/words.
3. Reenter the comments.

Actual Results:  
Desktop search shows empty results if keyword contain Cyrillic symbols/words.
Comments to file contain "?" instead of Cyrillic symbols.

Expected Results:  
The desktop search should return results to Cyrillic symbols containing keywords.
The comments to files must contain Cyriilic symbols instead of "?"
Comment 1 Aleksey 2011-09-28 19:47:27 UTC
Still present in KDE 4.7.1
Comment 2 Sebastian Trueg 2011-09-29 07:31:01 UTC
This is a Virtuoso bug for which a patch is provided in bug 271664. Also the upcoming Virtuoso 6.1.4 fixes the problem.

*** This bug has been marked as a duplicate of bug 271664 ***