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. Sverrir --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
