Changes between Version 8 and Version 9 of WebKitGTKFonts

Timestamp:

Oct 21, 2010, 4:45:06 PM (14 years ago)

Author:

Martin Robinson

Comment:

--

WebKitGTKFonts

@@ -28 +28 @@
 2. '''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.
 
-= Font Bugs =
+= FreeType/Fontconfig Font Backend Bugs =
 A collection of font-related bugs from Bugzilla:
 
  * [https://bugs.webkit.org/show_bug.cgi?id=26741 Share complex text support with Chromium Linux] (the switch to HarfBuzz)
  * [https://bugs.webkit.org/show_bug.cgi?id=30532 Wrong font size calculated on google.com] (likely an Epiphany bug)
+ * [https://bugs.webkit.org/show_bug.cgi?id=20783 (GTK) @font-face fonts do not have complex text support]
 
 These two may well be related. They both deal with fallback CJK fonts:
  * [https://bugs.webkit.org/show_bug.cgi?id=37984 WebKit freetype backend doesn't support "locl" tables]
  * [https://bugs.webkit.org/show_bug.cgi?id=26003 Has inconsistent font selection behavior compared with other GTK2 apps]
-
-These have patches pending review:
- * [https://bugs.webkit.org/show_bug.cgi?id=33299 CSS font-style: italic behavior]
- * [https://bugs.webkit.org/show_bug.cgi?id=41091 (GTK) Complex text rendering does not render custom fonts]
-
-Possibly fixed:
- * [https://bugs.webkit.org/show_bug.cgi?id=42400 TypeKit (web) fonts not rendered]
-
 
 == Pango backend bugs ==