diff options
| author | Raph Levien <raph@google.com> | 2012-09-12 15:53:26 -0700 |
|---|---|---|
| committer | Raph Levien <raph@google.com> | 2012-09-12 15:53:26 -0700 |
| commit | 2f5bdb06e7089c32fd1004f4757827e9a6d78bdc (patch) | |
| tree | 9ccda898d842c6cb1c31bd32eba12e7cb2153a6c /data | |
| parent | 753e1280cbc3f0006b04f67385f02e1f92019f7d (diff) | |
| download | frameworks_base-2f5bdb06e7089c32fd1004f4757827e9a6d78bdc.zip frameworks_base-2f5bdb06e7089c32fd1004f4757827e9a6d78bdc.tar.gz frameworks_base-2f5bdb06e7089c32fd1004f4757827e9a6d78bdc.tar.bz2 | |
Fix for bug 6872613 Need to revert back to a less hacky Arabic Font
Roozbeh provided an updated Arabic system UI font which does positioning
properly (using the GPOS mechanism, which is now fully supported in text
rendering), as opposed to the old workaround of using GSUB combinations.
It contains the following additional fixes:
1. Removed the new glyphs and relevant table fields created by GPOS2GSUB
2. [Kept empty glyphs for ZWSP, ZWNJ, and ZWJ]
3. Fixed a wrong GSUB substitution for Urdu Seven
4. Fixed shaping of U+06C1 HEH GOAL
5. Fixed shaping of U+06BA NOON GHUNNA
6. Removed the Rial ligature from the GSUB table
7. Tightened the Alef-Lam-Lam-Heh ligature in the GSUB table which was
getting triggered too frequently
This change just checks in the above work. I did a sanity-check
verification that Arabic text still renders reasonably in the system UI,
but did not check the above cases carefully.
Change-Id: Ie5fb9fd78d21bbfcd62b86deb327a5a2ae9321c6
Diffstat (limited to 'data')
| -rw-r--r-- | data/fonts/DroidNaskh-Regular-SystemUI.ttf | bin | 158148 -> 111520 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/data/fonts/DroidNaskh-Regular-SystemUI.ttf b/data/fonts/DroidNaskh-Regular-SystemUI.ttf Binary files differindex 2f495cf..c961de2 100644 --- a/data/fonts/DroidNaskh-Regular-SystemUI.ttf +++ b/data/fonts/DroidNaskh-Regular-SystemUI.ttf |