It was very deliberate that advances from the JDK's rasteriser was used
because many
applications were very sensitive to metrics. This was back in the T2K
days and it just
carried over to freetype. It worked out just fine with T2K but not so
much with freetype
I don't think I want to just take
Hello,
> I'm speculating here, but perhaps the issue is that glyphs are being
positioned using Freetype while the actual glyph rendering is using GDI,
and there is a disagreement between the two systems re: kerning?
> The issue does seem to be limited to the kerning between glyphs and not
the actu
Hi,
We tested this workaround for the bug
https://bugs.openjdk.java.net/browse/JDK-8217731 on windows 7 and 10 with
Java11 (Oracle JDK). It solves the ugly font problem.
Thanks a lot
Judith
Von: 2d-dev <2d-dev-boun...@openjdk.java.net> Im Auftrag von Peter Harvey
Gesendet: Sonntag, 28. April
On Sun, Apr 28, 2019 at 1:05 PM Phil Race wrote:
> One thing to add is that Swing on Windows will use LCD text in all cases I
> can think of and that is rendered by Windows/GDI not free type.
> Line and glyph spacing may still be affected (come from freetype) but not
> the glyph image itself.
> S
One thing to add is that Swing on Windows will use LCD text in all cases I can
think of and that is rendered by Windows/GDI not free type.
Line and glyph spacing may still be affected (come from freetype) but not the
glyph image itself.
So it would have to be some custom rendering in another mode
On 4/28/19, 8:25 AM, Peter Harvey wrote:
Apologies if this is not the correct channel for this email.
It is, but if you want to send any more emails to this list, you will
need to subscribe.
From what I can tell, Freetype 2.7 contained a change in hint
processing that led to poorer qualit
