JDK-6656651 : Windows Look and Feel LCD glyph images have some differences from native applications.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-01-29
  • Updated: 2010-04-02
  • Resolved: 2008-02-14
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.
6u10 b12Fixed 7Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
The Java 2D LCD glyph rasterisation is not the same as that of the Microsoft
Cleartype rasteriser. Some of the resulting differences are observable on Vista and XP
in applications which utilise the Windows L&F.

EVALUATION This can be fixed by asking GDI to perform the rasterisation of glyphs, then caching these glyphs in the same way as now. This avoids disruption to the various 2D rendering pipelines, particularly its hardware acceleration architecture. This has been verified with software and D3D and OpenGL pipelines, and with SwingSet and Font2DTest. Verification has also included complex scripts which requires glyph positioning. Glyph advance is still obtained from the JDK rasteriser which ensures that in the cases of fractional metrics, or algorithmically styled text, we maintain metrics compatibility. For integer metrics and no algorithmic styling JDK and GDI already agree for 99.75% of all glyphs, with only some obscure cases differing likely due to rounding. Some of the benefits of this approach are behavioural and metric compatibility with the existing code.