Source strings

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

Strings status

Strings Words Characters
19 404 2,615
All strings Browse Translate Zen
19 404 2,615
Read-only strings Browse Translate Zen
1 83 479
Strings with any failing checks Browse Translate Zen
1 83 479
Failing check: Unpluralised Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/package-maintainers
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/package-maintainers.git
Repository branch master
Last remote commit automatic update of pot/po files 006f285
♪ I'm a bot, bot, bot ♪ authored 3 days ago
Last commit in Weblate Update translation files a10f72b
Weblate authored 3 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-package-maintainers/nav/
File mask po/*/master/pages/bug_status.po
Translation file Download pot/master/pages/bug_status.pot
Last change Jan. 4, 2024, 3:27 p.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 19 404 2,615
Translated 100% 19 100% 404 100% 2,615
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 19 100% 404 100% 2,615
Failing checks 5% 1 20% 83 18% 479
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 0 changes 0 changes 0 changes 0 changes 0 changes 20 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
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

404
Hosted words
19
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
File “pot/master/pages/bug_status.pot” was added. 10 months ago
User avatar None

String updated in the repository
The _Priority_ field may be used, at their choice, by maintainers to keep track of the order in which they wish to address bugs in their package(s). This may be done with relation to the severity setting, or by any other method the maintainer chooses, at the maintainer's sole discretion. It may also be entirely ignored, if the maintainer in question does not wish to use it No-one other than the maintainer or team responsible for a particular bug should change this setting.
The _Priority_ field may be used, at their choice, by maintainers to keep track of the order in which they wish to address bugs in their package(s). This may be done with relation to the severity setting, or by any other method the maintainer chooses, at the maintainer's sole discretion. It may also be entirely ignored, if the maintainer in question does not wish to use it No-one other than the maintainer or team responsible for a particular bug should change this setting.
10 months ago
User avatar None

String updated in the repository
Priority
Priority
10 months ago
User avatar None

String updated in the repository
For most packages, most issues are likely to be of _Medium_ severity. These are not hard and fast rules. Use your best judgement in setting the severity field appropriately. There are obvious cases which require the exercise of judgement—for instance, a bug which affects more than just the program in which it occurs, but less than the 'whole system'.
For most packages, most issues are likely to be of _Medium_ severity. These are not hard and fast rules. Use your best judgement in setting the severity field appropriately. There are obvious cases which require the exercise of judgement—for instance, a bug which affects more than just the program in which it occurs, but less than the 'whole system'.
10 months ago
User avatar None

String updated in the repository
The _Urgent_ setting should not usually be used for hardware-specific bugs: a bug which causes the entire distribution to be affected but is restricted to a single specific type of hardware should usually be set to _High_. For instance, if a bug prevents X.org working correctly on a single particular graphics chipset, use the _High_ severity, not _Urgent_.
The _Urgent_ setting should not usually be used for hardware-specific bugs: a bug which causes the entire distribution to be affected but is restricted to a single specific type of hardware should usually be set to _High_. For instance, if a bug prevents X.org working correctly on a single particular graphics chipset, use the _High_ severity, not _Urgent_.
10 months ago
User avatar None

String updated in the repository
_Low_: anything else - cosmetic issues, corner cases with unusual (non-default) configurations, etc.
_Low_: anything else - cosmetic issues, corner cases with unusual (non-default) configurations, etc.
10 months ago
User avatar None

String updated in the repository
_Medium_: a real bug which makes program more difficult to use, at least part of the program is available; possibly workarounds are available
_Medium_: a real bug which makes program more difficult to use, at least part of the program is available; possibly workarounds are available
10 months ago
User avatar None

String updated in the repository
_High_: the bug makes the program in question unusable, or a major packaging guideline violation (license problem, bundled library, etc)
_High_: the bug makes the program in question unusable, or a major packaging guideline violation (license problem, bundled library, etc)
10 months ago
User avatar None

String updated in the repository
_Urgent_: the bug makes whole system unusable (or it is a security bug, which is per definition urgent)
_Urgent_: the bug makes whole system unusable (or it is a security bug, which is per definition urgent)
10 months ago
User avatar None

String updated in the repository
The _Severity_ field is used to indicate the bug's importance. The values for the severity field should be assigned with reference to the following guidance:
The _Severity_ field is used to indicate the bug's importance. The values for the severity field should be assigned with reference to the following guidance:
10 months ago
Browse all translation changes