The translation is temporarily closed for contributions due to maintenance, please come back later.
Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 100% 3
Chinese (Simplified Han script) CC-BY-SA-3.0 0% 60 1,527 10,897 60 1
Finnish CC-BY-SA-3.0 5% 57 1,432 10,342 57
French CC-BY-SA-3.0 0% 60 1,527 10,897 60 1
German CC-BY-SA-3.0 100% 1
Japanese CC-BY-SA-3.0 0% 60 1,527 10,897 60 1
Portuguese (Brazil) CC-BY-SA-3.0 0% 60 1,527 10,897 60 1
Spanish CC-BY-SA-3.0
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 c4a8ad638
♪ I'm a bot, bot, bot ♪ authored 03/13/2026
Last commit in Weblate Update translation files 3b1e17c14
Hosted Weblate authored 03/13/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/MPI.po
03/05/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 480 12,216 87,176
Source 60 1,527 10,897
Translated 38% 183 38% 4,676 38% 33,246
Needs editing 0% 0 0% 0 0% 0
Read-only 12% 60 12% 1,527 12% 10,897
Failing checks 1% 4 1% 40 1% 370
Strings with suggestions 1% 4 1% 4 1% 48
Untranslated strings 61% 297 61% 7,540 61% 53,930
Last 12 months Previous

Activity in last 12 months

0 changes 4 changes 0 changes 1 change 0 changes 1 change 0 changes 9 changes 1 change 7 changes 0 changes 5 changes 0 changes 3 changes 1 change 66 changes 1 change 5 changes 0 changes 85 changes 0 changes 28 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

12,216
Hosted words
480
Hosted strings
38%
Translated
5
Contributors
0
Components
8
Languages
8
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
+11%
Translated
+27%
−50%
Contributors
+100%
User avatar peartown

Component locked
Component locked 03/05/2026
User avatar weblate:commit

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

Translation completed
Translation completed 03/04/2026
User avatar serrador

Translation changed
# Define a macro for calling ../configure instead of ./configure
%global dconfigure %(printf %%s '%configure' | sed 's!\./configure!../configure!g')
# Define una macro para llaminvocar a ../configure en lugar de ./configure
%global dconfigure %(printf %%s '%configure' | sed 's!\./configure!../configure!g')
03/04/2026
User avatar serrador

Translation changed
A sample spec file
Un archivo de especificaciones de muestra
03/04/2026
User avatar serrador

Translation changed
Files must be shared between packages as much as possible. Compiler independent parts, such as data files in `+%{_datadir}/%{name}+` and man files MUST be put into a `+-common+` subpackage that is required by all of the binary packages (the serial package and all of the MPI packages).
Los archivos deben compartirse entre paquetes tanto como sea posible. Las partes independientes del compilador, como los archivos de datos en `+%{_datadir}/%{name}+` y los archivos man, DEBEN incluirse en un subpaquete `+-common+` requerido por todos los paquetes binarios (el paquete serial y todos los paquetes MPI).
03/04/2026
User avatar serrador

Translation changed
Each MPI build MUST have a separate -devel subpackage (e.g. foo-mpich-devel) that includes the development libraries and `+Requires: %{name}-headers+` if such a package exists. The goal is to be able to install and develop using e.g. 'foo-mpich-devel' without needing to install e.g. openmpi or the serial version of the package.
Cada compilación MPI DEBE tener un subpaquete -devel independiente (p. ej., foo-mpich-devel) que incluya las bibliotecas de desarrollo y `+Requires: %{name}-headers+` si dicho paquete existe. El objetivlogro es poder instalar y desarrollar usando, por ejemplo.e., "foo-mpich-devel" sin necesidad de instalar, por ejemplo.ej., OpenMPI o la versión serial del paquete.
03/04/2026
User avatar serrador

Translation changed
In case the headers are the same regardless of the compilation method and architecture (e.g. 32-bit serial, 64-bit Open MPI, MPICH), they MUST be split into a separate `+-headers+` subpackage (e.g. 'foo-headers'). Fortran modules are architecture specific and as such are placed in the (MPI implementation specific) `+-devel+` package (foo-devel for the serial version and foo-openmpi-devel for the Open MPI version).
Si los encabezados son los mismos independientemente del método de compilación y la arquitectura (p. ej., serial de 32 -bits, Open MPI de 64 -bits, MPICH), DEBEN dividirse en un subpaquete `+-headers+` independiente (p. ej., `foo-headers`). Los módulos Fortran son específicos de cada arquitectura y, por lo tanto, se incluyen en el paquete `+-devel+` (específico de la implementación de MPI) (foo-devel para la versión serial y foo-openmpi-devel para la versión Open MPI).
03/04/2026
User avatar serrador

Translation changed
Each MPI build of shared libraries SHOULD have a separate -libs subpackage for the libraries (e.g. foo-mpich-libs). As in the case of MPI compilers, library configuration (in `+/etc/ld.so.conf.d+`) MUST NOT be made.
Cada compilación MPI de bibliotecas compartidas DEBE tenerTENDRÍA un subpaquete -libs independiente para las bibliotecas (p. ej., foo-mpich-libs). Al igual que en el caso de los compiladores MPI, NO DEBE configurarse la biblioteca (en `+/etc/ld.so.conf.d+`).
03/04/2026
User avatar serrador

Translation changed
The MPI enabled bits MUST be placed in a subpackage with the suffix denoting the MPI compiler used (for instance: `+foo-openmpi+` for Open MPI [the traditional MPI compiler in Fedora] or `+foo-mpich+` for MPICH). For directory ownership and to guarantee the pickup of the correct MPI runtime, the MPI subpackages MUST require the correct MPI compiler's runtime package.
Los bits habilitados para MPI DEBEN incluirse dentro de un subpaquete con el sufijo que indica el compilador MPI utilizado (por ejemplo: `+foo-openmpi+` para Open MPI [el compilador MPI tradicional de Fedora] o `+foo-mpich+` para MPICH). Para la propiedad del directorio y para garantizar la instalación del entorno de ejecución MPI correcto, los subpaquetes MPI DEBEN requerir el paquete de entorno de ejecución del compilador MPI correcto.
03/04/2026
Browse all component changes