fedora-docs-l10n/modularity - English @ Fedora Weblate

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
Glossary fedora-docs-l10n/modularity CC-BY-SA-3.0	100%	0	0	0	0	0	0	0

master/antora.yml CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/archive CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/copr/building-modules-in-copr CC-BY-SA-3.0		0	0	0	0	2	0	0

master/pages/building-modules/fedora/adding-new-modules CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/fedora/building-modules CC-BY-SA-3.0		0	0	0	0	1	0	0

master/pages/building-modules/fedora/defining-modules CC-BY-SA-3.0		0	0	0	0	3	0	0

master/pages/building-modules/fedora/index CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/fedora/inspecting-build-failures CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/fedora/managing-defaults CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/fedora/module-obsoletes CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/fedora/updating-modules CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/index CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/building-modules/local/building-modules-locally CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/community CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/building CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/consuming CC-BY-SA-3.0		0	0	0	0	1	0	0

master/pages/core-concepts/dnf-behavior CC-BY-SA-3.0		0	0	0	0	1	0	0

master/pages/core-concepts/index CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/modular-repository CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-artifacts CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-buildorder CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-context CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-dependency-resolution CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-lifecycles CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/module-stream CC-BY-SA-3.0		0	0	0	0	2	0	0

master/pages/core-concepts/nsvca CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/core-concepts/upgrade-paths CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/faq CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/glossary CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/history CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/hosting-modules CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/index CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/_partials/core-concepts-links CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/_partials/submit-module-update CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/policies/index CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/policies/naming-guidelines CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/policies/packaging-guidelines CC-BY-SA-3.0		0	0	0	0	3	0	0

master/pages/references CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/requirements CC-BY-SA-3.0		0	0	0	0	0	0	0

master/pages/using-modules CC-BY-SA-3.0		0	0	0	0	0	0	0

nav CC-BY-SA-3.0		0	0	0	0	0	0	0

Overview

Project website	pagure.io/fedora-docs-l10n/modularity
Instructions for translators	Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation license	CC-BY-SA-3.0 ^nav ^{fedora-docs-l10n/modularity} ^{master/pages/community} ^{master/pages/faq} ^{master/pages/using-modules} ^{master/pages/glossary} ^{master/pages/core-concepts/upgrade-paths} ^{master/pages/core-concepts/index} ^{master/pages/_partials/submit-module-update} ^{master/antora.yml} ^{master/pages/policies/naming-guidelines} ^{master/pages/building-modules/fedora/defining-modules} ^{master/pages/policies/packaging-guidelines} ^{master/pages/building-modules/fedora/updating-modules} ^{master/pages/building-modules/fedora/inspecting-build-failures} ^{master/pages/archive} ^{master/pages/references} ^{master/pages/core-concepts/dnf-behavior} ^{master/pages/_partials/core-concepts-links} ^{master/pages/core-concepts/module-context} ^{master/pages/core-concepts/consuming} ^{master/pages/core-concepts/module-lifecycles} ^{master/pages/core-concepts/module-dependency-resolution} ^{master/pages/core-concepts/nsvca} ^{master/pages/building-modules/fedora/module-obsoletes} ^{master/pages/history} ^{master/pages/requirements} ^{master/pages/policies/index} ^{master/pages/index} ^{master/pages/building-modules/fedora/index} ^{master/pages/building-modules/fedora/managing-defaults} ^{master/pages/building-modules/local/building-modules-locally} ^{master/pages/building-modules/copr/building-modules-in-copr} ^{master/pages/building-modules/fedora/building-modules} ^{master/pages/building-modules/fedora/adding-new-modules} ^{master/pages/hosting-modules} ^{master/pages/building-modules/index} ^{master/pages/core-concepts/module-buildorder} ^{master/pages/core-concepts/modular-repository} ^{master/pages/core-concepts/module-stream} ^{master/pages/core-concepts/module-artifacts} ^{master/pages/core-concepts/building}

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		1,308		28,331		209,460
Translated	100%	1,308	100%	28,331	100%	209,460
Needs editing	0%	0	0%	0	0%	0
Read-only	100%	1,308	100%	28,331	100%	209,460
Failing checks	1%	13	2%	748	3%	8,062
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	0%	0	0%	0	0%	0

Last 12 months Previous

Activity in last 12 months


Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul

Quick numbers

28,331

Hosted words

1,308

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+4%

—

Hosted strings

+3%

—

Translated

—

Contributors

—

