category: "SANS_SERIF"
date_added: "2011-12-19"
source {
- repository_url: "https://github.com/librefonts/armata"
- commit: "fbbc7c2575fe310df0450aaa721ee4e860b03a0e"
+ repository_url: "https://github.com/googlefonts/armata"
+ commit: "acd66b422a3b61baae8fee57c197e9f782b87f57"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/Armata-Regular.ttf"
+ dest_file: "Armata-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yaml"
}
fonts {
# Armata
-**Status**: `missing_config`
-**Date**: 2026-02-25
-**Designer**: Viktoriya Grabowska
-**License**: OFL
-**METADATA.pb**: `ofl/armata/METADATA.pb`
+Source modernized 2026-07: the FontForge `.sfd` sources were converted to Glyphs (`.glyphs`) and now build with the Google Fonts Rust pipeline (gftools-builder3 + fontc). The repository, commit and config are recorded in the `source { }` block of METADATA.pb and are not duplicated here.
-## Data
+## Initial state
-| Field | Value |
-|-------|-------|
-| Repository URL | https://github.com/librefonts/armata |
-| Commit | `fbbc7c2575fe310df0450aaa721ee4e860b03a0e` |
-| Config YAML | — |
-| Branch | `master` |
-| Source types | sfd |
+The upstream repository at librefonts/armata shipped only FontForge sources (`src/Armata-Regular-TTF.sfd`) and had no config.yaml or Glyphs sources, so it could not build with the current Google Fonts pipeline. METADATA.pb recorded the repository and onboarding commit but no build configuration.
-## Methodology
+## Actions taken
-### Repository URL
-Discovered via google/fonts commit history, PR references, or GitHub search.
+The repository adopted the Unified Font Repository template. The FontForge source `src/Armata-Regular-TTF.sfd` was converted to Glyphs with babelfont-rs (upstream commit `219c0bb`), producing `sources/Armata-Regular.glyphs`, and a gftools-builder3 config was added. During conversion, the no-break space (U+00A0) was corrected to the expected advance width (683 units), and 22 glyphs were renamed to their production names. The superseded FontForge sources and legacy build cruft were then retired.
-### Commit Hash
-Used HEAD of upstream repository (latest commit at time of onboarding).
-- Commit date: 2014-10-17 13:29:34 +0300
-- Commit message: "update .travis.yml"
+## Final state
-### Config YAML
-Not applicable — upstream repo contains only FontForge .sfd sources, which are not compatible with gftools-builder.
+The repository builds `Armata-Regular.ttf` from `sources/Armata-Regular.glyphs` using gftools-builder3 and fontc. The `source { }` block in METADATA.pb points at the modernized repository, branch and config.
-## Evidence
+## Verification
-### METADATA.pb source block
-No source block present in METADATA.pb.
+The freshly built `Armata-Regular.ttf` was compared against the shipped Google Fonts binary on cmap coverage, vertical metrics, usWeightClass, fsSelection/macStyle, GSUB/GPOS feature sets, GDEF classes and advance widths. The verdict was FUNCTIONAL: the only difference was 22 glyphs renamed to their production names, with codepoint coverage unchanged. No blocking differences were found.
-### google/fonts history
-- Last font modification: `ecc5f91e743c`
-- Date: 2017-08-07 21:09:35 +0100
-- Subject: "hotfix-armata: v1.003 added (#823)"
+## Original repository (dormant)
-### Upstream repo cache
-- Cached at: `librefonts/armata`
-- Commit `fbbc7c2575fe` verified ✓
-
-## Confidence
-
-**Medium**: URL discovered via research; commit verified in upstream repo
-
-## Notes
-
-SFD-only sources (FontForge format), not gftools-builder compatible
+The original upstream repository is https://github.com/librefonts/armata (default branch `master`), whose latest commit is `fbbc7c2575fe310df0450aaa721ee4e860b03a0e`. This is the same commit recorded as the Google Fonts onboarding commit; no upstream commits were made after onboarding.