https://bugs.kde.org/show_bug.cgi?id=444908

            Bug ID: 444908
           Summary: Generated accelerators in Kate end up being used in
                    characters with diacritics/accents, making them
                    impossible to activate via keyboard
           Product: frameworks-kxmlgui
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdelibs-b...@kde.org
          Reporter: herzensch...@gmail.com
  Target Milestone: ---

At the KDE Brasil l10n team we noticed that Kate would show the accelerator in
the character R in "próxima" if one directly opens the Search and Replace pane,
but the character Ó if one first opens the Power Search and Replace Bar first
(which shows up via Ctrl+F and clicking its icon) and then the Search and
Replace pane. The word "próxima" in Brazilian Portuguese, which means "next",
occurs on both areas of the UI, the pane and the bar.

The character Ó is impossible to activate in keyboards with dead keys, like
abnt2 for Brazilian Portuguese.

We have no control over these accelerators, since they're not shown in Kate's
PO files.

What seems to be happening is something like this:

* We have a word "próxima" occurring twice in the UI
* if P is taken by another word (like "Pesquisar", then the first "próxima" has
an accelerator in the second character, R
* if R is taken by the first "próxima", then the second "próxima" has an
accelerator in the third character, Ó

I'm filing this up on frameworks-kxmlgui since Kate uses that and this bug
(https://bugs.kde.org/show_bug.cgi?id=407145) is similar, but applied to
frameworks-kirigami because that's what Discover uses.

IMO, there's no issue in the fact that these accelerators are generated (as far
as I understand), the issue is that these generated accelerators can be bound
to characters with diacritics/accents, as those cannot be typed.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to