JDK-5053211 : Bad glyph rendering spoils apearance of applications under Windows LAF
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 1.4.2_03
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2004-05-26
  • Updated: 2004-08-09
  • Resolved: 2004-08-09
Related Reports
Duplicate :  
JDK-4924220 - Microsoft Sans Serif (True Type) font is not rendered properly
Description
Java version: 1.4.2; 1.5.0 beta b49
Platform: Windows 2000, Windows XP

When running a Swing application that uses the Windows Look-And-Feel, a number of glyphs are poorly rendered. This draws attention to the fact that the application is not a native Windows application and makes it looks 'amateurish', in my opinion.

This is a real shame, since such huge improvements have been made to the Windows LAF in 1.4.2 and Tiger.

The glyphs affected include 'C', 'M', '8' and '9', althought this is certainly not a comprehensive list. A simple testcase is attached called 'RobTest.java' along with PNG capture of how the output looks on Windows XP under the default XP style, and the Windows 'Classic' style.

I am also attaching  couple of screen shots of my application, which is part of a Sun product under development (SunMAT). The bad 8s, 9s and Cs are particularly conspicuous.

The problem occurs on both Windows XP and Windows 2000. The output under Windows 2000 is similar/the same as the output under WinXP with 'classic' style. The problem occurs under Java 1.4.2 and 1.5.0 beta (b49).

Please, please, please can you consider committing to fix this for Tiger ?
Comments
EVALUATION Name: inR10103 Date: 05/27/2004 I believe that this problem is same as reported in the 4924220. I will recheck that default font used by Windows L&F is Microsoft Sans Serif and if so than close this one as duplicate. ====================================================================== ###@###.### 2004-05-28 If the above is true, and this bug is closed as a duplicate of 4924220, then please can you give serious consideration to committing to fix 4924220, particularly since 4924220 seems to have been open for over 8 *months* now without any sign of action ? The description of 4924220 makes it sound like this is nothing more than an obscure problem with a seldom-used platform specific font. In reality, it's an in-your-face problem with pretty much every application that uses Windows LAF. It's even visible in the Java Control Panel app in tiger beta 2.
13-08-2004