Translation status

30 Strings 0%
Browse Translate
1,101 Words 0%
7,082 Characters 0%

Strings status

Strings Words Characters
30 1,101 7,082
All strings Browse Translate Zen
30 1,101 7,082
Unfinished strings Browse Translate Zen
30 1,101 7,082
Untranslated strings Browse Translate Zen
30 1,101 7,082
Unfinished strings without suggestions 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 a233f9785
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Last commit in Weblate Translated using Weblate (Spanish) 76319285b
User avatar vareli authored 4 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/LicensingGuidelines.po
Translation file Download po/fr/master/pages/LicensingGuidelines.po
Last change Aug. 22, 2023, 10:01 p.m.
Last author None
a week ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 30 1,101 7,082
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% 30 100% 1,101 100% 7,082
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 8 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

1,101
Hosted words
30
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

Resource updated
The “po/fr/master/pages/LicensingGuidelines.po” file was changed. a year ago
User avatar None

String updated in the repository
However, if a subpackage is independent of any base package (it does not require it, either implicitly or explicitly), it must include copies of any license texts (as present in the source) which are applicable to the files contained within the subpackage.
 
a year ago
User avatar None

String updated in the repository
If a subpackage is dependent (either implicitly or explicitly) upon a base package (where a base package is defined as a resulting binary package from the same source RPM which contains the appropriate license texts as `+%license+`), it is not necessary for that subpackage to also include those license texts as `+%license+`.
 
a year ago
User avatar None

String updated in the repository
If the source package does not include the text of the license(s), the packager should contact upstream and encourage them to correct this mistake.
 
a year ago
User avatar None

String updated in the repository
Note also that it is acceptable for license files to be so flagged in a list which is generated programmatically and included using `+%files -f+`. This tagging is often done automatically by macros and not directly visible to the packager. What is important is not the visible presence of the `+%license+` directive but instead that all relevant license files included in a package appear when using `+rpm -q --licensefiles+`.
 
a year ago
User avatar None

String updated in the repository
Note that the path so flagged can be either relative or absolute. For relative paths, RPM will automatically copy them from the source directory into a subdirectory of `+%_defaultlicensedir+` (`+/usr/share/licenses+`). For absolute paths, RPM will simply tag the file in the final package as being a license file.
 
a year ago
User avatar None

String updated in the repository
If the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in the `+%files+` list flagged with the `+%license+` directive.
 
a year ago
User avatar None

Resource updated
The “po/fr/master/pages/LicensingGuidelines.po” file was changed. 2 years ago
User avatar None

String updated in the repository
For more information on what to do if you find a license that is not on the Fedora list, does not have a corresponding SPDX license identifier or expression, or other process questions, see xref:legal::license-review-process.adoc[License Review Process].
 
2 years ago
User avatar None

String updated in the repository
xref:legal::license-field.adoc[License: field in Spec file] contains examples and further explanations for using SPDX expressions in the `License:` field.
 
2 years ago
Browse all translation changes