Source strings

55 Strings 100%
Browse Translate
1,685 Words 100%
12,853 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
55 1,685 12,853
All strings Browse Translate Zen
55 1,685 12,853
Read-only strings Browse Translate Zen
40 1,241 9,869
Strings with any failing checks Browse Translate Zen
2 73 563
Failing check: Unpluralised Browse Translate Zen
40 1,241 9,869
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 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/ReviewGuidelines.po
Translation file Download pot/master/pages/ReviewGuidelines.pot
Last change Sept. 9, 2024, 10:30 p.m.
Last author None
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 55 1,685 12,853
Translated 100% 55 100% 1,685 100% 12,853
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 55 100% 1,685 100% 12,853
Failing checks 72% 40 73% 1,241 76% 9,869
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 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 36 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 41 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

1,685
Hosted words
55
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

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

String added in the repository
[[man-pages]] *SHOULD*: your package should contain man pages for binaries/scripts. If it doesn't, work with upstream to add them where they make sense. See xref:index.adoc#_manpages[Packaging Guidelines: Manpages] +
[[man-pages]] *SHOULD*: your package should contain man pages for binaries/scripts. If it doesn't, work with upstream to add them where they make sense. See xref:index.adoc#_manpages[Packaging Guidelines: Manpages] +
a month ago
User avatar None

String added in the repository
[[file-requires]] *SHOULD*: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself. See xref:index.adoc#_file_and_directory_dependencies[Packaging Guidelines: File and Directory Dependencies] +
[[file-requires]] *SHOULD*: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself. See xref:index.adoc#_file_and_directory_dependencies[Packaging Guidelines: File and Directory Dependencies] +
a month ago
User avatar None

String added in the repository
[[pkgconfig-in-devel]] *SHOULD*: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb. See xref:index.adoc#_pkgconfig_files_foo_pc[Packaging Guidelines: Pkgconfig Files] +
[[pkgconfig-in-devel]] *SHOULD*: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb. See xref:index.adoc#_pkgconfig_files_foo_pc[Packaging Guidelines: Pkgconfig Files] +
a month ago
User avatar None

String added in the repository
[[subpackage-versioned-requires]] *SHOULD*: Usually, subpackages other than devel should require the base package using a fully versioned dependency. See xref:index.adoc#_requiring_base_package[Packaging Guidelines: Requiring Base Package] +
[[subpackage-versioned-requires]] *SHOULD*: Usually, subpackages other than devel should require the base package using a fully versioned dependency. See xref:index.adoc#_requiring_base_package[Packaging Guidelines: Requiring Base Package] +
a month ago
User avatar None

String added in the repository
[[sane-scriplets]] *SHOULD*: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity. See xref:index.adoc#_scriptlets[Packaging Guidelines: Scriptlets] +
[[sane-scriplets]] *SHOULD*: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity. See xref:index.adoc#_scriptlets[Packaging Guidelines: Scriptlets] +
a month ago
User avatar None

String added in the repository
[[functions-as-described]] *SHOULD*: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. +
[[functions-as-described]] *SHOULD*: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. +
a month ago
User avatar None

String added in the repository
[[supports-all-architectures]] *SHOULD*: The package should compile and build into binary rpms on all supported architectures. See xref:index.adoc#_architecture_support[Packaging Guidelines: Architecture Support] +
[[supports-all-architectures]] *SHOULD*: The package should compile and build into binary rpms on all supported architectures. See xref:index.adoc#_architecture_support[Packaging Guidelines: Architecture Support] +
a month ago
User avatar None

String added in the repository
[[builds-in-mock]] *SHOULD*: The reviewer should test that the package builds in mock. See https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock to test package builds] +
[[builds-in-mock]] *SHOULD*: The reviewer should test that the package builds in mock. See https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock to test package builds] +
a month ago
User avatar None

String added in the repository
[[upstream-license-file]] *SHOULD*: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it. See xref:LicensingGuidelines.adoc#_license_text[Licensing Guidelines: License Text] +
[[upstream-license-file]] *SHOULD*: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it. See xref:LicensingGuidelines.adoc#_license_text[Licensing Guidelines: License Text] +
a month ago
Browse all translation changes