Name: joT67522 Date: 01/12/98


With components like the java.awt.TextField, there is no problem
to use the Sun's COMPOSE key to enter any iso8859-1 character
into such a java.awt.TextField (proably because the native motif
components handled this transparently for the awt library
somewhere in the inside).

With the adoption of the java.swing classes, the COMPOSE key
processing doesn't work for *all* swing UI components (plus things
like java.awt.Frame and java.awt.Pane, where COMPOSE key
processing doesn't work, too) !!

This happens for example with a simple frame just containing a
java.swing.JTextField - you can only enter those iso8859-1
characters ``directly'' present on your keyboard (i.e. in the US
just the 7-bit ASCII subset, in Germany - with a german
keyboard - perhaps also half a dozen or so german special
characters like äöüß...)

I think, the solaris awt library should use something like
XLookupString (with a passed-in XComposeStatus pointer)
before sending KeyEvents to the java event queue, so that
COMPOSE key processing is enabled for the AWT and Swing!
(Review ID: 23187)
======================================================================