Fixing i18n + global shortcuts

David Faure faure at
Tue Mar 4 15:13:25 GMT 2008

On Tuesday 04 March 2008, Thiago Macieira wrote:
> On Tuesday 04 March 2008 14:46:24 Lubos Lunak wrote:
> >  I don't see any need to store i18n-ed shortcut names in the config or in
> > the kded module if kcmkeys is changed back to some #include-like solution
> > for a list of shortcuts that should be configurable there. In the thread
> > about this about a month ago ('Global shortcuts and i18n') I don't see any
> > comments from you on this though - what's your position on that?
> I'd just like to make a note:
> kwin is almost unusable right now because of i18n'ed global shortcut names. 
> The shortcuts are assigned to the English version of the names, but kwin acts 
> on the Portuguese translation in my system. I don't know what the issue is or 
> if it's just a config issue.
> In any case, please make sure that you do not write i18n names to the config 
> files. Ever.

That's what Andreas' patch fixes.

Lubos' question is more about: do we want to use the kded module for the kcm
(and then it needs to know the translated texts of the shortcuts too), or do
we want to go back to some #include-like solution
(which I find ugly and unflexible, personally).

David Faure, faure at, sponsored by Trolltech to work on KDE,
Konqueror (, and KOffice (

More information about the kde-core-devel mailing list