Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2420 non-English modifier keys not registered correctly by jEdit

normal bug
open
nobody
5
2014-03-24
2005-07-03
Björn Kautler
No

Some Keys, e. g. the ö, ä, ü, ... on the german keyboard
layout are not recognized correctly by jEdit if pressed
with C- or A-modifier. The Keyboardtester receives a
KEY_PRESSED, and a KEY_RELEASED, but no
KEY_TYPED.

Discussion

1 2 > >> (Page 1 of 2)
  • Björn Kautler
    Björn Kautler
    2005-07-03

    Logged In: YES
    user_id=918212

    I forgot to mention:

    My jEdit-Version: 4.2final
    My java-Version: Suns 1.5.0_03
    My operating system: Win XP Pro SP2

     
  • Brad Mace
    Brad Mace
    2006-03-21

    Logged In: YES
    user_id=370261

    This is a JVM issue which unfortunately is somewhat common
    with non-english keyboards.

     
    • status: open --> pending
     
  • Is this still a problem?

    If it looks a bug in jEdit, please report the actual log of
    Keyboard Tester.

     
  • Robert Schwenn
    Robert Schwenn
    2008-09-13

     
    Attachments
  • Robert Schwenn
    Robert Schwenn
    2008-09-13

    Not sure if this is a problem ;-) - but it's still true. I attached a log of Keyboard Tester for the keys: 0, ß, ü, ö, ä (pure and in combination with CTRL resp. ALT).

    - German Keyboard
    - Windows XP SP3
    - jEdit 4.3pre15

    File Added: Umlaut.log

     
    • status: pending --> open
     
  • Thank you for the log. It tells almost where the problem is in. But I
    want a bit more to think the way to fix. Could you please add the
    correct (expected) results for each wrong (unexpected) part in the log?

     
  • Robert Schwenn
    Robert Schwenn
    2008-09-18

    Sorry, that's out of my knowledge. All I can say is that the Keyboard Tester doesn't display anything in it's output field for the mentioned key strokes.

     
  • Damien
    Damien
    2010-11-15

    Has this been fixed? It definitely sounds like a JVM issue to me, in which case this shouldn't be listed as a jEdit bug.

     
1 2 > >> (Page 1 of 2)