Not checking whether a font covers a character or not for LATIN make a lot of characters otherwise supported by a font the system. Not checking would not save any time, either for the most common case (English or Western European). In other words, checking it would not slow them down. 
Not checking whether a font covers a character or not for LATIN make a lot of
characters otherwise supported by a font
the system. Not checking would not save any time, either for the most common
case (English or Western European). In other words,
checking it would not slow them down. 


This is a regression and affects Vietnamese (when no font is specified at all).

Besides, add some more fonts to the font fallback list (4 Chinese fonts to
cover
CJK Ext. A), FreeSerif/FreeSans and Gentium/GentiumAlt to cover a
wider range of non-CJK BMP characters including Latin, Greek Cyrillic and other
less-used scripts. These fonts are not usually installed on Windows, but 'geeks'
 tend to install them and they would make a loud noise if Chrome does not make
use of them.

Note: Somehow gcl created a new issue (although I just wanted to update my CL
for issue 1385 : http://chrome-reviews.prom.corp.google.com/1385). The previous
CL was already in the branch and was ok'd by Brett. (the change since issue 1385
is adding several fonts to the list). So, I'm TBR'ing it. 

BUG=1317551
TEST=http://unicode.org/cldr/utility/list-unicodeset.jsp?a=[:Script=Latin:]
TBR=brettw


git-svn-id: dd90618784b6a4b323ea0c23a071cb1c9e6f2ac7@1242 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser,wistoch/meego-app-browser