Bug 196771 - KRunner: search in keywords of all installed locales
Summary: KRunner: search in keywords of all installed locales
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 203417 304774 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-16 17:15 UTC by LXj
Modified: 2020-10-15 19:37 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LXj 2009-06-16 17:15:18 UTC
Version:            (using KDE 4.2.4)
Installed from:    Gentoo Packages

Currently if my active locale is English, KRunner searches only through metadata in English, and if I switch to, say, Russian, it only searches in Russian metadata. There are a couple of problems with that. For instance, I forget all the time how some names are translated (I type "настройки системы" to launch System Settings, while it's actually translated as "параметры системы" -- both are valid translations, just synonims, which is by the way another problem with KRunner).

Another problem, as described in aseigo's blog post from last year http://aseigo.blogspot.com/2008/02/simple-but-amazingly-useful.html , sometimes the keywords for curtain applications may be not specified for particular locale. So searching through English keywords may get better results, but I need to switch to English locale to do so.

After all, if the user have installed particular set of locale data, he had a reason for it, right? So why limiting him to the "active" subset of installed data?
Comment 1 Jekyll Wu 2011-12-10 13:00:30 UTC
*** Bug 203417 has been marked as a duplicate of this bug. ***
Comment 2 Maarten De Meyer 2012-11-17 08:47:35 UTC
*** Bug 304774 has been marked as a duplicate of this bug. ***
Comment 3 Nick Shaforostoff 2018-12-02 16:57:02 UTC
possible fix for this bug: https://phabricator.kde.org/D16832
a workaround is to clean configuration or create a new user
Comment 4 Alexander Lohnau 2020-10-15 19:37:13 UTC
Now there are the runners are individually enabled/disabled and there has been a migration script for years to bring the config to KF5.