Translation status

8 Strings 12%
Browse Translate
589 Words 4%
4,467 Characters 7%

Strings status

Strings Words Characters
8 589 4,467
All strings Browse Translate Zen
1 27 339
Translated strings Browse Translate Zen
7 562 4,128
Unfinished strings Browse Translate Zen
7 562 4,128
Untranslated strings Browse Translate Zen

Summary

Project website pagure.io/fedora-docs-l10n/modularity
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/modularity.git
Repository branch master
Last remote commit automatic update of pot/po files 503bd7c4
♪ I'm a bot, bot, bot ♪ authored 3 months ago
Last commit in Weblate Translated using Weblate (Spanish) 88e72e83
User avatar vareli authored 4 weeks ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-modularity/nav/
File mask po/*/master/pages/core-concepts/module-buildorder.po
Translation file Download po/es/master/pages/core-concepts/module-buildorder.po
Last change May 4, 2025, 12:56 a.m.
Last change made by None
Language Spanish
Language code es
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 507,161,083
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
7 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 8 589 4,467
Translated 12% 1 4% 27 7% 339
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 87% 7 95% 562 92% 4,128
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 9 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes
JulAugSepOctNovDecJanFebMarAprMayJun

Quick numbers

589
Hosted words
8
Hosted strings
12%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+12%
—
Contributors
+100%
User avatar None

Changes committed
Changes committed 2 months ago
User avatar serrador

Propagated change
**The Modularity project has been retired** and there are https://fedoraproject.org/wiki/Changes/RetireModularity[no modules in Fedora 39 or newer] or https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KA3JQUZW63A4V7OQ7ZVDFCM32EQUSOXH/[in EPEL]. This page is only retained for historical reference.
**El proyecto Modularity ha sido retirado** y no hay https://fedoraproject.org/wiki/Changes/RetireModularity[sino modules iódulos en Fedora 39 or newe posterior] o https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KA3JQUZW63A4V7OQ7ZVDFCM32EQUSOXH/[ien EPEL]. Esta página sólo se conserva como referencia histórica.
2 months ago
User avatar serrador

Propagated change
**The Modularity project has been retired** and there are https://fedoraproject.org/wiki/Changes/RetireModularity[no modules in Fedora 39 or newer] or https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KA3JQUZW63A4V7OQ7ZVDFCM32EQUSOXH/[in EPEL]. This page is only retained for historical reference.
**El proyecto Modularity ha sido retirado** y no hay https://fedoraproject.org/wiki/Changes/RetireModularity[no modules in Fedora 39 or newer] o https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KA3JQUZW63A4V7OQ7ZVDFCM32EQUSOXH/[in EPEL]. Esta página sólo se conserva como referencia histórica.
2 months ago
User avatar None

Resource updated
The “po/es/master/pages/core-concepts/module-buildorder.po” file was changed. 3 months ago
User avatar None

String added in the repository
**The Modularity project has been retired** and there are https://fedoraproject.org/wiki/Changes/RetireModularity[no modules in Fedora 39 or newer] or https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KA3JQUZW63A4V7OQ7ZVDFCM32EQUSOXH/[in EPEL]. This page is only retained for historical reference.
 
3 months ago
User avatar None

Resource updated
File “po/es/master/pages/core-concepts/module-buildorder.po” was added. a year ago
User avatar None

String updated in the repository
In this example we have the build order of the `perl-bootstrap:5.32` module. The component with the lowest `buildorder` number will start building first. In our case this is the package `perl` with the `buildorder` number 0. All the other component (package) builds need to wait until the first build batch is built. A build batch consists of packages which share the same `buildorder` number. After the `perl` package is built then the build batch has finished building all its components and can move to a higher order of the build order. The build of package `perl` needs to be added and enabled to the buildroot of the build of packages of the next `buildorder` number. In our case the next build batch is the build batch with the `buildorder` number 2. A build batch can have one or more packages. This means that the packages can be built simultaneously. Each build batch uses all the previous build batches as build dependencies which are available and enabled in its buildroots. The only build batch which does not have any previous build batch dependencies is the build batch with `buildorder` number 0. The only build batch which is not used as build batch dependencies is the build batch with the highest `buildorder` number. In our example the build batch with `buildorder` number 5 consists of 9 packages and number 4 consists of over 100 packages. All the packages built in build batches of `buildorder` numbers 0-4 will be used as build time dependencies for the build batch with the `buildorder` number 5.
 
a year ago
User avatar None

String updated in the repository
⋮
components:
rpms:
perl:
rationale: The Perl interpreter.
ref: f33
buildorder: 0
perl-Fedora-VSP:
rationale: A build dependency.
ref: f33
buildorder: 1
perl-generators:
rationale: A build dependency.
ref: f33
buildorder: 2
perl-Algorithm-Diff:
rationale: A build dependency.
ref: f33
buildorder: 3
⋮
perl-Config-AutoConf:
rationale: A build dependency.
ref: f33
buildorder: 4
⋮
perl-IO-Compress-Lzma:
rationale: A build dependency.
ref: f33
buildorder: 5
⋮
perl-Data-OptList:
rationale: A build dependency.
ref: f33
buildorder: 6
⋮
perl-Sub-Exporter:
rationale: A build dependency.
ref: f33
buildorder: 7
perl-Data-Section:
rationale: A build dependency.
ref: f33
buildorder: 8
perl-Software-License:
rationale: A build dependency.
ref: f33
buildorder: 9
⋮
 
a year ago
User avatar None

String updated in the repository
build order of a `perl-bootstrap:5.32` module stream
 
a year ago
User avatar None

String updated in the repository
If the `buildorder` property is specified for each component of the module stream, the build system needs to respect this ordering. This means that each `buildorder` number represents a group or a batch of packages that need to be built together. Each higher “build batch” needs the RPM artifacts from the previous build batches to be present and enabled in the current one. So they can serve as dependencies for the current batch. This continues until the last batch is built. The last batch will contain all the other artifacts from the previous batches.
+
+
 
a year ago
Browse all translation changes