Name: inR10103 Date: 07/30/2003
I confirm that problem is reproducible if you select
"Lucida Sans Typewriter" if Font2DTest and set unicode range to 2500-267f
(affected glyphs are in range 2565-2666).
I also checked other software (like Microsoft Charmap and even Fontlab)
also have the problem with these glyphs because they have too big descent
(comparing to font metrics).
In fact font metrics for the font are:
family=Lucida Sans Typewriter,name=Lucida Sans Typewriter Regular,
style=plain,size=50]ascent=48, descent=11, height=59]
and bounds for one of glyphs (\u2fcf)
1) i do not see any Java2D font rendering problem here
(we do the best we can)
2) all code that rely on usage of FontMetrics may show these glyphs
Generic solution (not for this particular
font) depends on particular case - it could be either
usage of GlyphMetrics instead of FontMetrics or clipping region
outside font bounding box or something else.
If these symptoms could be observed on standard AWT/Swing components
then i suggest to file bugs against these components.
3) Font2DDemo also shows overlaps but i do not think this is bug
because it gives impression about difference of FontMetrics
and GlyphMetrics. Clipping here is not good idea because
this is just hiding symptoms (that can be important to make decisions).
Moreover, zoomed version of any glyph is clipped.
4) Generally speaking there is no obligation that all font glyphs
are fitting into font bounding box.
But because "Lucida Sans Typewriter" font is shipped with JDK and
is supposed to be used with JDK it could be nice to update
shipped fonts somehow (if it possible).
I propose to recategorize this bug to those who are responsible for fonts
shipped with jdk.