Bug 176135 - ability to define default shortcut sets per language
Summary: ability to define default shortcut sets per language
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.1
Platform: openSUSE Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-26 15:13 UTC by Maciej Pilichowski
Modified: 2024-09-14 16:17 UTC (History)
0 users

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 Maciej Pilichowski 2008-11-26 15:13:08 UTC
Version:            (using KDE 4.1.3)
Installed from:    SuSE RPMs

ability to define default shortcut sets per language

This is another effect of discussion about usability of layouts and national shortcuts on usability ML.

The thing is when some user from Poland picks up "Polish" as the language for KDE she/he does not longer see
print
find

but

drukuj
szukaj

But yet, she/he sees the default shortcuts as ctrl+P and ctrl+F which are not related at all to Polish labels.

So the wish is that KDE framework could be so flexible that translators could define their own national shortcut sets.

So that user from the example would see
Drukuj ctrl+D
Szukaj ctrl+S

One important note: it is not about forcing anything. It would be up to translator teams if they want to change something, like instead of ctrl+ setting just +. This is about _opportunity_ not about _obligatory_ task ("now, when we have this framework all shortcuts have to be translated").

The aim is _being able_ to fine-tune the global (US-centric) shortcuts, not messing up entire set.
Comment 1 Christoph Cullmann 2024-09-14 16:17:52 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann