Overview

Project website pagure.io/fedora-docs-l10n/fedora-docs
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.git
Repository branch master
Last remote commit automatic update of pot/po files 0561ca79
♪ I'm a bot, bot, bot ♪ authored yesterday
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/it/master/pages/contributing-docs/contrib-release-notes.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 17 589 3,646
Translated 0% 0 0% 0 0% 0
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 100% 17 100% 589 100% 3,646
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

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

Trends of last 30 days

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

New strings to translate

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

17 new strings to translate appeared to the translation. 11 months ago
User avatar None

Resource update

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

File po/it/master/pages/contributing-docs/contrib-release-notes.po was added. 11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

Repeat the above for as many issues as you want.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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`.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

Now the workflow diverges based on your Pagure permissions and technical skills:
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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.
 
11 months ago
User avatar None

String updated in the repository

fedora-docs-l10n/fedora-docs / master/pages/contributing-docs/contrib-release-notes — Italian

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.
 
11 months ago
Browse all translation changes