Use font manager for fallback on Android.

Source/platform/fonts/android/FontCacheAndroid.cpp

Index: Source/platform/fonts/android/FontCacheAndroid.cpp
diff --git a/Source/platform/fonts/android/FontCacheAndroid.cpp b/Source/platform/fonts/android/FontCacheAndroid.cpp
index 131bc27e99dc4542f317a9925af070046fe96951..8f070e8603027de4758b8e4caef8cded2df45bdd 100644
--- a/Source/platform/fonts/android/FontCacheAndroid.cpp
+++ b/Source/platform/fonts/android/FontCacheAndroid.cpp
@@ -35,8 +35,8 @@
 #include "platform/fonts/SimpleFontData.h"
 #include "platform/fonts/FontDescription.h"
 #include "platform/fonts/FontFaceCreationParams.h"
-
-#include "SkTypeface_android.h"
+#include "third_party/skia/include/core/SkTypeface.h"
+#include "third_party/skia/include/ports/SkFontMgr.h"
 
 namespace blink {
 
@@ -63,10 +63,13 @@ static AtomicString getFamilyNameForCharacter(UChar32 c, UScriptCode script)
         break;
     }
 
-    SkString skiaFamilyName;
-    if (!SkGetFallbackFamilyNameForChar(c, locale, &skiaFamilyName) || skiaFamilyName.isEmpty())
+    RefPtr<SkFontMgr> fm = adoptRef(SkFontMgr::RefDefault());
+    RefPtr<SkTypeface> typeface = adoptRef(fm->matchFamilyStyleCharacter(0, SkFontStyle(), locale, c));
+    if (!typeface)
         return emptyAtom;
 
+    SkString skiaFamilyName;
+    typeface->getFamilyName(&skiaFamilyName);
     return skiaFamilyName.c_str();

[f(malita), 2014/08/07 17:41:07]

Unrelated nit: for the sake of the next person looking at this and not spilling
their coffee, we should instantiate the AtomicString explicitly :)

[bungeman-skia, 2014/08/07 17:48:06]

OMG, yes. This is what it was doing, so I'm leaving it for now. This happens to
work because the underlying Rec in the String is just being reffed and then
unreffed here but is still owned by the typeface. So in theory this pointer is
good for as long as the typeface exists (forever, essentially). Even though this
code never should have relied on that (we certainly don't guarantee it).

I'm not really into fixing it right now because the idea that you can do
fallback using family names is wrong (even with the extra ttcindex hack) because
it isn't necessarily the case that requesting the family name from the font and
then looking that name up is going to get you the same typeface anyway
(especially with styles and such). So this all needs to change in the future in
any event to use the looked up typeface directly.

 }