JDK-6869114 : Typo in the logger alias in keysym2ucs.h
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: solaris
  • CPU: generic
  • Submitted: 2009-08-06
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Description
Following line in file 
  src/solaris/classes/sun/awt/X11/keysym2ucs.h
has typo: "kye" instead of "key". That might cause a confusion when user would switch on appropriate logger:
tojava     private static Logger keyEventLog = Logger.getLogger("sun.awt.X11.kye .XKeysym");

Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014

- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014

EVALUATION It's not so obvoius: from one hand it really helps analysing logs, from the other it's a letter order change which doesn't look good in program as it increases the % of error. We decided that both "key" and "kye" variants are not excellent so we may want to name it like "key-entry" or something.
02-09-2010

EVALUATION Also, should check if that's not a typo too (there are a few other places within the file): 0x3171 #define XK_Hangul_SunkyeongeumMieum 0xef0 0x3178 #define XK_Hangul_SunkyeongeumPieub 0xef1
06-08-2009

PUBLIC COMMENTS It is not a typo but a conscious decision to take such a key (kye). It is easy to find in logs and also in the code which is rather big and full of the term "key" in it's proper sense.
06-08-2009