Summary

Project website gitlab.com
Instructions for translators

This project host translation for the new fedoraproject.org website. More information can be found on the GitLab project & Fedora Chat: https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0 https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org
Project maintainers1 User avatar glb
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 monolingual files.
  • The translation base language can not be edited.

Reviews are disabled for this language. Review setting: Project settings.

All translation states, including those needing editing, are eligible to be written to the translation file.

Learn how to customize the workflow for this language.

Source code repository https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0.git
Repository branch develop
Last remote commit use the new cms download section configuration 922ebc8a
User avatar glb authored 10/04/2026
Last commit in Weblate use the new cms download section configuration 922ebc8a
User avatar glb authored 10/04/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-websites-3-0/fedoraproject-org/
File mask locales/*.json
Monolingual base language file locales/en.json
Translation file Download locales/fur.json
Last change Oct. 4, 2026, 11:55 p.m.
Last change made by GitLab webhook
Language Friulian
Language code fur
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 36,578
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
10/05/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,570 22,911 152,864
Translated 34% 541 25% 5,880 26% 40,411
Needs editing 1% 1 1% 10 1% 60
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 42 1% 163 1% 1,560
Strings with suggestions 23% 375 21% 4,830 21% 32,398
Untranslated strings 65% 1,028 74% 17,021 73% 112,393
Last 12 months Previous

Activity in last 12 months

54 changes 33 changes 4 changes 32 changes 6 changes 94 changes 28 changes 37 changes 4 changes 139 changes 71 changes 27 changes 36 changes 44 changes 8 changes 23 changes 4 changes 51 changes 56 changes 120 changes 41 changes 150 changes 12 changes 80 changes
OctNovDecJanFebMarAprMayJunJulAugSep

Quick numbers

22,911
Hosted words
1,570
Hosted strings
34%
Translated
4
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
−1%
+3%
Hosted strings
−1%
−1%
Translated
+1%
—
Contributors
—
User avatar webhook:gitlab

Resource updated
The “locales/en.json” file was changed. 10/04/2026
User avatar webhook:gitlab

String added in the repository
For RISC-V systems
 
For RISC-V systems
10/04/2026
User avatar webhook:gitlab

String added in the repository
Bootable Container
 
Bootable Container
10/04/2026
User avatar webhook:gitlab

Resource updated
The “locales/en.json” file was changed. 09/29/2026
User avatar webhook:gitlab

Resource updated
The “locales/en.json” file was changed. 09/13/2026
User avatar webhook:gitlab

String added in the repository
Privacy Policy
 
Privacy Policy
09/13/2026
User avatar webhook:gitlab

String added in the repository
How to Structure Your Article
 
How to Structure Your Article
09/13/2026
User avatar webhook:gitlab

String added in the repository
Fedora Magazine follows the privacy practices described in the [Privacy Statement for the Fedora Project](https://docs.fedoraproject.org/en-US/legal/privacy/).
 
Fedora Magazine follows the privacy practices described in the [Privacy Statement for the Fedora Project](https://docs.fedoraproject.org/en-US/legal/privacy/).
09/13/2026
User avatar webhook:gitlab

String added in the repository
Fedora Magazine Terms of Use
 
Fedora Magazine Terms of Use
09/13/2026
User avatar webhook:gitlab

String added in the repository
**HOW TO USE THIS PAGE**: Copy the template below to your article. Replace the sections and headings with your own content, following this structure as a guide.

## Introduction

Explain one or two situations in which a user would need to use the process you will describe. Don’t explain the process here. The point of the introduction is to _introduce_ the concepts the reader will put to use later, and to explain _why_ it’s even useful to begin with.

Here’s a short example for an article about setting the hostname: “The computer’s hostname helps distinguish the system on a network. If you have appropriate privileges, you can set your system’s hostname to something that helps you identify it in your home or office network.”

If there’s anything the user needs to know in order to use the process, describe it here. For instance, in the hostname example, you would describe that only lowercase letters a-z, numerals 0-9, or the dash “-” may appear in a hostname. You might also tell them whether they need to be on a specific Fedora edition or version.

## Running the Most Common Process

Describe the process one step at a time. Describe the simplest and most common usage first. Assume the reader will try the first process they see.

Use a graphical interface as the first and most common process. Document the default installation wherever possible. Use a screenshot, and don’t use your own customized user account. Use a fresh user account so it has a non-customized and stock appearance.

You may follow this case with a command-line equivalent in an additional section.

## Running a More Complex or Less Common Process

You can describe a less common process as well. In this case, describe why it is useful. Be honest with yourself about whether this process is actually useful. Don’t use the article as a way of showing off your deep knowledge of a tool.

## Conclusion

If there are common references, you can include them at the bottom. Do not point to dated information. Only use resources that are unlikely to change, are undated, or are well maintained.
 
**HOW TO USE THIS PAGE**: Copy the template below to your article. Replace the sections and headings with your own content, following this structure as a guide.

## Introduction

Explain one or two situations in which a user would need to use the process you will describe. Don’t explain the process here. The point of the introduction is to _introduce_ the concepts the reader will put to use later, and to explain _why_ it’s even useful to begin with.

Here’s a short example for an article about setting the hostname: “The computer’s hostname helps distinguish the system on a network. If you have appropriate privileges, you can set your system’s hostname to something that helps you identify it in your home or office network.”

If there’s anything the user needs to know in order to use the process, describe it here. For instance, in the hostname example, you would describe that only lowercase letters a-z, numerals 0-9, or the dash “-” may appear in a hostname. You might also tell them whether they need to be on a specific Fedora edition or version.

## Running the Most Common Process

Describe the process one step at a time. Describe the simplest and most common usage first. Assume the reader will try the first process they see.

Use a graphical interface as the first and most common process. Document the default installation wherever possible. Use a screenshot, and don’t use your own customized user account. Use a fresh user account so it has a non-customized and stock appearance.

You may follow this case with a command-line equivalent in an additional section.

## Running a More Complex or Less Common Process

You can describe a less common process as well. In this case, describe why it is useful. Be honest with yourself about whether this process is actually useful. Don’t use the article as a way of showing off your deep knowledge of a tool.

## Conclusion

If there are common references, you can include them at the bottom. Do not point to dated information. Only use resources that are unlikely to change, are undated, or are well maintained.
09/13/2026
Browse all translation changes