Source strings

114 Strings 100%
Browse Translate
2,889 Words 100%
19,860 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
114 2,889 19,860
All strings Browse Translate Zen
114 2,889 19,860
Read-only strings Browse Translate Zen
1 1 8
Strings with any failing checks Browse Translate Zen
1 1 8
Failing check: Multiple failing checks Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
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/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files 7660837d1
♪ I'm a bot, bot, bot ♪ authored 3 hours ago
Last commit in Weblate Update translation files 59fcabe17
Weblate authored 3 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Versioning.po
Translation file Download pot/master/pages/Versioning.pot
Last change Nov. 21, 2024, 10:25 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Number of speakers 1,728,900,209
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
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 114 2,889 19,860
Translated 100% 114 100% 2,889 100% 19,860
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 114 100% 2,889 100% 19,860
Failing checks 1% 1 1% 1 1% 8
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 1 change 0 changes 1 change 0 changes 2 changes 0 changes 0 changes 0 changes 26 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

2,889
Hosted words
114
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “pot/master/pages/Versioning.pot” file was changed. 4 weeks ago
User avatar None

String added in the repository
`+<scm><number>.<revision>`
`+<scm><number>.<revision>`
4 weeks ago
User avatar None

String added in the repository
`+<scm><date>.<revision>`
`+<scm><date>.<revision>`
4 weeks ago
User avatar None

Resource updated
The “pot/master/pages/Versioning.pot” file was changed. a year ago
User avatar None

String updated in the repository
The method described in this section is deprecated, but **may** be used. As mentioned in the xref:_handling_non_sorting_versions_with_tilde_dot_and_caret[Handling non-sorting versions with tilde, dot, and caret] section above, this method is recommended for packages with complex versioning when supporting RHEL7 and other systems with old rpm versions.
The method described in this section is deprecated, but **may** be used. As mentioned in the xref:_handling_non_sorting_versions_with_tilde_dot_and_caret[Handling non-sorting versions with tilde, dot, and caret] section above, this method is recommended for packages with complex versioning when supporting RHEL7 and other systems with old rpm versions.
a year ago
User avatar None

Resource updated
The “pot/master/pages/Versioning.pot” file was changed. a year ago
User avatar None

String updated in the repository
In the situation described in <<Only an old branch needs a change>>, you **may** adjust the `+Release+` by appending a number *after* the dist tag, creating a E-V-R for F{CURRENTVER} that still compares lower than the one in F{NEXTVER}. Set `+<minorbump>+` to an in integer beginning with '1' and increase it by one for each minor bump you need to do. Remove `+<minorbump>+` once you are able to increase the package release normally without introducing ordering issues.
In the situation described in <<Only an old branch needs a change>>, you **may** adjust the `+Release+` by appending a number *after* the dist tag, creating a E-V-R for F{CURRENTVER} that still compares lower than the one in F{NEXTVER}. Set `+<minorbump>+` to an in integer beginning with '1' and increase it by one for each minor bump you need to do. Remove `+<minorbump>+` once you are able to increase the package release normally without introducing ordering issues.
a year ago
User avatar None

String updated in the repository
Rebuilds in older branches using `<minorbump>`
Rebuilds in older branches using `<minorbump>`
a year ago
User avatar None

String updated in the repository
Note that the dist tag is supplied by other portions of the system and may in some circumstances contain additional structure, including tildes. As this is not under the control of the packager, that structure is not covered here. The packager **must** simply include `+%{?dist}+` verbatim as indicated above.
Note that the dist tag is supplied by other portions of the system and may in some circumstances contain additional structure, including tildes. As this is not under the control of the packager, that structure is not covered here. The packager **must** simply include `+%{?dist}+` verbatim as indicated above.
a year ago
User avatar None

String updated in the repository
In this method, `+%autorelease+` is not used, and the `Release` field must be managed manually.
In this method, `+%autorelease+` is not used, and the `Release` field must be managed manually.
a year ago
Browse all translation changes