From Fedora Project Wiki

Translations are coming from everywhere, project by project on a "vertical" way. It comes from a project and through the packaging process it reach the user, project by project. When an Hungarian or French use Fedora in his language, use many software when using Fedora, and see translations (and localisation) on a horizontal way ( ie, per locale ). To improve the end-user experience, we need to think and act in a transversal way.

Improve Fedora (as a platform) translation release preparation

Objective

We want to support language teams activities and help the emergence of new languages by giving more support tools to help language monitoring : production process, current status and quality insurance.

Context : please note this is not Fedora software focused but Fedora product focused, it means it also includes upstream project perimeter.

To do so, many metrics and tools are needed

Globally

  • Monitor the current state of Fedora on a horizontal way ;
    • Status : what is the LANGUAGE status in Fedora packages ?
      • Overall statistics about current packages translation (with timeline)
      • How active is the localization team ? mailing list, active contributors, bugs, words changed
      • Request level : per country visitor stats : ISO download, websites visitors, user settings
      • Automated quality checks : typography rules, grammar rules, translation pull from source.
  • Have better communications with other teams, packages, maintainers, and create in long term an standardized operation procedure (SOP) for translators
    • Write about translation platform, good and bad habits, encourage internalization, explain how we work, etc.
  • Support a per language community (independent of project source or processes)
    • Languages teams should be helped to go behind Fedora limits and reach other translation teams
  • We need a translation team wrangler / overseer (With a task of managing dates, schedules, and leader of the coordinators)
  • Have recurring online meetings on IRC or elsewhere, maybe once together with Zanata devs
  • Clarify the way we handle new Fedora version (websites, docs, packages, languages)

On the current translation platform (Zanata)

  • Know where we are => Metrics  : what is translated/fuzzy/untranslated for my language ?
  • Product centric categories => what is translated/fuzzy/untranslated for my language for Fedora 25, or Fedora Atomic, etc.
  • Product centric information => when is the next release and until when can I correct things ?
  • To know what is happening => who contributed ? what changed in the translation (diff) ? what are the new project po files ? what are the last added projects ?
    • Examples : add improved version of this page https://fedora.zanata.org/profile/view/jibecfed
    • Sorting improvements : sort project by last edit, by last maintainer po push, by importance, etc.
    • Produce automatic digest of changes to mailing list (new projects, new files, translation updates, etc.)
  • Create per language review process => a language should be able to prevent content to be available to the project maintainer if it isn't reviewed
  • Ease communication =>
  • Automatic tools to help =>
    • Ex1 : detect very close sentences that have different translations
    • Ex2 : when there is an existing translation close to the source and that is not translated yet, propose merge (use case : two branches on the same project, one was translated, not the other one)
    • Ex3: Automated quality checking, looking for potential typo, size of the string, typographic rules
  • Zanata feature request to aid problems above
    • Percentage usage from translation memory - what is fuzzy, or need to be retranslated fully (minor fix, or remake)
    • Branch categorization - better overall view of the project files, and their importance before freezing date
    • Missing overall statistics per language (untranslated, fuzzy, translated)