Pass DOM locale to Skia in FontCache::getFontDataForCharacter

Source/core/platform/graphics/chromium/FontCacheAndroid.cpp

Index: Source/core/platform/graphics/chromium/FontCacheAndroid.cpp
diff --git a/Source/core/platform/graphics/chromium/FontCacheAndroid.cpp b/Source/core/platform/graphics/chromium/FontCacheAndroid.cpp
index 2cf212a8b0254dc17a8294798dab6ebe67f64515..d8f7e23d8141126a78ad32c7b55d2fb818d6d728 100644
--- a/Source/core/platform/graphics/chromium/FontCacheAndroid.cpp
+++ b/Source/core/platform/graphics/chromium/FontCacheAndroid.cpp
@@ -42,7 +42,8 @@ namespace WebCore {
 PassRefPtr<SimpleFontData> FontCache::getFontDataForCharacter(const Font& font, UChar32 c)
 {
     SkString skiaFamilyName;
-    if (!SkGetFallbackFamilyNameForChar(c, &skiaFamilyName) || skiaFamilyName.isEmpty())
+    if (!SkGetFallbackFamilyNameForChar(c, font.fontDescription().locale().string().ascii().data(), &skiaFamilyName)

[falken, 2013/09/25 08:11:51]

What happens if a page has -webkit-locale: '<crazy-non-ascii-text>';

I guess SkGetFallbackFamilyNameForChar can handle it OK?

[djsollen, 2013/09/25 13:20:19]

Skia uses that value to search over a list of known languages when selecting
which fallback chain to use.  It does however cache the incoming language for
efficient subsequent lookups.  It may be prudent to trim the input to a
reasonable value for a BCP-47 language identifier.  I think the spec recommends
around 42 characters.

see http://tools.ietf.org/html/bcp47#section-4.4

+        || skiaFamilyName.isEmpty())
         return 0;
     return getFontResourceData(getFontResourcePlatformData(font.fontDescription(), AtomicString(skiaFamilyName.c_str()), DoNotRetain), DoNotRetain);
 }