The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.

Translation status

61 Strings 0%
Browse Translate
1,732 Words 0%
13,381 Characters 0%

Strings status

Strings Words Characters
61 1,732 13,381
All strings Browse Translate Zen
61 1,732 13,381
Unfinished strings Browse Translate Zen
61 1,732 13,381
Untranslated strings Browse Translate Zen

Summary

Project website pagure.io
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 e989df043
♪ I'm a bot, bot, bot ♪ authored a month ago
Last commit in Weblate Translated using Weblate (Spanish) 69a0268f3
Weblate Translation Memory authored 10 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 po/ja/master/pages/ReviewGuidelines.po
Last change May 8, 2025, 10:39 p.m.
Last change made by None
Language Japanese
Language code ja
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 117,608,755
Number of plurals 1
Plural type None
Plurals
Plural formula 0
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 1,732 13,381
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% 61 100% 1,732 100% 13,381
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 41 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 36 changes 0 changes 0 changes 58 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

1,732
Hosted words
61
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

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

String added in the repository
The following exceptions apply to the review process linked above
 
a month ago
User avatar None

String added in the repository
Contributors and reviewers MUST follow the https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/[Package Review Process], with the exceptions listed in the next section
 
a month ago
User avatar None

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

String added in the repository
Please also note that while you may actually be able to build a package because all of its build-time dependencies are met, the package may still be non-installable (and thus useless) if its _runtime_ dependencies are not met. A package *MUST* not be built if any of its runtime dependencies are unsatisfied.
 
a month ago
User avatar None

String added in the repository
However, please keep in mind that you cannot do koji builds unless all of the build dependencies are met (because you cannot provide additional dependencies to koji) and when the time comes to build these packages, they must be built in order and you must wait between builds for the dependencies to make it into the appropriate branch of the distribution. This can be automated using side tags and chain builds.
 
a month ago
User avatar None

String added in the repository
It is often useful to submit a package for review along with its dependencies in separate tickets. As long as the submitter sets up the _Depends on:_ and _Blocks:_ fields in BugZilla properly, this is not an issue, and it is perfectly possible to review these packages before the full dependency chain is in the distribution (by maintaining a local repository, building and installing the packages locally, or maintaining a COPR).
 
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].
 
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].
 
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].
 
a month ago
Browse all translation changes