Add Android fonts to blimp engine

Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929
Committed: https://crrev.com/b4fd57023ade2863e463d3380456968dca6c8bcf
Cr-Commit-Position: refs/heads/master@{#380022}

[nyquist, 2016-03-08 22:16:13]

Description was changed from

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

BUG=585668, 588929
==========

to

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929
==========

[nyquist, 2016-03-08 22:17:40]

nyquist@chromium.org changed reviewers:
+ dpranke@chromium.org, dtrainor@chromium.org, klobag@chromium.org,
maniscalco@chromium.org

[nyquist, 2016-03-08 22:17:41]

dpranke: DEPS and GCS integration
maniscalco: //blimp/README.md, //blimp/docs, //blimp/engine, //blimp/tools
dtrainor: //third_party/blimp_fonts
klobag: //third_party OWNERS

[David Trainor- moved to gerrit, 2016-03-08 22:26:16]

lgtm

[nyquist, 2016-03-08 22:32:55]

The CQ bit was checked by nyquist@chromium.org to run a CQ dry run

[maniscalco, 2016-03-08 22:33:21]

lgtm

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md
File blimp/docs/fonts.md (right):

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md#new...
blimp/docs/fonts.md:20: upload_to_google_storage.py --archive -b chromium-fonts
font_bundle
Neat.  Even simpler now.

[commit-bot: I haz the power, 2016-03-08 22:33:31]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1776133002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1776133002/20001

[Dirk Pranke, 2016-03-08 22:38:32]

lgtm w/ a couple of minor questions.

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/container.md
File blimp/docs/container.md (right):

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/container.md...
blimp/docs/container.md:46: --build-dir out-chromeos/Debug \
I thought we got rid of the chromeos part?

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md
File blimp/docs/fonts.md (right):

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md#new...
blimp/docs/fonts.md:6: 1.  Copy the necessary files to
`//third_party/blimp_fonts/font_bundle`.
it would be nice if we could script this step or something to be less manual.

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md#new...
blimp/docs/fonts.md:20: upload_to_google_storage.py --archive -b chromium-fonts
font_bundle
On 2016/03/08 22:33:21, maniscalco wrote:
> Neat.  Even simpler now.

Agreed. I was mostly concerned that the upload/download scripts might not
support archive/extract and I didn't want you to roll your own. 

Given that they do, I agree that just versioning the archives is fine and
probably the right tradeoff.

[nyquist, 2016-03-08 22:56:14]

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/container.md
File blimp/docs/container.md (right):

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/container.md...
blimp/docs/container.md:46: --build-dir out-chromeos/Debug \
On 2016/03/08 22:38:32, Dirk Pranke wrote:
> I thought we got rid of the chromeos part?

You're right! My bad. Fixed! :-)

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md
File blimp/docs/fonts.md (right):

https://codereview.chromium.org/1776133002/diff/20001/blimp/docs/fonts.md#new...
blimp/docs/fonts.md:6: 1.  Copy the necessary files to
`//third_party/blimp_fonts/font_bundle`.
On 2016/03/08 22:38:32, Dirk Pranke wrote:
> it would be nice if we could script this step or something to be less manual.

I agree that it would be nice. However, the repositories contain a bunch of
files that we do not want usually such as irrelevant build-files, etc., so I'm
not sure if I'd be able to do that in an effective way.

In addition to containing unnecessary files, the repositories we are pulling
from have widely varied directory structures. Some have fonts at the top level,
others in a subfolder somewhere, and others again in several subfolders. See the
README.chromium for details by the way.

Sorry about that :-(

[nyquist, 2016-03-08 23:30:37]

The CQ bit was checked by nyquist@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-08 23:31:59]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1776133002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1776133002/40001

[klobag.chromium, 2016-03-09 00:30:19]

lgtm

[commit-bot: I haz the power, 2016-03-09 01:32:16]

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

[commit-bot: I haz the power, 2016-03-09 01:32:17]

Dry run: This issue passed the CQ dry run.

[nyquist, 2016-03-09 01:34:46]

The CQ bit was checked by nyquist@chromium.org

[nyquist, 2016-03-09 01:34:47]

The patchset sent to the CQ was uploaded after l-g-t-m from
dpranke@chromium.org, dtrainor@chromium.org, maniscalco@chromium.org
Link to the patchset: https://codereview.chromium.org/1776133002/#ps40001
(title: "Removed references to chromeos")

[commit-bot: I haz the power, 2016-03-09 01:35:18]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1776133002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1776133002/40001

[commit-bot: I haz the power, 2016-03-09 01:42:25]

Description was changed from

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929
==========

to

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929
==========

[commit-bot: I haz the power, 2016-03-09 01:42:27]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-03-09 01:43:34]

Description was changed from

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929
==========

to

==========
Add Android fonts to blimp engine

The blimp engine is currently using Linux fonts, which works well
for Linux clients. However, for Android clients, Skia should be
instructed to use Android fonts instead to ensure that the font
rendering works correctly.

This CL adds a starting set of fonts to be used, ensures that they
are part of the engine bundle, and provides documentation for how
to use them in locally hosted engines and also for how to keep the
fonts up to date.

This also updates the engine manifest and starts loading a new
dynamic library while running the engine plus fixes the documentation
for running the engine as a container.

Initial CL: https://codereview.chromium.org/1735783002/
Revert: https://codereview.chromium.org/1772343003/

BUG=585668, 588929

Committed: https://crrev.com/b4fd57023ade2863e463d3380456968dca6c8bcf
Cr-Commit-Position: refs/heads/master@{#380022}
==========

[commit-bot: I haz the power, 2016-03-09 01:43:35]

Patchset 3 (id:??) landed as
https://crrev.com/b4fd57023ade2863e463d3380456968dca6c8bcf
Cr-Commit-Position: refs/heads/master@{#380022}