bd1844d272
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
98 lines
3.6 KiB
XML
98 lines
3.6 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Fallback Fonts
|
|
|
|
This file specifies the fonts, and the priority order, that will be searched for any
|
|
glyphs not handled by the default fonts specified in /system/etc/system_fonts.xml.
|
|
Each entry consists of a family tag and a list of files (file names) which support that
|
|
family. The fonts for each family are listed in the order of the styles that they
|
|
handle (the order is: regular, bold, italic, and bold-italic). The order in which the
|
|
families are listed in this file represents the order in which these fallback fonts
|
|
will be searched for glyphs that are not supported by the default system fonts (which are
|
|
found in /system/etc/system_fonts.xml).
|
|
|
|
Note that there is not nameset for fallback fonts, unlike the fonts specified in
|
|
system_fonts.xml. The ability to support specific names in fallback fonts may be supported
|
|
in the future. For now, the lack of files entries here is an indicator to the system that
|
|
these are fallback fonts, instead of default named system fonts.
|
|
|
|
There is another optional file in /vendor/etc/fallback_fonts.xml. That file can be used to
|
|
provide references to other font families that should be used in addition to the default
|
|
fallback fonts. That file can also specify the order in which the fallback fonts should be
|
|
searched, to ensure that a vendor-provided font will be used before another fallback font
|
|
which happens to handle the same glyph.
|
|
|
|
Han languages (Chinese, Japanese, and Korean) share a common range of unicode characters;
|
|
their ordering in the fallback or vendor files gives priority to the first in the list.
|
|
Locale-specific ordering can be configured by adding language and region codes to the end
|
|
of the filename (e.g. /system/etc/fallback_fonts-ja.xml). When no region code is used,
|
|
as with this example, all regions are matched. Use separate files for each supported locale.
|
|
The standard fallback file (fallback_fonts.xml) is used when a locale does not have its own
|
|
file. All fallback files must contain the same complete set of fonts; only their ordering
|
|
can differ.
|
|
-->
|
|
<familyset>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidNaskh-Regular-SystemUI.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansEthiopic-Regular.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansHebrew-Regular.ttf</file>
|
|
<file>DroidSansHebrew-Bold.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansThai.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansArmenian.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansGeorgian.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansDevanagari-Regular.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>Lohit-Bengali.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansTamil-Regular.ttf</file>
|
|
<file>DroidSansTamil-Bold.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>AndroidEmoji.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>MTLmr3m.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
<family>
|
|
<fileset>
|
|
<file>DroidSansFallback.ttf</file>
|
|
</fileset>
|
|
</family>
|
|
</familyset>
|