From Fedora Project Wiki

< Changes

Revision as of 21:48, 8 December 2020 by Jibecfed (talk | contribs) (doc)

Distribution Localization statistics


Generate per language statistics about the current localization support for the whole Fedora Operating System. Provide a static website with results and useful files for translators (as an example: translation memories).


Current status

  • Targeted release: Fedora 34
  • Last updated: 2020-12-08
  • 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

Language support is a transversal activity, there is no way to know the actual language support provided by Fedora as an Operating System.

Because language support and translations are part of each upstream software, the Linux language community is as spread as the Free Libre and Open Source community is.

The ability to share efforts is limited (with data, tools, etc.):

  • because translators often have a low level of technical knowledge,
  • because development experts are more keen to use English by default, and don't know much about languages support requirements,
  • because of the complexity to get an overview of the current localization status of the Linux community.

Debian did something similar (20 years ago) (code:


  • Why not reuse the code from Debian? This source code is deeply integrated with Debian infrastructure, and uses a language that doesn't allow to share easily with existing i18n/l10n tooling/libraries. We do use translation-finder used by Weblate, language data from Weblate, polib from David Jean Louis, Translate Toolkit from

Benefit to Fedora

Help the Linux community to face understand the language support challenges by providing measurement. Increase the contributor effectiveness by providing translation memories and other tools. Opens the possibility to change the translation file release process.


All of the work is isolated, as long as dnf works, the automation works. The closer to mirror the cheaper it is for network cost (all Fedora is downloaded at each execution).

  • Proposal owners:
    • Francois Andrieu integrate the existing scripts into containers to allow execution into openshift
    • Infra team:
      • provide some space for script execution (50 GB per release)
      • provide the domain name
      • provide a location for static website (about 2 GB per release, may increase over time)

  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience


N/A (not a System Wide Change)

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
  • Blocks product? product


A draft with simplistic template is there:

Code and "documentation" are there:

Release Notes