GNOME Bugzilla – Bug 337593
move glyph extents code (and cache) from pangocairo-*font.c into pangocairo-font.c
Last modified: 2007-06-10 00:52:54 UTC
The glyph extents code is cairo-backend agnostic. It should be moved into pangocairo-font.c. The code in pangocairo-fcfont is the reference code, with bug fixes and performance boosts, while the used-to-be-copies in win32 and atsui backends are just rotting. For the record, I just made some rounding fix in pangocairo-fcfont.c, explained in https://bugs.freedesktop.org/show_bug.cgi?id=5200
Can I add a object of the struct GlyphExtentsCacheEntry in the struct PangoCairoFont?
No, the PangoCairoFont struct doesn't really exist. I've got the patch for this.
oh, I am writing the patch for this bug now. :)
2007-06-09 Behdad Esfahbod <behdad@gnome.org> Bug 337593 – move glyph extents code (and cache) from pangocairo-*font.c into pangocairo-font.c * pango/pangocairo-fontmap.c: * pango/pangocairo-fcfontmap.c: Remove per-fontmap renderer. We've not been using it for a while and there is no reason to use it. * pango/pangocairo-font.c * pango/pangocairo-fcfont.c: Most most code (including glyph extents caching) from fcfont.c to font.c. Simplifies individual backends a lot. ATSUI and Win32 cairo backends should adapt. * pango/pangocairo-render.c * pango/pangocairo-private.h: Update to reflect above changes.
Created attachment 89667 [details] [review] committed patch