From Fedora Project Wiki


Improve Default Font Handling

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

This aims to make default fonts easier to update for all the variants on Fedora and reduce the maintenance costs to apply for them.

Owner


Current status

  • Targeted release: Fedora Linux 39
  • Last updated: 2023-05-24
  • [<will be assigned by the Wrangler> devel thread]
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Currently there are multiple sources to manage what font packages should be installed for a Fedora release and spins, such as comps, langpacks, lorax, workstation-ostree-config, and fedora-kickstarts. This sometimes makes compilcated to update the default fonts. So we want to introduce new meta packages into langpacks and replace a list of font packages with it. We expect to improve such situations by updating langpacks only then.

  • langpacks-font-core-sans, langpacks-fonts-core-serif, langpacks-fonts-core-monospace, langpacks-fonts-core-emoji
    • Metapackages to pull the default font for Latin characters and emoji
  • langpacks-font-default-cjk-sans, langpacks-fonts-default-cjk-serif, langpacks-fonts-default-cjk-monospace
    • Metapackages to pull the default font for CJK
  • langpacks-font-default-sans, langpacks-fonts-default-serif, langpacks-fonts-default-monospace
    • Metapackages to pull the default fonts for other languages
  • langpacks-font-extra-<language code>
    • Metapackages to pull extra fonts for certain languages if any

Feedback

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes