Notes |
|
(0012753)
|
Sean McBride
|
2008-07-18 17:59
|
|
Unfortunately, 2.3.6 breaks some VTK unit tests. The reason is that freetype renders the fonts in VTK differently. The results are worse, with 'l' and 'i' looking very similar. This could be a freetype bug, or a bug in the font itself.
Werner (freetype dev) thinks: "I suspect that the font is badly hinted; it seems to miss hints (both ghost and normal) at least for the `i'. This, in combination with a not-yet fixed problem within FreeType (which sometimes displaces horizontal strokes too much vertically) probably causes the effects you can see."
We need to convert the VTK C++-ified fonts to a standard format so that Werner can debug. |
|
|
(0013515)
|
Mike Jackson
|
2008-09-18 13:08
|
|
Does 2.3.7 help any on the unit tests? The fix for bug 7705 is in 2.3.7 so moving to 2.3.7 would help this out. |
|
|
(0014441)
|
Sean McBride
|
2008-12-25 17:48
|
|
No Mike, I'm afraid 2.3.7 does not help.
Note to self: multiLineTextPython is the best test to see the problems. |
|
|
(0014442)
|
Sean McBride
|
2008-12-26 00:01
(edited on: 2009-01-02 11:58) |
|
After painstaking regression through freetype CVS, the source of the problem was committed on 2008-05-18:
* src/pshinter/pshalgo.c (ps_hints_apply): Reset scale values after
correction for pixel boundary. Without this patch, the effect can
be cumulative under certain circumstances, making glyphs taller and
taller after each call. This fixes Savannah bug #19976.
https://savannah.nongnu.org/bugs/?19976 [^]
|
|
|
(0014460)
|
Sean McBride
|
2009-01-02 12:05
|
|
I have attached to this bug the unit test results with 2.3.5 and 2.3.7. Notice how the 'i' character looks much worse in 2.3.7.
|
|
|
(0014490)
|
Sean McBride
|
2009-01-08 11:52
|
|
committed 2.3.7 (with change to pshalgo.c to restore old behaviour) a few minutes ago... |
|