Remove Android FontConfigInterface

Delete the old font management implementation based on SkFontConfigInterface, now that SkFontMgr_Android is live.

BUG=chromium:400801
R=djsollen@google.com,bungeman@google.com

Committed: https://skia.googlesource.com/skia/+/c773390eefe70d13faab147a70bd9319b9ac3afb

[tomhudson, 2014-08-06 20:09:36]

Once Ben's fix lands, this should be clean.

[bungeman-skia, 2014-08-06 20:29:43]

https://codereview.chromium.org/445143002/diff/1/src/ports/SkFontConfigInterf...
File src/ports/SkFontConfigInterface_android.cpp (left):

https://codereview.chromium.org/445143002/diff/1/src/ports/SkFontConfigInterf...
src/ports/SkFontConfigInterface_android.cpp:576: bool
SkGetFallbackFamilyNameForChar(SkUnichar uni, const char* lang, SkString* name)
{
Clank still needs this until it switches, is it safe to remove this?

[djsollen, 2014-08-07 14:03:42]

https://codereview.chromium.org/445143002/diff/1/src/ports/SkFontConfigInterf...
File src/ports/SkFontConfigInterface_android.cpp (left):

https://codereview.chromium.org/445143002/diff/1/src/ports/SkFontConfigInterf...
src/ports/SkFontConfigInterface_android.cpp:576: bool
SkGetFallbackFamilyNameForChar(SkUnichar uni, const char* lang, SkString* name)
{
On 2014/08/06 20:29:43, bungeman1 wrote:
> Clank still needs this until it switches, is it safe to remove this?

It is not safe yet, as we will need your chromium change to use the fontMgr
before we can submit this patch.

[Tom Hudson, 2014-08-11 20:10:15]

Ben's change tests out locally; it is making its way through the bots, and once
those are green we can land this in Skia.

[bungeman-skia, 2014-08-11 20:11:41]

https://codereview.chromium.org/445143002/diff/20001/src/ports/SkFontConfigIn...
File src/ports/SkFontConfigInterface_android.cpp (left):

https://codereview.chromium.org/445143002/diff/20001/src/ports/SkFontConfigIn...
src/ports/SkFontConfigInterface_android.cpp:569: void
SkUseTestFontConfigFile(const char* mainconf, const char* fallbackconf,
This and the following one (SkGetTestFontConfiguration) are still used.

[bungeman-skia, 2014-08-13 16:24:43]

The CQ bit was checked by bungeman@google.com

[bungeman-skia, 2014-08-13 16:24:44]

lgtm

[commit-bot: I haz the power, 2014-08-13 16:25:06]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/tomhudson@chromium.org/445143002/60001

[commit-bot: I haz the power, 2014-08-13 16:25:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-13 16:25:11]

Presubmit check for 445143002-60001 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit ERRORS **
Since the CL is editing public API, you must have an LGTM from one of:
('reed@chromium.org', 'reed@google.com', 'bsalomon@chromium.org',
'bsalomon@google.com', 'djsollen@chromium.org', 'djsollen@google.com')

Presubmit checks took 1.3s to calculate.

[djsollen, 2014-08-13 17:30:48]

lgtm

[bungeman-skia, 2014-08-13 17:31:26]

The CQ bit was checked by bungeman@google.com

[commit-bot: I haz the power, 2014-08-13 17:32:14]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/tomhudson@chromium.org/445143002/60001

[commit-bot: I haz the power, 2014-08-13 17:41:31]

Committed patchset #4 (60001) as c773390eefe70d13faab147a70bd9319b9ac3afb