On Tue, 2010-03-16 at 15:49 -0700, Brent Fulgham wrote:
Recently, an update that attempted to share more Cairo-related font
code was added to the WebKit repository
(http://trac.webkit.org/changeset/55510). While this was no doubt of
great benefit to the Gtk-based ports, it had the unintended
Hi Gustavo,
On Wed, Mar 17, 2010 at 7:22 AM, Gustavo Noronha Silva g...@gnome.org wrote:
While I agree with the rest of your email, I failed to understand the
actual problem this caused. Is it because the include path for
platform/graphics/cairo is coming before the one you were using, and
-dev] Frustrations with WebKit Font Representation
Recently, an update that attempted to share more Cairo-related font
code was added to the WebKit repository
(http://trac.webkit.org/changeset/55510). While this was no doubt of
great benefit to the Gtk-based ports, it had the unintended side
effect
Recently, an update that attempted to share more Cairo-related font
code was added to the WebKit repository
(http://trac.webkit.org/changeset/55510). While this was no doubt of
great benefit to the Gtk-based ports, it had the unintended side
effect of breaking the WinCairo port, as it placed a
On Tue, Mar 16, 2010 at 3:49 PM, Brent Fulgham bfulg...@gmail.com wrote:
Has anyone else run into these kinds of issues, and might have some
suggestions for how to better approach this problem?
On the Chromium side, Brett Wilson is our master of font code.
PK
5 matches
Mail list logo
