JDK-4122022 : Check for incorrect use of UTF conversions
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows_95
  • CPU: x86
  • Submitted: 1998-03-23
  • Updated: 1998-06-16
  • Resolved: 1998-06-16
Related Reports
Relates :  
JDK-4117584 - TextField, TextArea setText() call core dump in Win95.
Relates :  
JDK-4103579 - JDK1.2b2(win32) TextArea and TextField do not support non-English
Description
Several bugs (specifically 4117584 and 4103579) were fixed by removing 
the UTF calls from TextComponent.cpp, etc.  There is now a question as to whether the remaining calls are used correctly.  Below is the request 
from Roger Calnan to investigate this issue.  

See bugids 4117584 and 4103579. 

> Eric,
> 
>         could you put in a P3 bug so that we don't forget to
> check on this.  Include this message and the bug number of 
> the other bug,
> 
>         Thanks,
> 
>         Roger
> Eric Hawkes wrote:
> > 
> > > > I don't understand the issue at a deep level, but it appears
> > > > to be a good fix.
> > >
> > >         ok, one last thing, does this fix indicate that we
> > > should look through the code of any other instances of the
> > > same problem?
> > >
> > 
> > The calls that we are replacing are rarely used now.  It might
> > be worthwhile to see when those calls are used elsewhere, and
> > determine whether they are being used appropriately.  BTW,
> > I believe Benjamin Renaud added the UTF calls to TextComponent.cpp,
> > (revision 1.18) so maybe he might know more about their use?
> > 
> > Eric
Comments
EVALUATION eric.hawkes@eng 1998-06-16 Almost all instances of UTFString in the awt are associated with Fonts and DragAndDrop. A file containing all instances of the string "UTFString" is attached to this report. The remaining uses of UTF functionality in the awt do not appear to be problematic. This bug is therefore closed.
11-06-2004