>> One extra lookup per glyph might be enough to explain the difference. >> We need to look up the glyph to get a skyline, but maybe could cache >> its index into the font in the stencil. > > That does not sound very useful since we still would do the lookup > once per stencil rather than once per m and once per f. > > It _is_ annoying that this job is not done efficiently by the > Freetype library.
I don't follow. What exactly is annoying? Please explain. > Is it possible that the Freetype library on Windows imprudently > accesses (and possibly creates on the fly) some Truetype versions or > conversions of the fonts for getting the outlines? Nope. FreeType uses exactly the same code on both platforms, and it never converts fonts on the fly. > That might also explain > <URL:http://code.google.com/p/lilypond/issues/detail?id=2657>, the > still unresolved Issue 2657: font kerning on Windows is broken Certainly not. This is not a FreeType problem, since kerning and the like is handled one level above FreeType. I've specifically added Behdad's reply to the tracker who is willing to help the issue. However, this needs someone using the Windows platform and the ability to compile code... Werner _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
