JDK-6548743 : Fedora core 6: CharWiew display window exploded when selected certain ranges of glyphs
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86
  • Submitted: 2007-04-21
  • Updated: 2010-04-02
  • Resolved: 2007-04-24
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.
JDK 7
7Resolved
Related Reports
Duplicate :  
Description
Platforms: Fedora core 6
JDK: OpenJDK b11
test: /net/jano.sfbay/export/disk12/i18n/ws/7/j2se/test/closed/java/awt/font/CharView/CharView.java

1. Just compile and run the test CharView, with default setting
2. Click on Next Page, the application window would expand with all blank (most of time) when move to page 0100, 0200, 0400, then again from 1e00, 1f00
notice that window expanded the edge of monitor, please see the attached snapshot fedora6-b11-charview to compare with the testresult with JDK7 b11 - top is from openjdk b11, bottom is from jdk7 b11
3. for range 2000 (with Currency symbols), notice the position is pretty off from the one from jdk7 b11, snapshot is also attached (fedora6-b11-charview-currency).

This might or might not related to 6542749?

Comments
EVALUATION Same font and same symptoms as in the 6542749.
24-04-2007

EVALUATION OpenJDK does not include Lucida fonts (shipped with Sun's jdk6/7) and it is very likely that Serif is mapped to different set of physical fonts. Therefore some difference in the glyph appearance, metrics and even availability of particular glyphs is expected. However, expanding window is symtom of potential problem with metrics. It is likely that for on of glyphs advance is too large and may be this is because bug in calculation. It will be nice to get m,ore details. In particular, which physical font is involved and which glyph range.
23-04-2007