Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update Mozila Typeface web fonts

Open
#1,086 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 12 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
design, web-dev

Research direction

Start by locating the current WOFF2 files and the OFL source-repository pipeline that produces the extended font artifacts. Compare the Mozilla Headline and Mozilla Text assets with the newer versions; done means consumers receive the added glyphs and language support.

Written by the indexing model from the issue text.

Description

Please describe the change you wish to see

New glyphs were added to Mozilla Headline and Mozilla Text over time. The last versions submitted to G Fonts contain additional language support (Latin Ext-B basically).

Please describe why these changes need to be made

Currently consumers have to decide whether to apply the Mozilla family based on the language served, given the lack of i18n support in the fonts.

Recent additions at least cover more languages to make the cut less tedious, and/or any missing glyphs falling back to system shapes not that painful if a backup font override is not specified for such language wholesale.

Please describe where this component is currently in use

All consumers.

The WOFF2 files used previously were provided by the foundry. The extended ones are a build artifact of the OFL source repo pipeline now.

Dominant language
SCSS
Stars
299
Forks
83
Avg merge
10d 2h
Merged PRs (30d)
21

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/protocol

All issues in mozilla/protocol

Similar issues

More Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.