Bug ID: 4371923 Three keys ><* don't appear in Swing components with German keyboard

4371923 : Three keys ><* don't appear in Swing components with German keyboard

Details

Type:	Bug	Submit Date:	2000-09-18
Status:	Closed	Updated Date:	2001-07-02
Project Name:	JDK	Resolved Date:	2000-12-08
Component:	client-libs	OS:	linux,generic
Sub-Component:	java.awt	CPU:	x86,generic
Priority:	P3
Resolution:	Fixed
Affected Versions:	1.3.0
Fixed Versions:	1.3.0_03

Related Reports

Backport:	JDK-2037092 - Three keys ><* don't appear in Swing components with German keyboard
Backport:	JDK-2037093 - Three keys ><* don't appear in Swing components with German keyboard
Duplicate:	JDK-4390994 - Impossible to type a question mark (?) on Linux (red hat 7.0)
Duplicate:	JDK-4362411 - JTextField does not accept some numeric keys on Linux
Duplicate:	JDK-4393876 - JTextArea does not add characters for special key-strokes (such as '<' and '>')
Duplicate:	JDK-4387422 - Some keys not working in JTextArea for Danish keyboards(JDK 1.3RC1)
Duplicate:	JDK-4381329 - #4362411 again: JTextComp won't accept some numeric keys on Linux (French keybd)
Duplicate:	JDK-4380071 - some keys do not work with swing (Linux)
Relates:	JDK-4389057 - merlinb40 Fonts all bold in SwingSet2/not displaying properly on Linux RH: 6.1

Sub Tasks

Description


Name: rmT116609			Date: 09/18/2000


Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-b17)
Java HotSpot(TM) Client VM (build 1.3.0rc1-b17, mixed mode)

Using SuSE-Linux 7.0 with XFree 3.3.6 and Germany keyboardlayout, the keys '*',
'<' and '>' don't work with Swing-components, but work with AWT-components.

Switching to US-layout fixes the problem.

import javax.swing.*;
 
public class SwingTest {
  public static void main( String[] args ) {
    JFrame f = new JFrame();
    f.getContentPane().add( new JTextField( 40 ) );
    f.pack();
    f.show();
  }
}
(Review ID: 109704) 
======================================================================

Comments

CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
ladybird
merlin

FIXED IN:
ladybird
merlin

INTEGRATED IN:
1.3.0_03
ladybird
merlin-beta

VERIFIED IN:
1.3.0_03

2004-06-14

EVALUATION

Blackdown has a hack. 

===============================================================

The Synopsis seems to be messing up the bug query scripts, so I changed it 
from: 

'*' and '<' don't appear with German keyboard

to: 

Three keys ><* don't appear in Swing components with German keyboard 

eric.hawkes@eng 2000-10-10


When reading through the emails in the Blackdown log, I saw complaints that 
a lot of keys on a German keyboard layout don't work.  It isn't completely 
clear whether they are using a US keyboard with some kind of German layout, 
or a German keyboard.  They also mention that many keys using a French 
keyboard layout work incorrectly.  

Their proposed fix is to change code in awt_InputMethod.c  This sounds 
completely wrong to me, unless they only saw the bug when using InputMethods.  
I guess I'll need to test both cases.  

eric.hawkes@eng 2000-10-18

Please note that this bug affects Swing component ONLY; awt components work fine. I am reassigning to Swing for triage -- feel free to reassign it back to us if it turns out that we are passing in bad keycodes or some such.

Thanks.

hania.gajewska@Eng 2000-10-30
===============================================================
I have sent a mail to the submitter asking for the information
whether he is using German Key Board or US keyboard with a german 
layout.
ranjith.mandala@Eng 2000-10-31
===============================================================

When using a german keyboard with a german layout in KDE KeyListeners and InputMethodListeners are not notified of any KeyEvents for the <> or * (not the one on the numlock side of things). On the other hand, in the heavyweights the keys appear, even though KeyListener are not notified.
I have attached the test case I used. First component is a subclass of Container that has a KeyListener, second component is a subclass of Container that has a InputMethodListener, third is a TextField and fourth is a JTextField. Click in each to see the varying behavior.
Reassigning to awt for further evaluation as to why KeyListeners aren't being notified.
scott.violet@eng 2000-11-01

I added an email from calvin about this bug containing the suggested fix and a URL for the discussion about this bug to the Comments section.  
eric.hawkes@eng 2000-11-01

Put the keys in the keymap table in canvas.c
mike.bronson@eng 2000-11-06

Stopped discarding valid keycodes.
mike.bronson@eng 2000-12-18

2000-11-01

SELECT A COUNTRY/REGION
Africa Operation Argentina Australia Austria Bahrain Bangladesh Belgium & Luxembourg Belize Bhutan Bolivia Bosnia & Herzegovina Brasil Brunei Bulgaria Cambodia Canada - English Canada - French Chile China Colombia	Costa Rica Croatia Cyprus Czech Republic Denmark Ecuador Egypt Estonia Finland France Germany Greece Guatemala Honduras Hong Kong Hungary India Indonesia Iraq Ireland	Israel Italy Japan Jordan Kazakhstan Korea Kuwait Laos Latvia Lebanon Lithuania Malaysia Maldives Malta Mexico Moldova Nepal Netherlands New Zealand Nicaragua	Norway Oman Pakistan Panama Paraguay Peru Philippines Poland Portugal Puerto Rico Qatar Romania Russia Saudi Arabia Serbia & Montenegro Singapore Slovakia Slovenia South Africa Spain	Sri Lanka Sweden Switzerland -- French Switzerland -- German Taiwan Thailand Turkey Ukraine United Arab Emirates United Kingdom United States Uruguay Venezuela Vietnam Yemen

Hardware and Software, Engineered to Work Together