From Fedora Project Wiki
m (doc)
(improve descriptions)
Line 2: Line 2:


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.
 
Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
Provide a public website for end users and contributors, containing translation progress and useful files for translators (as an example: translation memories).
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).


== Owner ==
== Owner ==
Line 30: Line 28:
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/34 | Fedora 34]]  
* Targeted release: [[Releases/34| Fedora 34]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 51: Line 49:
The ability to share efforts is limited (with data, tools, etc.):
The ability to share efforts is limited (with data, tools, etc.):


* because of the complexity to get an overview of the current localization status of the Linux community,
* because translators often have a low level of technical knowledge,
* 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 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) https://www.debian.org/international/l10n/ (code: https://salsa.debian.org/webmaster-team/webwml/-/commits/master/english/international/l10n/scripts/transmonitor-check). But this work:


Debian did something similar (20 years ago) https://www.debian.org/international/l10n/ (code: https://salsa.debian.org/webmaster-team/webwml/-/commits/master/english/international/l10n/scripts/transmonitor-check)
* is limited in terms of features (no translation memories there)
* is too deeply integrated with Debian infrastructure (data extraction, computation and website generation are 100% debian specific)
* is using a programming language that doesn't allow to share easily with existing i18n/l10n libraries (it did not exist 20 years ago)


== Feedback ==
== Feedback ==
* 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 translatehouse.org.


<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
Line 67: Line 67:
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved? -->
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved? -->


Help the Linux community to face understand the language support challenges by providing measurement.
It is a progress for the project: provide a new tool to translator community.
Increase the contributor effectiveness by providing translation memories and other tools.
 
Opens the possibility to change the translation file release process.
It helps the Linux community to better understand the language support challenges.
 
It increases contributors effectiveness by providing translation memories and other tools.
 
It opens new possibilities:
 
* could we use these translation memories to train machines to suggest new translations?
* could we use these translation memories to detect quality issues (spellcheck, linters, etc)?
* could we use these translation memories the way we ship translations to users? (Ubuntu does it, but never bring back translation to main project: https://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/files)


== Scope ==
== Scope ==

Revision as of 20:28, 9 December 2020

Distribution Localization statistics

Summary

Provide a public website for end users and contributors, containing translation progress and useful files for translators (as an example: translation memories).

Owner

Current status

  • Targeted release: Fedora 34
  • Last updated: 2020-12-09
  • 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 of the complexity to get an overview of the current localization status of the Linux community,
  • 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.

Debian did something similar (20 years ago) https://www.debian.org/international/l10n/ (code: https://salsa.debian.org/webmaster-team/webwml/-/commits/master/english/international/l10n/scripts/transmonitor-check). But this work:

  • is limited in terms of features (no translation memories there)
  • is too deeply integrated with Debian infrastructure (data extraction, computation and website generation are 100% debian specific)
  • is using a programming language that doesn't allow to share easily with existing i18n/l10n libraries (it did not exist 20 years ago)

Feedback

Benefit to Fedora

It is a progress for the project: provide a new tool to translator community.

It helps the Linux community to better understand the language support challenges.

It increases contributors effectiveness by providing translation memories and other tools.

It opens new possibilities:

  • could we use these translation memories to train machines to suggest new translations?
  • could we use these translation memories to detect quality issues (spellcheck, linters, etc)?
  • could we use these translation memories the way we ship translations to users? (Ubuntu does it, but never bring back translation to main project: https://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/files)

Scope

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 languages.fedoraproject.org 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

Dependencies

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

Documentation

A draft with simplistic template is there: https://jibecfed.fedorapeople.org/partage/fedora-localization-statistics/f32/language/fr/

Code and "documentation" are there: https://pagure.io/fedora-localization-statistics

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/LocalizationMeasurementAndTooling&oldid=597068"