From Fedora Project Wiki


Produce tooling for translators and measurement of Linux translation progress. By extracting information coming from source files used in RPMs.

How to achieve this objective?

As RPMs change all the time, either the system would extract the full list of RPM for a particular Fedora version at a given time (is it doable?) or would register to RPM package activity using datagrepper.

From the source file, use to identify translation file and python to copy the files.

From the translation file, use to interact with content (statistics, aggregation, conversion...).


Why not using list of ISO images? It was used for first tests, but it only contains a sub set of packages.

Which package updates are meaningful for this goal? What interest us is upstream code change, independently if this source code is part of one or many RPM package. Only new package name and version interests us, the package release is not meaningful.

Which Fedora versions do we want? We only want actual branches, rawhide activity is not mandatory.

Open questions

If the system registers to RPM activity notification, how to run first initialization?


about how to register to package activity

Way to do it:

  1. Extract build information from Datagrepper
    1. probably this topic with new state=1 (documentation:
  2. Ask koji the list of related RPMs using listBuildRPMs(Build) (
  3. Ask koji files related to this RPM using getRPMDeps(rpmID, depType=None, queryOpts=None, strict=False)
  4. Ask koji files details about each file using getRPMFile(rpmID, filename, strict=False)
  5. If file was never processed before, then apply translation processing


Step Link Retrieved information Comment/questions
1 koji build id=1589180 can we have more than one build?
2 get linked rpm Texte de la cellule
3/4 Texte de la cellule Texte de la cellule