None Resource update fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	The "`pot/master/pages/core-concepts/upgrade-paths.pot`" file was changed. a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English With a static context it's possible to use a xref:building-modules/fedora/module-obsoletes.adoc[`modulemd-obsoletes` document] to switch to a completely different stream. This is useful when you want to stop supporting an existing stream, or a context, and you provide a replacement. When user has installed an obsolete stream, or a context, DNF will offer switching to the replacement. English Read only With a static context it's possible to use a xref:building-modules/fedora/module-obsoletes.adoc[`modulemd-obsoletes` document] to switch to a completely different stream. This is useful when you want to stop supporting an existing stream, or a context, and you provide a replacement. When user has installed an obsolete stream, or a context, DNF will offer switching to the replacement. a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English The same constrains of dynamic context and a strong recommendation for static context apply here. With static context you can stop building modules for that context whenever you want. With dynamic context you cannot and need to maintain the full matrix forever. English Read only The same constrains of dynamic context and a strong recommendation for static context apply here. With static context you can stop building modules for that context whenever you want. With dynamic context you cannot and need to maintain the full matrix forever. a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English Removing a context English Read only Removing a context a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English On the other hand, with a static context DNF will understand that modules from context `B` should not mix with module from a context `A`. When installing `perl-DBI:stream` for the first time, DNF will pick the right context based on an already installed `perl` stream. When upgrading `perl-DBI:stream`, DNF will preserve the context based on an already installed `perl-DBI:stream` context. Thus using static-context modules is recommended. English Read only On the other hand, with a static context DNF will understand that modules from context `B` should not mix with module from a context `A`. When installing `perl-DBI:stream` for the first time, DNF will pick the right context based on an already installed `perl` stream. When upgrading `perl-DBI:stream`, DNF will preserve the context based on an already installed `perl-DBI:stream` context. Thus using static-context modules is recommended. a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English Upgrade path 1 Upgrade path 2 ──────────────────── ──────────────────── perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑ requires perl:5.30 ↑ requires perl:5.32 ↑ ↑ ┌────────────────────┐ perl-DBI:stream:1:A ↑ │perl-DBI:stream:1:B │ An artificial module build requires perl:5.30 ↑ │ requires perl:5.32│ filling a gap in this matrix └────────────────────┘ English Read only Upgrade path 1 Upgrade path 2 ──────────────────── ──────────────────── perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑ requires perl:5.30 ↑ requires perl:5.32 ↑ ↑ ┌────────────────────┐ perl-DBI:stream:1:A ↑ │perl-DBI:stream:1:B │ An artificial module build requires perl:5.30 ↑ │ requires perl:5.32│ filling a gap in this matrix └────────────────────┘ a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English It's not possible to achieve this by standard means with a dynamic context. DNF would report https://bugzilla.redhat.com/show_bug.cgi?id=1708589[a warning] or https://bugzilla.redhat.com/show_bug.cgi?id=1757460[an error]. If you ever needed to achieve this with nonstatic contexts, the key point how to indulge DNF is fill a matrix of contexts and versions with artificial modules which have never been built (i.e. manually writing the modulemd documents): English Read only It's not possible to achieve this by standard means with a dynamic context. DNF would report https://bugzilla.redhat.com/show_bug.cgi?id=1708589[a warning] or https://bugzilla.redhat.com/show_bug.cgi?id=1757460[an error]. If you ever needed to achieve this with nonstatic contexts, the key point how to indulge DNF is fill a matrix of contexts and versions with artificial modules which have never been built (i.e. manually writing the modulemd documents): a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/upgrade-paths — English	English Upgrade path A Upgrade path B ──────────────────── ──────────────────── perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑ requires perl:5.30 ↑ requires perl:5.32 ↑ perl-DBI:stream:1:A ↑ requires perl:5.30 ↑ ╰──────────────────╯ ╰──────────────────╯ Old context New context English Read only Upgrade path A Upgrade path B ──────────────────── ──────────────────── perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑ requires perl:5.30 ↑ requires perl:5.32 ↑ perl-DBI:stream:1:A ↑ requires perl:5.30 ↑ ╰──────────────────╯ ╰──────────────────╯ Old context New context a month ago
None Resource update fedora-docs-l10n/modularity / master/pages/core-concepts/module-context — English	The "`pot/master/pages/core-concepts/module-context.pot`" file was changed. a month ago
None String updated in the repository fedora-docs-l10n/modularity / master/pages/core-concepts/module-context — English	English The name of the context specifically identifies a variant of a module stream. The name of the context is specified by the packager of the module stream. The name of the context should be the same during the whole lifetime of a module stream. If you change the name of an existing context it will automatically be considered as a new context within a module stream and there will be no connection between the new and the old context. This means that the upgrade path will end with the old context. The new context will be its own entity independent of the old context. English Read only The name of the context specifically identifies a variant of a module stream. The name of the context is specified by the packager of the module stream. The name of the context should be the same during the whole lifetime of a module stream. If you change the name of an existing context it will automatically be considered as a new context within a module stream and there will be no connection between the new and the old context. This means that the upgrade path will end with the old context. The new context will be its own entity independent of the old context. a month ago

Browse all language changes

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2022-07-10 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2022-07-10 AND state:<=needs-editing`	Add