This project is obsolete. Please translate https://translate.fedoraproject.org/projects/fedora-docs-l10n-fedora-docs instead.

The translation is temporarily closed for contributions due to maintenance, please come back later.

Source strings

17 Strings 100%
Browse Translate
636 Words 100%
4,056 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
17 636 4,056
All strings Browse Translate Zen
17 636 4,056
Read-only strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary fedora-docs-l10n/fedora-docs-contributing CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/design-ux CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/working-with-translations CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/repo-structure CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/style-guide CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/local-preview CC-BY-SA-3.0 0 0 0 0 2 0 2
master/pages/prerequisites CC-BY-SA-3.0 0 0 0 0 3 0 0
master/pages/git CC-BY-SA-3.0 0 0 0 0 3 0 0
master/pages/markup 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
Browse all components

Overview

Project website pagure.io/fedora-docs-l10n/fedora-docs-contributing
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/fedora-docs-contributing.git
Repository branch master
Last remote commit Update translation files 191fb693
Weblate authored a year ago
Last commit in Weblate Translated using Weblate (Indonesian) 148ddb8d
User avatar arifbudiman authored 10 months ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-fedora-docs-contributing/nav/
File mask po/*/master/pages/contributing-to-release-notes.po
Translation file Download pot/master/pages/contributing-to-release-notes.pot
Last change None
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 17 636 4,056
Translated 100% 17 100% 636 100% 4,056
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 17 100% 636 100% 4,056
Failing checks 0% 0 0% 0 0% 0
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

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 18 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
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

636
Hosted words
17
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
File pot/master/pages/contributing-to-release-notes.pot was added. a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
If you have any questions, xref:ROOT:index.adoc#find-docs[contact Docs on IRC, Matrix, or the forums].
If you have any questions, xref:ROOT:index.adoc#find-docs[contact Docs on IRC, Matrix, or the forums].
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
See also the xref:git.adoc[Git for docs writers] page for more detailed information about working with Fedora Documentation git repositories.
See also the xref:git.adoc[Git for docs writers] page for more detailed information about working with Fedora Documentation git repositories.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
Repeat the above for as many issues as you want.
Repeat the above for as many issues as you want.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
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.
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.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
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. Use the `build.sh` and `preview.sh` scripts in the repository root to preview your changes locally; see the link:https://docs.fedoraproject.org/en-US/fedora-docs/contributing/local-preview/[docs] for specific instructions. 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`.
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. Use the `build.sh` and `preview.sh` scripts in the repository root to preview your changes locally; see the link:https://docs.fedoraproject.org/en-US/fedora-docs/contributing/local-preview/[docs] for specific instructions. 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`.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
Now the workflow diverges based on your Pagure permissions and technical skills:
Now the workflow diverges based on your Pagure permissions and technical skills:
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
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.
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.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
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.
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.
a year ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/fedora-docs-contributing
  2. master/pages/contributing-to-release-notes
  3. English
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.
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.
a year ago
Browse all translation changes