The primary difference between the AndroidClock and Roboto-Thin fonts is that the new clock font defaults to variable width characters for better alignment on the lock screen.
Bug:7206207
Change-Id: I8509324510ce01d0a73ab1bb6b730b5d646a462c
Latest versions of DroidSansFallback from Monotype.
The DroidSansFallback.ttf file has some additional glyphs and
glyph fixes (including a fix for bug 6723057 and will likely fix
bug 6629748). It continues to cover Korean Hangul but does not
cover CJK Ext A (for space reasons on small system image devices).
The DroidSansFallbackFull.ttf file has the bug fixes listed and
also removes the Korean Hangul because we are now going to use
NanumGothic for Korean (NanumGothic.ttf is added in a separate
CL in the external/naver-fonts directory).
The falback_fonts.xml file has been modified to add NanumGothic.ttf
before DroidSansFallback.
Bug: 4531601
Bug: 6723057
Bug: 6629748
Change-Id: I670d33078b4a97c4eda00fc2323be187696e927a
This change adds the Roboto Thin and Thin Italic font variants, which
are accessible through, for example, Typeface.create("sans-serif-thin",
Typeface.NORMAL).
The version checked in is Roboto_1.100150 as obtained from Christian.
The other fonts in the family should probably be rev'ed as well, but
that would be a separate change.
I verified that the fonts work, that they're thin, that kerning and
ligatures work, and that the "kern" table (redundant and bulky) is
missing.
This should close bug 7173069: Integrate roboto thin to support jb mr1
time displays
Change-Id: I5c950a1843675668b83c005234b44abbe924d9fe
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
We also now send the correct broadcasts to each user.
You no longer need to be running the shell as root
to be able to create/remove users.
Also added some more man page material to the pm command, and
got rid of a bunch of showUsage() calls that now make error
messages completely buried because of how large the usage info
has become.
And the package manager now shows the user each historical broadcast
was sent to.
Change-Id: Iab42498e1352a0c023069139c80fc04d2d69ab4b
Cherry-pick Ib5dd86950156c5a438f25c289acb839206bb455a from master.
Data: label MTLmr3m with "ja" locale attribute, fallback_fonts-ja.xml removed,
as we only need a single fallback font file
Code: Add locale and variant to TextLayoutCache. Paint.java sets textLocale as
the language (for example, "ja") rather than the language/locale concatenated
(for example "ja_JP")
This checkin, along with Change-Id: Id8c91ae0be6cad8a7ef77a0cd5803676290986c1,
allows text view objects to set their locale dynamically and skia will use the
correct font for the locale.
Change-Id: Ieb60b0d7a39fcfef4f8ce90cd4f6065d33673710
Lohit-Telugu.ttf provides incorrect glyphs for U+FFBC-10007, masking
fonts later in the fallback chain that provide correct glyphs for
that range. I've temporarily demoted Lohit-Telugu in the fallback
order so that this does not happen, and appended a comment that
explains why. In the future, when we have our own Telugu font, we
can place that with the rest of the Indic fonts in the fallback list.
Bug: 6723057
Change-Id: I15fb06dcb7dd13289e226de01c36058134a1b7cb
Font files are marked with elegant or compact in attributes.
This is the data check for the code checkin with a similar title
Bug: 6649136
Change-Id: Ie246ae0cff55c1e76c0f32012a740547274e8221
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
Also show a notification when an external keyboard is connected
and does not have a keyboard layout selected yet.
Bug: 6405203
Change-Id: Id0ac6d83b3b381f8a236b2244a04c9acb203db3c
This adds the Roboto Condensed family (with the name
sans-serif-condensed, for consistency with existing family names).
Change-Id: Ied2c509ebbb2b3b8637c659e62c9a821b6941eaa
These fonts are replacements for the Lohit Devanagari/Tamil fonts.
We need to fit Devanagari onto all builds, so we only provide a single,
regular-weight font there, but Tamil is omitted for SMALLER_FONT_FOOTPRINT
builds and gets UI/non-UI and Regular/Bold weight versions. The UI versions
of the fonts are used for UI/system display, and the non-UI versions are
used only by WebView.
Bug: 6318791
Change-Id: I50ff6ec4bb428c0ac30049273f03a94de05b0c4f
- bug #5987379 Need an Arabic font with metrics "compatible" with Roboto
- use the Alt version with GSUB optimizations
Change-Id: I4d8c62cab37a7b010abab602c39899084d347fdc
Automatically choose a default value for the 'number' property
based on the characters that the key can generate.
Don't generate any character when ctrl, alt or meta is
pressed unless the behavior exactly matches the modifier keys
that are pressed.
Simplified the basic keyboard layouts taking into account the
new features.
Bug: 6110399
Change-Id: Ibc0f0b50c2dcf3f962a33ac77c24d2993b77637d
This is the latest drop (ver 1.00) of DroidNaskhShifAlt.ttf
from Monotype. Checking it in so we can see if there is any
clipping.
Bug: 5987379
Change-Id: I25697e64c1643dc4d36fe4ff6a407549c1165d60
On devices with adequate space, add MTLmr3m.ttf (Japanese) to the set
of fallback fonts. By default, DroidSansFallback (Chinese) is given
priority over MTLmr3m. If the locale is changed to Japanese, the
priority is reversed.
Bug: 6272763
Change-Id: I785a927d6dff0206aa9a670c51fdad76e219fc97
These keys are specific to Japanese hardware keyboard which can be
used by input method.
Patch ported from AOSP, with the addition of EISU and KANA mappings.
Change-Id: I647473cdd257458e3b9d134b0fc623eae946c3e0
Fallback and vendor font configuration files now describe how to
customize font setup for Han languages (Chinese, Japanese, Korean).
Bug: 5873170
Change-Id: Id27cce9a6ba2b6ce61b221342dabdd1b40962933