Changes between Version 8 and Version 9 of WebKitGTKFonts


Ignore:
Timestamp:
Oct 21, 2010 4:45:06 PM (9 years ago)
Author:
mrobinson@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTKFonts

    v8 v9  
    28282. '''Remove the Pango backend''' Maintaining the Pango backend is a serious support burden and since we'll be using HarfBuzz to do layout and shaping, is very redundant. For GTK+ ports that do not want to depend on Fontconfig, there is the option of using native Win32 font selection. The WinCairo port is already using this.
    2929
    30 = Font Bugs =
     30= FreeType/Fontconfig Font Backend Bugs =
    3131A collection of font-related bugs from Bugzilla:
    3232
    3333 * [https://bugs.webkit.org/show_bug.cgi?id=26741 Share complex text support with Chromium Linux] (the switch to HarfBuzz)
    3434 * [https://bugs.webkit.org/show_bug.cgi?id=30532 Wrong font size calculated on google.com] (likely an Epiphany bug)
     35 * [https://bugs.webkit.org/show_bug.cgi?id=20783 (GTK) @font-face fonts do not have complex text support]
    3536
    3637These two may well be related. They both deal with fallback CJK fonts:
    3738 * [https://bugs.webkit.org/show_bug.cgi?id=37984 WebKit freetype backend doesn't support "locl" tables]
    3839 * [https://bugs.webkit.org/show_bug.cgi?id=26003 Has inconsistent font selection behavior compared with other GTK2 apps]
    39 
    40 These have patches pending review:
    41  * [https://bugs.webkit.org/show_bug.cgi?id=33299 CSS font-style: italic behavior]
    42  * [https://bugs.webkit.org/show_bug.cgi?id=41091 (GTK) Complex text rendering does not render custom fonts]
    43 
    44 Possibly fixed:
    45  * [https://bugs.webkit.org/show_bug.cgi?id=42400 TypeKit (web) fonts not rendered]
    46 
    4740
    4841== Pango backend bugs ==