Add new entry point that supports fallback font selection based on language.

Add new entry point that supports fallback font selection based on language.

BUG=chromium:287995
R=reed@google.com, wangxianzhu@chromium.org

Committed: https://code.google.com/p/skia/source/detail?r=11394

[reed1, 2013-09-17 15:33:48]

lgtm w/ parameter-style nit

https://codereview.chromium.org/23819067/diff/1/include/ports/SkTypeface_andr...
File include/ports/SkTypeface_android.h (right):

https://codereview.chromium.org/23819067/diff/1/include/ports/SkTypeface_andr...
include/ports/SkTypeface_android.h:39: SK_API bool
SkGetFallbackFamilyNameForChar(SkUnichar uni, const SkString& lang, SkString*
name);
usually we just use const char lang[] for input strings : no reason really to
require a string-object just for input.

[Xianzhu, 2013-09-17 16:31:55]

Thanks Derek for the fix! Actually I made a similar change yesterday and would
upload after I tested with blink today. My change also includes using an
auto-generated pseudo family name instead of the path name. Would you like to
include that part in this change, or I create another change?

A question: does fontVariant matter in the case? If yes, should we pass
SkPaintOptionsAndroid?

I'd like to continue to fix the blink side after this change rolled in chromium.

[Xianzhu, 2013-09-17 17:01:31]

Just FYI, uploaded my patch https://codereview.chromium.org/23621052.

[djsollen, 2013-09-17 17:14:17]

The font variant will always be elegant so there really isn't a need to set it. 
Additionally, the reason we isolated SkPaintOptionsAndroid is that we would like
to remove it, so the fewer callsites that use it the better.

[Xianzhu, 2013-09-17 17:39:58]

lgtm

[djsollen, 2013-09-17 18:45:06]

uploaded a new patch set that should address the comments.

[Xianzhu, 2013-09-19 16:44:37]

lgtm. Derek, would you submit this CL soon?

[djsollen, 2013-09-19 18:22:36]

Committed patchset #2 manually as r11394 (presubmit successful).