26003 2009-05-24 23:57:08 -0700 Has inconsistent font selection behavior compared with other GTK2 apps 2012-02-20 14:59:25 -0800 1 1 1 Unclassified WebKit WebKitGTK 528+ (Nightly build) PC Linux RESOLVED FIXED P2 Normal --- 0 wanghz webkit-unassigned gustavo kenneth mrobinson tonikitoo xan.lopez oldest_to_newest 123013 0 wanghz 2009-05-24 23:57:08 -0700 I'm using Debian Linux (sid/unstable). Currently, Debian provides epiphany-webkit version 2.27.1-2 in sid, which uses webkitGTK+1.1.7. The problem I encountered is that epiphany-webkit has not inconsistent font selection behavior compared with other GTK2 apps when epiphany-webkit is rendering web pages containing Chinese characters. To be specific, we consider a freshly setup Debian Linux with packages ttf-arphic-uming and ttf-arphic-ukai installed. These two packages provide Chinese fonts: AR PL UMing and AR PL UKai. These packages also installed fontconfig configuration files which contain the instructions to prefer to AR PL UMing when Chinese characters are rendered through fontconfig. That is, when a typical GTK2 app needs display some Chinese characters (not covered by the system's default font DeJaVu Sans), AR PL UMing font will be selected. Such a behavior is consistent in both GTK2 and QT4 apps. But in epiphany-webkit, a GTK2 app using webkit, this behavior is no longer consistent. For example, when we open a web page, like www.google.com.hk, AR PL UKai will be used instead to render the Chinese characters. As another example, when www.xinhuanet.com is accessed, AR PL UKai is also selected instead of AR PL UMing. So, I wonder if there is a bug in webkitGTK+ so that epiphany-webkit does not fully respect fontconfig's configurations. 131422 1 32682 devans 2009-07-13 15:25:03 -0700 Created attachment 32682 Patch to fix QuickTime/X11 namespace conflict 237963 2 tonikitoo 2010-06-14 11:56:16 -0700 (In reply to comment #1) > Created an attachment (id=32682) [details] > Patch to fix QuickTime/X11 namespace conflict Also, epiphany guys cc'ed ps: patch looks unrelated and is in so bad shape (lack of commit message and explaination, lack of context, etc). 560385 3 mrobinson 2012-02-20 14:52:20 -0800 Is this still an issue? A lot has changed with font selection. If you notice some inconsistency between Chromium/Firefox and WebKitGTK+, I'd be very interested to fix it. 560388 4 mrobinson 2012-02-20 14:59:25 -0800 I see Chromium and Firefox selecting the same font that WebKitGTK+ does in the situation listed above. If this is not truly the case or there is some further issue, feel free to reopen this bug. I think it may be fixed now though. 32682 2009-07-13 15:25:03 -0700 2010-06-10 17:47:06 -0700 Patch to fix QuickTime/X11 namespace conflict patch-WebKitTools-DumpRenderTree-gtk-TestNetscapePlugin-TestNetscapePlugin.cpp.diff text/plain 702 devans LS0tIFdlYktpdFRvb2xzL0R1bXBSZW5kZXJUcmVlL2d0ay9UZXN0TmV0c2NhcGVQbHVnaW4vVGVz dE5ldHNjYXBlUGx1Z2luLmNwcC5vcmlnCTIwMDktMDctMTAgMDM6MDI6MDIuMDAwMDAwMDAwIC0w NzAwCisrKyBXZWJLaXRUb29scy9EdW1wUmVuZGVyVHJlZS9ndGsvVGVzdE5ldHNjYXBlUGx1Z2lu L1Rlc3ROZXRzY2FwZVBsdWdpbi5jcHAJMjAwOS0wNy0xMyAxMjo1OTo0MC4wMDAwMDAwMDAgLTA3 MDAKQEAgLTI2LDYgKzI2LDEzIEBACiAgKi8KIAogI2luY2x1ZGUgImNvbmZpZy5oIgorCisjZGVm aW5lIEN1cnNvciAgICAgICBRRF9DdXJzb3IKKyNkZWZpbmUgV2luZG93UHRyICAgIFFEX1dpbmRv d1B0cgorI2RlZmluZSBQaWN0dXJlICAgICAgUURfUGljdHVyZQorI2RlZmluZSBCT09MICAgICAg ICAgT1NYX0JPT0wKKyNkZWZpbmUgRXZlbnRUeXBlICAgIEhJVF9FdmVudFR5cGUKKwogI2luY2x1 ZGUgIlBsdWdpbk9iamVjdC5oIgogCiAjaW5jbHVkZSAibnBhcGkuaCIKQEAgLTM2LDYgKzQzLDEz IEBACiAjaW5jbHVkZSA8c3RkaW8uaD4KICNpbmNsdWRlIDxzdHJpbmcuaD4KICNpbmNsdWRlIDxz dGRsaWIuaD4KKworI3VuZGVmIEN1cnNvcgorI3VuZGVmIFdpbmRvd1B0cgorI3VuZGVmIFBpY3R1 cmUKKyN1bmRlZiBCT09MCisjdW5kZWYgRXZlbnRUeXBlCisKICNpbmNsdWRlIDxYMTEvWGxpYi5o PgogCiBleHRlcm4gIkMiIHsK