google / google/fonts

Manrope[wght].ttf declares family "Manrope ExtraLight" (default instance is wght 200)

Open
#10,870 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
20.5k
Forks
2.9k
Avg merge
1d 21h
Merged PRs (30d)
95

Description

## Summary

`ofl/manrope/Manrope[wght].ttf` declares its legacy family name as **`Manrope ExtraLight`**, because the `wght` axis defaults to 200 and name IDs 1/2 describe the default instance. Anything that reads name ID 1 — or instances statics from this file without overriding names — reports or produces "Manrope ExtraLight".

## Evidence

From `ofl/manrope/Manrope[wght].ttf` (current `main`):

```
name family(1) "Manrope ExtraLight"
name subfamily(2) "Regular"
name postScript(6) "Manrope-ExtraLight"
name typoFamily(16) "Manrope"
name typoSubfamily(17) "ExtraLight"
OS/2 usWeightClass 200
fvar wght min 200 default 200 max 800
```

`ofl/manrope/METADATA.pb` carries it too — the entry declared at `weight: 400` reads:

```
post_script_name: "Manrope-ExtraLight"
full_name: "Manrope ExtraLight"
```

## Why it matters downstream

Tools that read a font's name rather than its outlines report pages using Manrope as using Manrope ExtraLight, at every weight. Rendering is unaffected — outlines and per-instance weights are correct — so this is invisible in a browser and shows up only in design-handoff tools, font inspectors and asset catalogues.

It also propagates: packages that instance static webfonts from this file inherit the name. `@fontsource/manrope@5.3.0` ships woff2 named `Manrope ExtraLight SemiBold`, `Manrope ExtraLight Medium`, and so on. Filed separately at fontsource/font-files#162.

## Suggested fix

Set the default instance of the `wght` axis to 400 (Regular), so name IDs 1/2 describe Manrope Regular, or set name IDs 1/2/4/6 explicitly to the Regular instance while leaving the axis default. Most variable families on Google Fonts with a 400 default do not have this problem; Manrope's axis starting and defaulting at 200 is what exposes it.

Related: `upstream_info.md` records the upstream as https://github.com/aaronbell/manrope (the `sharanda/manrope` URL in METADATA.pb is deleted). The static webfonts in that repo's `fonts/webfonts/` **are** named correctly — `Manrope`, `Manrope Medium`, `Manrope SemiBold`, `Manrope`/Bold, `Manrope ExtraBold` — so the correct names exist upstream and are lost in the variable build.

Contributor guide

Open the contributing guide

Research direction

Inspect ofl/manrope/Manrope[wght].ttf and ofl/manrope/METADATA.pb, then compare their names with the static files in the upstream fonts/webfonts/ directory. Trace how the variable font is generated and verify that the default or explicit names identify Manrope Regular while preserving the correct weight metadata.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.