summaryrefslogtreecommitdiffstats
path: root/data
diff options
context:
space:
mode:
authorRaph Levien <raph@google.com>2012-06-08 10:17:23 -0700
committerRaph Levien <raph@google.com>2012-06-08 10:17:23 -0700
commit13f6e7c819e201db0311e3d9394ff7b33efb748b (patch)
tree77e03dcbafeaa8a7744c5d43b68bc5bbbc613c1e /data
parentda741b4f2437458394a05421c50b7f11995181fa (diff)
downloadframeworks_base-13f6e7c819e201db0311e3d9394ff7b33efb748b.zip
frameworks_base-13f6e7c819e201db0311e3d9394ff7b33efb748b.tar.gz
frameworks_base-13f6e7c819e201db0311e3d9394ff7b33efb748b.tar.bz2
Workaround for bug 6609605: Hindi rendering regression in WebView
This patch changes the font data so that all anchor points are in absolute coordinates, rather than relative to outline points. With the workaround, we don't trigger the bug in the HarfBuzz/Skia integration that causes incorrect outline point data to be read. The font was prepared with FontForge. There's some risk of other problems, but I tested the font fairly carefully and it looks fine. (With a version prepared in TTX, the substitution of the different width forms of the ivowelsigndeva got broken, likely due to a TTX bug, as this seems to happen with roundtrip of unedited original). Change-Id: I3f6fffce91c3ea0695e6005b051bcf4e9b6f6361
Diffstat (limited to 'data')
-rw-r--r--data/fonts/DroidSansDevanagari-Regular.ttfbin123804 -> 123372 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/data/fonts/DroidSansDevanagari-Regular.ttf b/data/fonts/DroidSansDevanagari-Regular.ttf
index 45e15e6..a25e0e3 100644
--- a/data/fonts/DroidSansDevanagari-Regular.ttf
+++ b/data/fonts/DroidSansDevanagari-Regular.ttf
Binary files differ