<AWT Dev> Status of JDK-8016255
Sergey Bylokhov
Sergey.Bylokhov at oracle.com
Sat Sep 21 18:42:23 UTC 2019
On 9/16/19 11:36 am, DRC wrote:
> OK, thanks for the update. I submitted two related issues for macOS and
> Windows. Java does not correctly handle dead keys on those platforms,
> either, but the symptoms are different. On Windows, Java produces the
> incorrect key symbol for dead keys that are activated via a modifier
> (Shift, AltGr.) On macOS, Java produces the incorrect key symbol for
> the key release of a dead key (but the key press is usually correct.)
Thank you, for these reports.
> Is it your assertion that these issues will have to be fixed by the
> community as well?
Not "have to", but since currently, nobody works on these issues, someone
can step in and propose a patch.
>
> On 9/16/19 1:18 PM, Sergey Bylokhov wrote:
>> Hello, DRC.
>>
>> It looks like this particular bug is not on the table and nobody working
>> on it right now =(
>> I encourage the community to participate.
>>
>> On 9/9/19 7:55 pm, DRC wrote:
>>> This bug:
>>> https://bugs.openjdk.java.net/browse/JDK-8016255
>>> was opened over six years ago and is still listed as "unresolved." It
>>> unfortunately affects my product. Any chance of getting a resolution or
>>> an update on its status?
>>>
>>> In a nutshell, "dead keys" (accent modifier keys) on certain
>>> international keyboards are not properly handled in Swing on Un*x
>>> systems. Only the key release event from those keys is delivered to
>>> applications, without a prior key press event.
>>>
>>> DRC
>
--
Best regards, Sergey.
More information about the awt-dev
mailing list