fedora-docs-l10n/ci/master/pages/faq @ Fedora Weblate

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English CC-BY-SA-3.0		0	0	0	0	0	0	0

Czech CC-BY-SA-3.0	0%	9	278	1,697	9	0	0	0

French CC-BY-SA-3.0	44%	5	260	1,601	4	0	1	0

German CC-BY-SA-3.0		0	0	0	0	0	0	0

Indonesian CC-BY-SA-3.0	0%	9	278	1,697	9	0	1	0

Italian CC-BY-SA-3.0	0%	9	278	1,697	9	0	1	0

Spanish CC-BY-SA-3.0		0	0	0	0	0	0	0

Please sign in to see the alerts.

Summary

Project website	forge.fedoraproject.org
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	`https://forge.fedoraproject.org/localization-docs/ci.git`
Repository branch	master
Last remote commit	automatic update of pot/po files `ce6fb789` ♪ I'm a bot, bot, bot ♪ authored 03/05/2026
Last commit in Weblate	Translated using Weblate (Czech) `6fa4dede` peartown authored 04/09/2026
Weblate repository	`https://translate.fedoraproject.org/git/fedora-docs-l10n-ci/nav/`
File mask	`po/*/master/pages/faq.po`

04/09/2026

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		63		1,946		11,879
Source		9		278		1,697
Translated	49%	31	43%	852	43%	5,187
Needs editing	1%	1	1%	5	1%	18
Read-only	14%	9	14%	278	14%	1,697
Failing checks	0%	0	0%	0	0%	0
Strings with suggestions	4%	3	1%	11	1%	70
Untranslated strings	49%	31	55%	1,089	56%	6,674

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

1,946

Hosted words

Hosted strings

49%

Translated

Contributors

Components

Languages

Translations

Screenshots

and previous 30 days

Trends of last 30 days

+14%

Hosted words

+100%

+14%

Hosted strings

+100%

−8%

Translated

+57%

—

Contributors

+100%

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>="1 month ago" 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:>="1 month ago" AND state:<=needs-editing`	Add
Strings changed in the past two weeks	`changed:>="2 weeks ago"`	Add
Automatically translated strings	`is:automatically-translated`	Add
Translated strings in a certain language	`is:translated AND language: en`	Add

None

Resource updated

File “po/cs/master/pages/faq.po” was added. 04/09/2026

None

String added in the repository

English

There are several options where to store the test code. Here are some of the most important advantages and disadvantages of each approach: Test code in *dist git rpms namespace* is branched together with spec files and thus can closely mirror functionality. Tests used across multiple components or OS releases can be stored in the *dist git test namespace* to share the test code and minimize maintenance. Fetching tests from an *upstream project git* is also possible and supported by standard-test-roles (source role). In order to prevent unexpected test failures caused by upstream changes it is sometimes better to reference a specific commit rather then branch. Tests enabled in *make check* are executed in a different environment (buildroot). This is good for unit tests but not recommended for new Tier 1 test coverage. Enable 'make check' in tests.yml only if testing installed rpm.