[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Kst Feature Freeze
From:       Hasso Tepper <hasso () kde ! org>
Date:       2005-04-14 22:25:13
Message-ID: 200504150125.13504.hasso () kde ! org
[Download RAW message or body]

George Staikos wrote:
> On Thursday 14 April 2005 11:16, Hasso Tepper wrote:
> > >   Which one specifically?  I can have a look today and change it if
> > > necessary.
> >
> > All with arrow keys at least, seems. I'm not sure it's problem in kst
> > even. There are two "Left" strings in kdelibs.po. Other one has QAccel
> > context and it appears correctly in accels config dialogs etc.
> >
> > #: common_texts.cpp:41
> > msgid "Left"
> > msgstr "Vasakul"
> >
> > #: kernel/qkeysequence.cpp:107
> > msgid ""
> > "_: QAccel\n"
> > "Left"
> > msgstr "Nool vasakule"
> >
> > But first one appears as translation of accelerators for example in
> > this same right click menu
> > (http://hasso.linux.ee/pics/kst-accel-bug.png).
>
>   I see it, and I'm stumped.  It's just a plain i18n() that gets passed
> to KPopupMenu::insertItem(). 

Plain i18n()? I think that you misunderstood. Menu entries itself are OK. I 
know how to handle these and this would be fixed with context info patch I 
posted here already. But problem is with shortcut key descriptions in the 
me same menu (which happen to be same strings in English). Look at picture 
again (http://hasso.linux.ee/pics/kst-accel-bug.png). Should be clearer 
now ;).

As far as I can see, these come from just last argument of 
KPopupMenu::insertItem(), no direct usage of i18n() in kst here. Shortcuts 
which can be changed via "Settings -> Configure shortcuts..." (entries in 
the Range menu for example) are shown correctly in menu.


-- 
Hasso Tepper
KDE Estonian Team
[prev in list] [next in list] [prev in thread] [next in thread]