Comment #15 on issue 21149 by fangqq: Support fontconfig's flag for
embedded bitmaps.
http://code.google.com/p/chromium/issues/detail?id=21149
The embedded bitmaps usually have a higher priority to be render on Windows
GDI or
Linux fontconfig by default. In other words, if a font has bitmap strikes
at the
certain font sizes, the bitmaps will be rendered first. So, fengshenx's
patch is a
reasonable fix for this problem.
However, I do notice that there is an increasing number of CJK users who
prefer
vector fonts. If Chrome want to have a more refined control on this matter,
I suggest
adding a global setup variable, say EmbededBitmapPriority and set to True
by default.
This only requires you to change the following in the skia patch:
if (!fRec.fHasEmbeddedBitmap || EmbededBitmapPriority==false)
loadFlags |= FT_LOAD_NO_BITMAP;
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
