On Fri, Jan 16, 2009 at 9:32 AM, Sverrir Á. Berg <sver...@google.com> wrote: > I'm running these tests: > http://trac.webkit.org/export/39759/trunk/LayoutTests/fast/text/stroking-decorations.html > http://trac.webkit.org/export/39759/trunk/LayoutTests/fast/text/stroking.html > It seems that our font rendering path uses UniScribe/ScriptTextOut because > of the accent (this means that the line containing the accented character is > rendered incorrectly). For other lines on the page we use paintSkiaText and > that works fine (not using GDI because of the stroking). > These tests run fine on webkit nightly because they end up > using CGContextShowGlyphsWithAdvances which as far as I know not open > source. > Potential solutions: > * Ignore. > * Dynamically map è into è so we can use the skia rendering > (along with other similar characters that are actually in use). > * Implement complex rendering features on top of Uniscribe. > Number two seems simple enough, number three scares me.
Number 3 is the right answer. You have to implement ScriptTextOut: http://msdn.microsoft.com/en-us/library/ms776504(VS.85).aspx for Skia in the same way that skiaDrawText implements Windows' DrawText funciton. I don't think this function is that scary, but I'm not totally sure about the details. You're given all of the glyphs and positions, so hopefully it's not that hard. There might be some font fallback and edge cases that won't work or will require extra code, but the initial implementation should be reasonably straightforward. Brett --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
