The cairo port of webkit renders synthetic bold/oblique fonts as normal. This is not a bug, just a lack of implementation caused when the font handling code was reorganised sometime back in June. The attached patch contains the cairo implementation for this feature
Created attachment 24211 [details] patch for synthetic font support in cairo
Simple testcase: <html> <b>赤と黒、4つのマーク、13の数字</b> <i>赤と黒、4つのマーク、13の数字</i> <b><i>赤と黒、4つのマーク、13の数字</i></b> </html>
(In reply to comment #1) > Created an attachment (id=24211) [edit] > patch for synthetic font support in cairo > Hi Alex, Please mark your patch r? if you want review. You should fix up coding style (spaces, not tabs) and include a ChangeLog entry too (exact procedure is described on webkit.org). Thanks
Created attachment 24329 [details] patch for synthetic font support with cairo
Oops, sorry about that, I've attached a better patch that conforms to the webkit guidelines.
Comment on attachment 24329 [details] patch for synthetic font support with cairo Style error: else { 63 cairo_translate(cr, point.x(), point.y()); 64 } But mitz should probably review this.
Comment on attachment 24329 [details] patch for synthetic font support with cairo WebKit prefers const values to #defines: +#define SYNTHETIC_OBLIQUE_ANGLE 14 This is what pixel tests were made for. It saddens me that gtk still doesn't have pixel tests.
Comment on attachment 24329 [details] patch for synthetic font support with cairo > + if(font->platformData().syntheticOblique()) { Need a space after the "if" here. Everything else looks OK, although the technique of drawing the text twice isn't the best known synthetic bold technique. r=me
A really great change -- works wonderfully under Windows! Landed in @r44268.
*** Bug 26120 has been marked as a duplicate of this bug. ***