Translation status

17 Strings
5%
Browse Translate
589 Words
1%
3,646 Characters
2%

Strings status

Strings Words Characters
17 589 3,646
All strings Browse Translate Zen
1 6 92
Translated strings Browse Translate Zen
16 583 3,554
Unfinished strings Browse Translate Zen
16 583 3,554
Untranslated strings Browse Translate Zen

Summary

Project website forge.fedoraproject.org
Instructions for translators

Mailing list for translators: trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 4.0 International
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/fedora-docs.git
Repository branch main
Last remote commit Revert migration to main bf2b0072
Rafael Fontenelle authored 06/16/2026
Last commit in Weblate Update translation files 62ea2b09
Hosted Weblate authored 06/16/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-fedora-docs/nav/
File mask po/*/master/pages/contributing-docs/contrib-release-notes.po
Translation file Download po/pt_BR/master/pages/contributing-docs/contrib-release-notes.po
Last change June 16, 2026, 4:34 p.m.
Last change made by None
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
06/16/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 17 589 3,646
Translated 5% 1 1% 6 2% 92
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 94% 16 98% 583 97% 3,554
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource updated
Parsing of the “po/pt_BR/master/pages/contributing-docs/contrib-release-notes.po” file was enforced. 06/16/2026
User avatar webhook:forgejo

Resource updated
File “po/pt_BR/master/pages/contributing-docs/contrib-release-notes.po” was added. 06/16/2026
User avatar webhook:forgejo

String added in the repository
Repeat the above for as many issues as you want.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
If the above sounds like gibberish to you, it’s fine. Just add a comment with your text into the issue, and someone will mark it up and add it to the final document.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
If you can’t see the section where you added your contributions at all, make sure that it’s included in the table of contents in `modules/release-notes/nav.adoc`.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
If you know how to use git and ASCIIDoc, write up the release note and send a pull request against the main repository. Make sure you open the pull request against the correct branch, not `main` - see first step of this procedure for info. (The `main` branch is only used as a template for each new release, so it only contains an empty structure and some pages that do not vary between releases.) Your contributions should go into one of the files in `modules/release-notes/pages/`, which one exactly depends on the contents of the change you’re documenting.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
Now the workflow diverges based on your Pagure permissions and technical skills:
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
Write a release note about the issue. If you’re not sure what exactly a release note looks like, check out some of the link:https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/[previous releases] for inspiration. We don’t want any long, overly technical texts, the release notes are generally meant to highlight changes, not to tell people how to use something.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
Find information about your issue. A lot of them have plenty of info in them already, especially in the Wiki link; if you need more, find out who is responsible for the change (also listed on the Wiki page linked in the issue), and @-mention them in the issue comments or talk to them on IRC/Matrix or via mail. Keep in mind that it’s always better if you try to do research before you ask questions. Note that you might not always be able to reach the owner in a reasonable time frame; in that case just do your best, if something ends up being wrong, we can always update it later.
 
06/16/2026
User avatar webhook:forgejo

String added in the repository
If you claim an issue, but later find out you don’t have time to finish it, remove yourself from the issue ASAP so someone else can pick it up.
 
06/16/2026
Browse all translation changes