Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 100% 2
Chinese (Simplified Han script) CC-BY-SA-3.0 0% 55 934 6,810 55 2
Finnish CC-BY-SA-3.0 12% 48 883 6,425 48 2
French CC-BY-SA-3.0 1% 54 933 6,804 54 1 2
German CC-BY-SA-3.0
Japanese CC-BY-SA-3.0 0% 55 934 6,810 55 2
Portuguese (Brazil) CC-BY-SA-3.0 1% 54 933 6,804 54 1 2
Spanish CC-BY-SA-3.0 18% 45 681 5,040 45
Please sign in to see the alerts.

Summary

Project website pagure.io
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files c51004531
♪ I'm a bot, bot, bot ♪ authored 02/05/2026
Last commit in Weblate Update translation files bbd3e989a
Hosted Weblate authored 02/05/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/GAP.po
02/03/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 440 7,472 54,480
Source 55 934 6,810
Translated 29% 129 29% 2,174 28% 15,787
Needs editing 0% 0 0% 0 0% 0
Read-only 12% 55 12% 934 12% 6,810
Failing checks 1% 6 1% 6 1% 50
Strings with suggestions 1% 8 1% 16 1% 148
Untranslated strings 70% 311 70% 5,298 71% 38,693
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 4 changes 77 changes 1 change 0 changes 3 changes 0 changes 9 changes 0 changes 14 changes 0 changes 5 changes 0 changes 2 changes 0 changes 61 changes 0 changes 6 changes 3 changes 96 changes 0 changes 6 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

7,472
Hosted words
440
Hosted strings
29%
Translated
7
Contributors
0
Components
8
Languages
8
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
+12%
Translated
+16%
−100%
Contributors
+100%
User avatar weblate:commit

Changes committed
Changes committed 01/13/2026
User avatar jti65

Translation added
Add-on Location
Lisäosan sijainti
01/12/2026
User avatar weblate:commit

Changes committed
Changes committed 01/12/2026
User avatar jti65

Translation added
This document describes the conventions and customs surrounding the proper packaging of https://www.gap-system.org/[GAP] add-on packages in Fedora. Throughout this document, we use the word _add-on_ to substitute for GAP upstream's use of the word _package_, to avoid confusion with RPM packages.
Tässä dokumentissa kuvataan https://www.gap-system.org/[GAP]-lisäosapakettien asianmukaiseen pakkaamiseen liittyvät käytännöt ja tavat Fedorassa. Tässä dokumentissa käytämme sanaa _add-on_ korvaamaan GAP upstreamin käyttämän sanan _package_, jotta vältytään sekaannuksilta RPM-pakettien kanssa.
01/12/2026
User avatar weblate:commit

Changes committed
Changes committed 01/03/2026
User avatar serrador

Translation added
GAP add-ons are written to be installed simply by unpacking them in an existing GAP directory tree. For most add-ons, the only build action necessary is building the documentation. However, since the add-on authors assumed this would happen within the GAP tree, add-ons freely use relative paths to access GAP files. For example, packages that use TTH to build documentation (see below) commonly invoke `+../../../convert.pl+`. The RPM spec file MUST account for this, either by altering the add-on to point to paths under `+%{gap_libdir}+`, or by creating symbolic links to create the appearance that the build is taking place inside the GAP tree. If the add-on is altered for the build, the spec file SHOULD arrange for the original (unaltered) files to be installed, so that paths are correct after installation.
Los complementos de GAP están diseñados para instalarse simplemente descomprimiéndolos en un árbol de directorios de GAP existente. Para la mayoría de los complementos, la única acción de compilación necesaria es compilar la documentación. Sin embargo, dado que los autores de los complementos asumieron que esto ocurriría dentro del árbol de directorios de GAP, los complementos usan libremente rutas relativas para acceder a los archivos de GAP. Por ejemplo, los paquetes que usan TTH para compilar la documentación (ver más abajo) suelen invocar `+../../../convert.pl+`. El archivo de especificaciones RPM DEBE tener esto en cuenta, ya sea modificando el complemento para que apunte a las rutas bajo `+%{gap_libdir}+` o creando enlaces simbólicos para que parezca que la compilación se realiza dentro del árbol de directorios de GAP. Si se modifica el complemento para la compilación, el archivo de especificaciones DEBERÍA encargarse de que se instalen los archivos originales (sin modificar), de modo que las rutas sean correctas después de la instalación.
01/02/2026
User avatar weblate:commit

Changes committed
Changes committed 12/25/2025
User avatar mariobl

Translation changed
GAP add-ons are intended to be unpacked in place within a GAP directory tree. Ordinarily, the entire distribution directory is copied into `+%{gap_libdir}/pkg+` or `+%{gap_archdir}/pkg+`. This includes the documentation directories, which are consumed by the tools contained in gap-online-help. However, some files are not needed in the final install directory. Files that should not appear there include:
GAP-Add-ons sind so konzipiert, dass sie direkt im GAP-Verzeichnisbaum entpackt werden. Normalerweise wird das gesamte entpackte Verzeichnis nach `+%{gap_libdir}/pkg+` oder `+%{gap_archdir}/pkg+` kopiert. Dies schließt die Dokumentationsverzeichnisse ein, die von den in gap-online-help enthaltenen ToolsWerkzeuge verwendet werden. Einige Dateien werden jedoch im endgültigen Installationsverzeichnis nicht benötigt. Folgende Dateien sollten dort nicht enthalten sein:
12/25/2025
User avatar None

Component unlocked
Fixing an alert automatically unlocked the component. 12/25/2025
User avatar None

Component locked
The component was automatically locked because of an alert. 12/24/2025
Browse all component changes