Comment #8 on issue 9100 by [email protected]: Don't depend on msttcorefonts
http://code.google.com/p/chromium/issues/detail?id=9100
The locations of the files are hard coded into test_shell. However, there's
also a
fallback string in our WebKit port which says, "if all else fails, use this
font". If
/that/ font doesn't even exist, we end up with a NULL pointer.
What we should probably do in that case is use a magic string
("__fallback__") and
catch that magic string in SkFontHost_fontconfig, returning anything
fontconfig will
give us. Fundamentally, if we have no fonts, there's not a lot we can do:
we should
probably just disable text rendering in that case.
--
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
-~----------~----~----~----~------~----~------~--~---
