> > Rogier, how do you handle this your engine?
>
> Ermmm, I ermmm, just don't, basically. I have other priorities than
> the Freetype project: buggy fonts tend to look buggy on my
> rasteriser, and I'm happy with that.
:-)
> The strategy you propose sounds good to me, though I think you
> forg
On 8/20/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>
> From: Rogier van Dalen <[EMAIL PROTECTED]>
> > FWIW: someone reported a similar problem in my TrueType loading
> > code, for another font. I was not sure this was due to a bug in my
> > code. My guess was, though I have not yet had the tim
From: Rogier van Dalen <[EMAIL PROTECTED]>
Date: Fri, 1 Jul 2005 09:17:44 +0200
> On 6/24/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>
> > Uh, oh, there is a serious bug in FreeType's TT code which
> > apparently has gone unnoticed *for years*! In ttgload.c, function
> > `compute_glyph_metric
On 6/24/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> Uh, oh, there is a serious bug in FreeType's TT code which apparently
> has gone unnoticed *for years*! In ttgload.c, function
> `compute_glyph_metrics', you can find this:
>
> /* translate array so that (0,0) is the glyph's origin */
>
George, thanks a lot for your help.
> So ftstring gives the distance between d & o as more than the
> counter, while the splines & ff's metricsview suggest it should be
> about half the counter.
Uh, oh, there is a serious bug in FreeType's TT code which apparently
has gone unnoticed *for years*!
