[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] implementing detection of hinting/rasterization errors in
From: |
Hin-Tak Leung |
Subject: |
Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts |
Date: |
Sat, 2 Jul 2016 14:56:19 +0000 (UTC) |
I found that bit of code inside Compute_Func when I was looking for other
examples of manipulating
those same variables to simplify my error detection code inside Direct_Move .
It is another case of
"Oh, you already did it, silently, years ago!".
I imagine many of the remaining errors (still nearly 60 to go!) are simply
silently
worked around also.
--------------------------------------------
On Sat, 2/7/16, Hin-Tak Leung <address@hidden> wrote:
<snipped>
...
/* at small sizes, F_dot_P can become too
small, resulting */
/* in overflows and `spikes' in a number of
glyphs like `w'. */
if ( FT_ABS( exc->F_dot_P ) < 0x400L )
exc->F_dot_P = 0x4000L;
...
That was in the initial freetype2 commit!
commit d2b1f357049f6b5e6766af9f3dfa134d2527feec
Author: David Turner <address@hidden>
Date: Thu Dec 16 23:11:37 1999 +0000
Initial revision
<snipped>
- [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/01
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/02
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts,
Hin-Tak Leung <=
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/02
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/03
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/03
- Re: [ft-devel] implementing detection of hinting/rasterization errors in fonts, Hin-Tak Leung, 2016/07/03