[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Devel] rendering bug reintroduced in freetype 2.1.7
From: |
Torgeir Veimo |
Subject: |
Re: [Devel] rendering bug reintroduced in freetype 2.1.7 |
Date: |
Thu, 05 Feb 2004 15:36:38 +0000 |
On Thu, 2004-02-05 at 00:43 +0100, Werner LEMBERG wrote:
> > Just a question; the pshinter in 2.1.5 seems to use pshalgo.c
> > allmost equal to pshalgo3.c in freetype 2.1.4. What happened to
> > pshalgo1/2.c in 2.1.4?
>
> From the ChangeLog:
>
> 2003-05-29 Werner Lemberg <address@hidden>
>
> * src/pshinter/pshalgo1.[ch], src/pshinter/pshalgo2.[ch]: Removed.
> * src/pshinter/pshalgo.h: Removed.
>
> * src/pshinter/pshalgo3.[ch]: Renamed to...
> * src/pshinter/pshalgo.[ch]: New files.
> s/PSH3/PSH/.
> s/psh3/psh/.
> s/ps3/ps/.
Here's a fix which restores the rendering as it was in 2.1.4;
--- src/pshinter/pshglob.c 2004-02-05 15:31:55.893371707 +0000
+++ src/pshinter/pshglob.c-orig 2004-02-05 15:29:16.757977331 +0000
@@ -663,7 +663,7 @@
read++;
}
- dim->stdw.count = write - dim->stdw.widths;
+ dim->stdw.count = priv->num_snap_heights;
}
/* copy blue zones */
I'm not qualified to say what is really happening here.
Simply replacing the pshglob.c file with the one from 2.1.4 also does
the trick. Note that there's a similar statement in line 647, but
changing that one doesn't affect the rendering.
--
Torgeir Veimo <address@hidden>