Font data for Phags-pa, Runic, Samaritan, and Tagalog are added, as
well as two new styles for Syriac (Estrangela was already included,
Eastern and Western are added).
Bug: 29535549
Bug: 32046261
Test: manual (new characters are now displayed) and 'make fontchain_lint'
Change-Id: Iad08286392850caf92e374818bd29d06b6a87e52
Droid Sans Fallback is now completely replaced by Noto Sans CJK. The
font files are kept in the tree, since the SDK still needs them.
Also, Android.mk is updated to reflect the fact that Noto Color Emoji
is now included in SMALLER_FONT_FOOTPRINT, so fontchain_lint checks
for emoji consistency in that footprint too.
Bug: 31854008
Test: make fontchain_lint
Change-Id: I4f57114a48ecfaee87b49f01f7ef4fa5cd0b19fb
If the language tag "und-Zsym" is applied to a TextView, the default
presentation should be text-style. However, it didn't work before this
patch, due to a lack of "und-Zsym" language tag in fonts.xml.
Bug: 31297127
Change-Id: Ieed8fe1532806dd1e75c58aa0d7a724bfeed7796
fontchain_lint scans directories in $(TARGET_OUT). There is no better
target working as dependency than the system.img.
Change-Id: I560b89f697e5ebd4f1e44a150f5af37996cf427e
This re-enables the emoji font tests, but doesn't run the tests if
SMALLER_FONT_FOOTPRINT is set.
Additionally, we test that there's one and only one emoji font in the
fallback chain.
Bug: 26187231
Bug: 27785690
Change-Id: I2e6d467e3f54ee3d41737170d7c2492a0f6b30f0
1. Check that all emoji characters are supported in emoji fonts.
2. Check that no default-emoji characters are included in any font
that can get a higher score then the color emoji font, either by
being before it or by having a language/script assigned.
Bug: 26187231
Change-Id: Ic76bf59f1c6f9d2d290b1b64128d725ae08dcb5c
Various tests have been added:
1. Availability of hyphens: Make sure that every font used for
rendering a language that is automatically hyphenated includes either
of Unicode hyphen characters U+2010 HYPHEN or U+002D HYPHEN-MINUS.
2. Range of values: Make sure that styles, weights, and styles belong
to certain limited sets.
Bug: 26187231
Bug: 21570828
Bug: 21815394
Change-Id: Ia63d63cc8da4f2d6bc81fe5619ccac6cfcd9a54e
Add various ISO 15924 codes to fonts.xml, as a signal for better
font selection in Minikin.
Bug: 27582800
Bug: 26187231
Change-Id: Ie06c156e0179e79c15cf2d66d577c3d36571860d
The font was mistakenly removed in
Ib69e73a6682d7eedd7b824f1dadc79cbccf07605, while it is still built
for SMALLER_FONT_FOOTPRINT devices.
Change-Id: Icb62ef6ef7445255191c70110a2b5eb4105628ce
These two fonts are no longer installed on a device.
This leaves the fonts themselves in place for the sdk build.
Change-Id: Ib69e73a6682d7eedd7b824f1dadc79cbccf07605
There are two reasons for this. First, the name 'ttcIndex' is over
specific, there are many indexed font containers in addition to ttc,
such as fon, pfr, bdf, and dfont. There may be others in the future.
Second, Skia implemented this attribute with the name 'index' quite
some time ago. By naming this attribute 'index' even existing apps will
be able to use this attribute (including Chrome).
BUG: 10861108
Change-Id: I68d2b69fad304d93313f96bf3365af71906dfe69
This is needed by Minikin to choose the best font when text and emoji
variation selectors are used.
BUG=11256006
Change-Id: I5774fdf0190dcc42ec827ef5dcec8cdbd28ee925
They were no longer in use by frameworks. They were never part of a
public API and were kept in the system just in case a legacy app read
them. They had also been deprecated for three releases, which should
have given everybody enough time to switch.
Bug: 21785593
Change-Id: Ib80bcea92e45b608388455ef576bbfde647f77db
This is a temporary font profile to get razor and razorg (Nexus 7,
2013 version). It's not tested thoroughly, and should not be used for
any other devices.
The CONSTRAINED profile removes Bamum, Lisu, Mandaic, Mongolian, New
Tai Lue, Syriac, Tibetan, and Vai fonts from razor[g] devices, and
switches the CJK fonts to the limited pre-Lollipop fonts.
Bug: 22929087
Change-Id: I58c1693ee45e54b429013029d236617834446811
Previously, the inconsistency resulted in test in the testUniformY in
frameworks/base/graphics/tests/graphicstests/src/android/graphics/TypefaceTest.java
fail. The tests assume the different sans/serif/mono styles share a
consistent ascent and descent.
The font is modified using the following Python script:
from fontTools import ttLib
font_file = 'DroidSansMono.ttf'
font = ttLib.TTFont(font_file)
font['hhea'].ascent = 1900
font['hhea'].descent = -500
font.save('touched/'+font_file)
Bug: 19791102
Change-Id: I2fcd44b952691deeeed18f30d06bc9f6d5e4a8de
This is now possible since we have less space restrictions on
devices.
This helps make sure that devices don't mistakenly ship with a
limited font support simply because they didn't turn on the extended
font profile.
Although the larger version of Droid Sans Fallback is no longer used
in any font profile for a device, it is kept since it's used by the
SDK.
The Nanum Gothic font is no longer used in any device profile either,
but it's kept in the fallback chain, so the SDK (that uses it)
continues to work.
Bug: 19668057
Change-Id: I6e32c4c98745e9b6aff6684d993943a19aebf6f7
This makes sure that symbol characters who have both an alternative
or "full-width" version in the CJK fonts and a more regular version
in the symbols font get the default or "half-width" version by
default in non-CJK locales.
This is not a complete fix: such "full-width" symbol characters only
exist in the Simplfied Chinese font for now, which means in
Traditional Chinese, Japanese, and Korean locales, they characters
would now appear "half-width", which *may* be sub-optimal. The
complete fix would make sure the ones that actually need to be
"full-width" in TC/J/K are also included in the TC/J/K font.
Bug: 21525318
Bug: 21525012
Bug: 21524421
Bug: 21521330
Bug: 21520316
Bug: 21518544
Bug: 21517912
Bug: 21503807
Bug: 21502245
Bug: 21501669
Bug: 21525905
Bug: 21524018
Bug: 21503952
Bug: 21502678
Change-Id: I93cf7119b45ed3c080cd39d631a687e0ef9fd8ce
The latest files from the upstream Noto repository are named
NotoNaskhArabic* instead of the previous NotoNaskh*.
Also, Noto Sans Tibetan is now included in the fallback chain. Apart
from supporting Tibetan and Dzongkha langauges, this adds a character
(U+0FD6) that completes coverage for ARIB character sets.
Bug: 13680438
Bug: 18181755
Bug: 18639453
Bug: 19390244
Change-Id: I09b493340d1453ef61b08c841e1731119d645822
This clarifies the meaning of the variable, that this switch only
affects the Noto Sans Japanese font.
Change-Id: I28043ed41ec51af0273a071692426d51352ef849
Noto fonts for Bamum, Lisu (Fraser), Mandaic, Mongolian, New Tai Lue,
Syriac (Estrangela), and Vai scripts are added to the fallback chain.
Bug: 19390244
Bug: 18639453
Change-Id: If18a7ea245f3b15baa9fb4f53855ae64759f921b
They are now moved to external/roboto-fonts. Symlinks from deprecated
fonts to Roboto for compatibility reasons are still created here.
Change-Id: I9e1b88a4289d055ea187e241d6514f0b37c5ee1b
This is to make sure the East Asian punctuation shared between CJK languages
and Tai Le are rendered from the CJK fonts when no language is specified
for the text, or CJK text is rendered in a non-CJK locale.
Also remove the old comment about 64k glyphs limit.
Bug: 19355391
Change-Id: Ic2cbc79cecf9539ace8a432f373685eeff81e106
Fonts for Cham, Coptic, Glagolitic, Kayah Li, Tai Le, Tai Tham, Tai
Viet, and Tifinagh scripts are added to the fallback chain.
This would enable or improve display of texts in Berber languages,
Cham, Church Slavonic, Coptic, Kayah languages, Khün, Northern Thai,
Tai Dam, Tai Dón, Tai Lü, Tai Nüa, and Thai Song.
Bug: 17686019
Change-Id: I689393bc03f3957e1025ac08ab31961a6c6bc24d
This adds Lohit Odia (Oriya) font as the default font for the Oriya
script to the fallback chain.
Bug: 17686019
Change-Id: If0c60a0f35a029c3761b8ea26a2546ca5c5fa0c0
Sets up Courier and Courier New to point to Cutive Mono, since
Courier is a serif monospace font.
BUG: 17666124
Change-Id: I96bb2ff59020edd8210c253752f76f0eb5100e18
Parse new fonts.xml config file, and resolve weight selection based on
the base weight of the font (as defined by a weight alias specified in
the config file) and the requested bold flag. This change improves the
appearance of bold spans for alternate weights of Roboto.
In addition, this patch enables weight selection for fallback fonts.
For example, if an additional font with a weight of 100 is added to the
Hebrew font family in the fallback list, then requesting
"sans-serif-thin" would select that font for Hebrew text.
Bug: 14538154
Change-Id: I99a04fad4f7bf01c75726e760d42735dd9003496
The fonts are passed through Noto's identity subsetter at
https://code.google.com/p/noto/source/browse/nototools/subset.py?r=bdd10822706b
which keeps the same functionality, but compresses tables, removes
unreachable glyphs, converts post table to version 3.0, etc.
Additionally, the DroidSansFallback fonts and MotoyaLMaru are passed through
fontcrunch.
The build footprint of the non-extended font profile is reduced by 546KB.
Bug: 15348046
Change-Id: I66777a0efeb98da6007091548a6ee847ecb4ea1f
This patch actually copies the new font config file to the /system/etc
directory on the device, where frameworks and apps will be able to read
it.
Bug: 14538154
Change-Id: I53a932210763b718f469d80cc92816edf4e5b14e
This adds a new configration file for fonts with several more features,
most notably the ability to specify numeric weights for fonts in a
family, and specify aliases for weights. This will help help choose an
appropriate font for a "bold" weight request, rather than just applying
auto-bolding.
Bug: 14538154
Change-Id: Ib4d54d66a0c68b7d46e665d7cd94e97b72468e95
The fonts are updated to upstream version 2.001047.
The previous version had buggy ccmp rules that were mistakenly replacing
sequences such as A` <U+0041, U+0060> with À <U+00C0>. The new fonts
replace those with corrected rules that use combining accents instead, such
as U+0300 COMBINING GRAVE ACCENT instead of U+0060 GRAVE.
Also, a GSUB rule that mistakenly replaced aʾ <U+0061, U+02BE> with
ẚ <U+1E9A> is removed, and U+2117 SOUND RECORDING COPYRIGHT that was missing
from the Thin and Thin Italic fonts is added to them.
Bug: 16727859
Bug: 16719701
Change-Id: Ibd0a63ea3f51992c0e56fb255e68352915cc6c3a
It was mistakenly re-added in 6feb729b686b902be2520a91281e1a000c055da2.
Change-Id: I99a41ed8e6f1975e9808d8063e594fbb996d4334
(cherry picked from commit a7d8d7bfa75b283588aacae16cce78f6161acce9)
Update to upstream version 2.001045, which adds fontcrunch to the font
production process and fixes a problem with uneven digit widths. Should fix
https://code.google.com/p/android-developer-preview/issues/detail?id=330.
The font footprint is reduced by 705KB, most of it due to the crunching, but
also by using a newer version of fonttools that removes extra unnecessary
paddings from the glyf table.
Bug: 15348046
Bug: 16296048
Bug: 16299966
Change-Id: I838711916f8c47db011cfe889b232e60e6f1aa0c
(cherry picked from commit 6feb729b686b902be2520a91281e1a000c055da2)
The old glyph had its right part using a wrong component. The right
component was available in the font. The following script was used to fix
the issue:
from fontTools import ttLib
from nototools import subset
font = ttLib.TTFont('DroidSansFallbackFull.ttf', lazy=False)
glyf_table = font['glyf']
glyph = glyf_table['uni3A34']
for component in glyph.components:
if component.glyphName == 'glyph45821':
component.glyphName = 'glyph30895'
glyph.recalcBounds(glyf_table)
font.save('DroidSansFallbackFull.ttf-fixed')
subset.subset_font(
'DroidSansFallbackFull.ttf-fixed', 'DroidSansFallbackFull.ttf-subset')
The font footprint is reduced by 12KB mostly due to removing unneeded glyph
paddings.
Bug: 15149504
Change-Id: I914ec89435caadbeaa321e10fb0848f181fef667
The build file is modified to hang non-module fonts on DroidSansMono
instead, now that a device may not have DroidSansFallback. Also, some
cleanup is done to make the rules clearer and keep usages near definitions.
The support for following character will disappear from the extended
profiles because of this change:
U+202A LEFT-TO-RIGHT EMBEDDING
U+202B RIGHT-TO-LEFT EMBEDDING
U+202C POP DIRECTIONAL FORMATTING
U+202D LEFT-TO-RIGHT OVERRIDE
U+F95A 讀 CJK COMPATIBILITY IDEOGRAPH-F95A
U+F9F3 麟 CJK COMPATIBILITY IDEOGRAPH-F9F3
U+10400 𐐀 DESERET CAPITAL LETTER LONG I
U+10428 𐐨 DESERET SMALL LETTER LONG I
U+1044D 𐑍 DESERET SMALL LETTER ENG
U+1044E 𐑎 DESERET SMALL LETTER OI
U+1044F 𐑏 DESERET SMALL LETTER EW
The first four are not needed, as HarfBuzz makes sure they are rendered as
invisible, the two CJK compatibility characters have canonnical
decompositions to unified ideographs already supported in included Noto Sans
CJK fonts, and the Deseret letters were only in DroidSansFallback for
testing purposes.
Change-Id: Ibb7fa61dc851710ba14c3944281e228bd2e4f5b2
Remove various fonts that are not used by any build: Droid Kufi
(replaced by Noto Naskh), Droid Sans (symlinked to Roboto),
and Droid Sans Japanese (replaced by Motoya).
Change-Id: Iefb056810f3c9386a311f1c7d617d76050eb7ffe
The BCP47 tag we use for selecting Simplified vs Traditional Chinese is
Hans and Hant. This patch uses those tags in fallback_fonts.xml rather
than country names, which weren't getting matched.
Change-Id: I97e1da7b86e8fe8f026365146393304a5ab74443
All characters are now supported in other fonts in the fallback chain:
U+303D is supported in Noto Color Emoji, everything else is supported in
the subsettd Noto Sans Symbols.
Bug: 15777351
Change-Id: Ibf4bbffbfdddfa9e0f08ceff96c835ffeb3e555d
The font is now included in all non-smaller font builds, as opposed to the
previous "not smaller but not extended either" builds. This is in sync with
not including Noto Sans Japanese in the extended build.
Change-Id: Id0f79bc1de714ac876a601c4867a55b6dbfc820c
