Changes between Version 5 and Version 6 of WebKitGTKFonts


Ignore:
Timestamp:
Aug 26, 2010, 2:56:35 PM (14 years ago)
Author:
Martin Robinson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WebKitGTKFonts

    v5 v6  
    1010Additionally, using HarfBuzz directly will allow us to share layout and shaping code with Chromium.
    1111
     12=== Caveats for replacing PangoCairo with HarfBuzz ===
     13{{{
    1214  (02:49:36 PM) mrobinson: Xan was saying that you mentioned something the GTK+ port does well, perhaps even better than Chromium.
    1315  (02:49:47 PM) evmar: complex text, definitely
    … …  
    2426  (02:52:05 PM) evmar: dealing with broken fonts (we had to hack around bad advances in some arabic font, i forget how it works now)
    2527  (02:52:32 PM) evmar: renormalizing text (harfbuzz expects "correct" text, i think pango knows to reorder it before giving it to harfbuzz)
     28}}}
    2629
    27303. '''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.