Add Android fonts to blimp engine

blimp/docs/running.md

Index: blimp/docs/running.md
diff --git a/blimp/docs/running.md b/blimp/docs/running.md
index a32b4366a27b2f2dd16c01f05dc01269e5e7d934..55765518841a1ed475b83fcad5418ebca312775a 100644
--- a/blimp/docs/running.md
+++ b/blimp/docs/running.md
@@ -95,6 +95,8 @@ also start a new shell and keep the following command running:
   compositor.
 * `--disable-cached-picture-raster`: Ensures that rasterized content is not
   destroyed before serialization.
+* `--android-fonts-location=$PATH`: Path to where the fonts are located.
+  Typically this would be `out-linux/Debug/gen/blimp/fonts`.

[Dirk Pranke, 2016/02/25 18:22:15]

Nit: I might not use "android" in the arg name for this ...

[nyquist, 2016/02/25 18:51:27]

That part isn't really up to me, but up to the CL that adds the argument:
https://codereview.chromium.org/1685053002/

So, if you look at that CL, it's specifically about forcing a linux build to use
the Android fontmanager instead of the default. I talked to the author of that
CL just now, and he wasn't really sure if it would be good to change it to
something that was not Android-specific.

Feel free to chime in on that CL if you feel otherwise though.

[Dirk Pranke, 2016/02/25 19:04:33]

It's just a nit, and I don't really have the context to be well informed or care
enough, so I'm fine with things as-is for now :)

 
 #### Typical invocation
 When the client connects to a manually specified engine instead of using the
@@ -117,6 +119,7 @@ out-linux/Debug/blimp_engine_app \
   --disable-cached-picture-raster \
   --blimp-client-token-path=/tmp/blimpengine-token \
   --user-data-dir=/tmp/blimpengine \
+  --android-fonts-location=out-linux/Debug/gen/blimp/fonts \
   --enable-logging=stderr \
   --vmodule="blimp*=1"
 ```