[ancient-date]
severity = normal
certainty = certain
description =
 The date refers to the time before the first GNU gettext release.
 As such, it's extremely unlikely to be correct.
references =
 https://git.savannah.gnu.org/cgit/gettext.git/tree/ChangeLog.0#n1767

[arithmetic-error-in-plural-forms]
severity = serious
certainty = possible
description =
 Computing a plural form value triggers division by zero or integer overflow.
 This normally indicates an error in the plural form expression.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[arithmetic-error-in-unused-plural-forms]
severity = normal
certainty = possible
description =
 Computing a plural form value triggers division by zero or integer overflow.
 (But there are no translated messages which use plural forms.)
 This normally indicates an error in the plural form expression.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[boilerplate-in-content-type]
severity = important
certainty = certain
description =
 The Content-Type header field contains xgettext boilerplate.
 It should be in the form ``text/plain; charset=``\ *encoding*.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files

[boilerplate-in-date]
severity = normal
certainty = certain
description =
 The date header field contains xgettext boilerplate.
 The date format should be ``YYYY-MM-DD hh:mm+ZZzz``,
 e.g. ``2011-11-05 10:14+0100``.

[boilerplate-in-initial-comments]
severity = minor
certainty = possible
description =
 The initial comments contain xgettext or msginit boilerplate.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[boilerplate-in-language-team]
severity = minor
certainty = certain
description =
 The Language-Team header field contains xgettext boilerplate.
 It should contain English name of the language,
 and the email address or homepage URL of the language team.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[boilerplate-in-last-translator]
severity = normal
certainty = certain
description =
 The Last-Translator header field contains xgettext boilerplate.
 It should contain the last translator's name and email address.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[boilerplate-in-project-id-version]
severity = minor
certainty = certain
description =
 The Project-Id-Version header field contains xgettext boilerplate.
 It should contain the name and the version of the package.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[boilerplate-in-report-msgid-bugs-to]
severity = normal
certainty = certain
description =
 The Report-Msgid-Bugs-To header field contains xgettext boilerplate.
 It should contain an email address
 or URL where one can report bugs in the untranslated strings.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[broken-encoding]
severity = serious
certainty = possible
description =
 Header fields and messages contained by this file couldn't be decoded to Unicode.
 The usual cause of this is incorrect or missing encoding declaration.
 .
 Note that in the absence of encoding declaration,
 i18nspector assumes ASCII encoding.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files
 https://tools.ietf.org/html/rfc2045#section-5

[c-format-string-argument-type-mismatch]
severity = serious
certainty = possible
description =
 There's a type mismatch between a C format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``;
 or between a C format argument in ``msgstr`` and ``msgid``;
 or between a C format argument in ``msgstr[``\ *N*\ ``]`` and corresponding ``msgid`` or ``msgid_plural``.
references =
 printf(3)
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[c-format-string-error]
severity = serious
certainty = possible
description =
 A C format string could not be parsed.
references =
 printf(3)

[c-format-string-excess-arguments]
severity = serious
certainty = possible
description =
 A C format string for ``msgid`` consumes more arguments than ``msgid_plural``;
 or ``msgstr`` consumes more arguments than ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` consumes more arguments than corresponding ``msgid`` or ``msgid_plural``.
references =
 printf(3)
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[c-format-string-missing-arguments]
severity = serious
certainty = possible
description =
 A C format string for ``msgid`` consumes fewer arguments than ``msgid_plural``;
 or ``msgstr`` consumes fewer arguments than ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` consumes fewer arguments than corresponding ``msgid`` or ``msgid_plural``.
 .
 Note that in some languages,
 the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on.
 Take this Serbian translation for example::
 .
 .  Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
 .  ...
 .  msgid "one byte"
 .  msgid_plural "%d bytes"
 .  msgstr[0] "%d bajt"
 .  msgstr[1] "%d bajta"
 .  msgstr[2] "%d bajtova"
 .
 Here ``%d`` should not be replaced with the spelled-out form ``jedan``.
 Either ``%d`` should be kept, or the Plural-Forms expression should be amended,
 so that there is a special case for n=1::
 .
 .  Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2
 .  ...
 .  msgid "one byte"
 .  msgid_plural "%d bytes"
 .  msgstr[0] "%d bajt"
 .  msgstr[1] "%d bajta"
 .  msgstr[2] "%d bajtova"
 .  msgstr[3] "jedan bajt"
references =
 printf(3)
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[c-format-string-non-portable-conversion]
severity = pedantic
certainty = possible
description =
 A C format string uses a conversion specified or length modifier,
 for which a more portable replacement exists:
 .
 * For integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``), use the ``ll`` length modifier instead of ``L`` or ``q``.
 * For floating-point conversions (``%a``, ``%A``, ``%e``, ``%E``, ``%f``, ``%F``, ``%g``, and ``%G``), don't use the ``l`` length modifier.
 * Use the ``z`` length modifier instead of ``Z``.
 * Use ``%lc`` instead of ``%C``.
 * Use ``%ls`` instead of ``%S``.
references =
 printf(3)

[c-format-string-redundant-flag]
severity = pedantic
certainty = possible
description =
 A C format string includes a redundant character flag.
 Either it's a duplicate, or it has no effect:
 .
 * The ``+`` flag overrides the *space* flag.
 * The ``-`` flag overrides the ``0`` flag.
 * If a precision is given, the ``0`` flag has no effect on integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``).
references =
 printf(3)

[codomain-error-in-plural-forms]
severity = serious
certainty = certain
description =
 Either a plural form value is outside the declared range,
 or some values within the declared range can never be reached.
 This normally indicates an error in the plural form expression.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[codomain-error-in-unused-plural-forms]
severity = normal
certainty = certain
description =
 Either a plural form value is outside the declared range,
 or some values within the declared range can never be reached.
 (But there are no translated messages which use plural forms.)
 This normally indicates an error in the plural form expression.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[conflict-marker-in-header-entry]
severity = serious
certainty = certain
description =
 The header contains a conflict marker (``#-#-#-#-#`` *…* ``#-#-#-#-#``).
 The conflict will have to be resolved manually.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Creating-Compendia.html#Creating-Compendia

[conflict-marker-in-translation]
severity = serious
certainty = possible
description =
 One of the translated messages appear to contain a conflict marker
 (``#-#-#-#-#`` *…* ``#-#-#-#-#``).
 The conflict will have to be resolved manually.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Creating-Compendia.html#Creating-Compendia

[conflicting-message-flags]
severity = important
certainty = possible
description =
 Two flags with conflicting meanings are associated with one of the messages.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[date-from-future]
severity = normal
certainty = certain
description =
 The date refers to the future.
 As such, it's extremely unlikely to be correct.

[distant-header-entry]
severity = important
certainty = certain
description =
 The header entry in this file is preceded by other entries.
 The header entry should be always the first one.

[duplicate-flag-for-header-entry]
severity = minor
certainty = certain
description =
 Multiple identical flags are associated with the header entry.

[duplicate-header-entry]
severity = serious
certainty = certain
description =
 This file contains multiple header entries.

[duplicate-header-field]
severity = minor
certainty = wild-guess
description =
 This file contains multiple header fields of the same name.

[duplicate-header-field-content-transfer-encoding]
severity = pedantic
certainty = certain
description =
 This file contains multiple Content-Transfer-Encoding header fields.

[duplicate-header-field-content-type]
severity = serious
certainty = certain
description =
 This file contains multiple Content-Type header fields.

[duplicate-header-field-date]
severity = normal
certainty = certain
description =
 This file contains multiple date header fields of the same name.

[duplicate-header-field-language]
severity = important
certainty = certain
description =
 This file contains multiple Language header fields.

[duplicate-header-field-language-team]
severity = normal
certainty = certain
description =
 This file contains multiple Language-Team header fields.

[duplicate-header-field-last-translator]
severity = normal
certainty = certain
description =
 This file contains multiple Last-Translator header fields.

[duplicate-header-field-mime-version]
severity = pedantic
certainty = certain
description =
 This file contains multiple MIME-Version header fields.

[duplicate-header-field-plural-forms]
severity = serious
certainty = certain
description =
 This file contains multiple Plural-Forms header fields.

[duplicate-header-field-project-id-version]
severity = minor
certainty = certain
description =
 This file contains multiple Project-Id-Version header fields.

[duplicate-header-field-report-msgid-bugs-to]
severity = normal
certainty = certain
description =
 This file contains multiple Report-Msgid-Bugs-To header fields.

[duplicate-header-field-x-poedit]
severity = normal
certainty = certain
description =
 This file contains multiple X-Poedit-*\** header fields.

[duplicate-message-definition]
severity = serious
certainty = certain
description =
 This file contains multiple definitions of the same message.

[duplicate-message-flag]
severity = minor
certainty = certain
description =
 Multiple identical flags are associated with one of the messages.

[empty-file]
severity = normal
certainty = certain
description =
 This file doesn't contain any messages.

[empty-msgid-message-with-plural-forms]
severity = serious
certainty = certain
description =
 The message with empty msgid contains plural forms.
 Such messages are reserved by GNU gettext for header entries,
 and your code should not call ``ngettext("", …)``.

[empty-msgid-message-with-source-code-references]
severity = serious
certainty = possible
description =
 The message with empty msgid contains plural forms.
 Such messages are reserved by GNU gettext for header entries,
 and your code should not call ``gettext("")``.

[encoding-in-language-header-field]
severity = minor
certainty = certain
description =
 The language header field contains encoding declaration.
 Such information shouldn't be included in this field.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[fuzzy-header-entry]
severity = pedantic
certainty = certain
description =
 The header entry is marked as fuzzy.
 For compatibility with very old (<< 0.11) **msgfmt**\ (1) versions,
 which didn't support fuzzy header entries, it shouldn't be marked as such.
references =
 https://git.savannah.gnu.org/cgit/gettext.git/tree/NEWS?id=v0.11#n44

[inconsistent-leading-newlines]
severity = important
certainty = possible
description =
 Some strings in an entry start with a newline, but some don't.
 Either all of them should start with a newline, or none of them should.

[inconsistent-number-of-plural-forms]
severity = serious
certainty = certain
description =
 Number of plural forms in a message definition doesn't match number of plural forms declared in another message definition.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[inconsistent-trailing-newlines]
severity = important
certainty = possible
description =
 Some strings in an entry end with a newline, but some don't.
 Either all of them should end with a newline, or none of them should.

[incorrect-number-of-plural-forms]
severity = serious
certainty = certain
description =
 Number of plural forms in a message definition doesn't match number of plural forms declared in the header.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[invalid-content-transfer-encoding]
severity = pedantic
certainty = certain
description =
 Value of the Content-Transfer-Encoding header field is invalid.
 It should be ``8bit``.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html
 https://tools.ietf.org/html/rfc2045#section-6.1

[invalid-content-type]
severity = important
certainty = possible
description =
 Value of the Content-Type header field should is invalid.
 It should be in the form ``text/plain; charset=``\ *encoding*.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files
 https://tools.ietf.org/html/rfc2045#section-5

[invalid-date]
severity = normal
certainty = certain
description =
 The date is invalid or in an invalid format.
 The format should be ``YYYY-MM-DD hh:mm+ZZzz``,
 e.g. ``2011-11-05 10:14+0100``.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[invalid-language]
severity = important
certainty = possible
description =
 The Language header field couldn't be parsed,
 or it contains an unknown language.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[invalid-language-team]
severity = normal
certainty = possible
description =
 The Language-Team header field contains an e-mail address
 that uses a reserved domain name,
 or a partially qualified domain name.
references =
 https://tools.ietf.org/html/rfc2606

[invalid-last-translator]
severity = normal
certainty = possible
description =
 The Last-Translator header field could neither be parsed as an e-mail,
 or the e-mail address uses a reserved domain name,
 or a partially qualified domain name.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html
 https://tools.ietf.org/html/rfc2606

[invalid-mime-version]
severity = pedantic
certainty = certain
description =
 Value of the MIME-Version header field is invalid.
 It should be ``1.0``.
references =
 https://tools.ietf.org/html/rfc2045#section-4

[invalid-mo-file]
severity = serious
certainty = certain
description =
 This file couldn't be parsed a MO file.

[invalid-range-flag]
severity = important
certainty = certain
description =
 A ``range:`` flag couldn't be parsed, or the designated range contained fewer than two numbers.
 The syntax is ``range:``\  *min*\ ``..``\ *max*, where both values are non-negative integers.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[invalid-report-msgid-bugs-to]
severity = normal
certainty = possible
description =
 The Report-Msgid-Bugs-To header field could neither be parsed as an e-mail nor as a URL,
 or the e-mail address uses a reserved domain name,
 or a partially qualified domain name.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html
 https://tools.ietf.org/html/rfc2606

[language-disparity]
severity = normal
certainty = possible
description =
 Language of this file has been declared in multiple places,
 but the declarations don't match.

[language-team-equal-to-last-translator]
severity = minor
certainty = possible
description =
 Language-Team and Last-Translator header fields contain the same e-mail address.

[language-variant-does-not-affect-translation]
severity = minor
certainty = possible
description =
 The Language header field contains a variant designator that is not relevant for the message translation.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[leading-junk-in-plural-forms]
severity = important
certainty = certain
description =
 The Plural-Forms header field contains unexpected text before the ``nplurals=`` string.
 .
 GNU gettext runtime ignores such leading junk,
 but other header parsers might be less liberal in what they accept.

[malformed-xml]
severity = serious
certainty = possible
description =
 The original string or the translated string contains an XML fragment,
 which is not well-formed.
references =
 https://www.w3.org/TR/REC-xml/#sec-well-formed

[no-content-transfer-encoding-header-field]
severity = pedantic
certainty = certain
description =
 The Content-Transfer-Encoding header field doesn't exist.
 It should be set to ``8bit``.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html
 https://tools.ietf.org/html/rfc2045#section-6.1

[no-content-type-header-field]
severity = important
certainty = certain
description =
 The Content-Type header field doesn't exist.
 It should be set to ``text/plain; charset=``\ *encoding*.
 .
 Note that in the absence of encoding declaration,
 i18nspector assumes ASCII encoding.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files
 https://tools.ietf.org/html/rfc2045#section-5

[no-date-header-field]
severity = minor
certainty = certain
description =
 The date header field doesn't exist.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-language-header-field]
severity = pedantic
certainty = certain
description =
 The Language header field doesn't exist.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-language-team-header-field]
severity = pedantic
certainty = certain
description =
 The Language-Team header field does not exist.
 It should contain English name of the language,
 and the email address or homepage URL of the language team.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-last-translator-header-field]
severity = normal
certainty = certain
description =
 The Last-Translator header field doesn't exist.
 It should contain the last translator's name and email address.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-mime-version-header-field]
severity = pedantic
certainty = certain
description =
 The MIME-Version header field doesn't exist.
 It should be to set to ``1.0``.
references =
 https://tools.ietf.org/html/rfc2045#section-4

[no-package-name-in-project-id-version]
severity = minor
certainty = possible
description =
 The Project-Id-Version header field doesn't appear to contain any name.
 It should contain both the name and the version of the package.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-plural-forms-header-field]
severity = minor
certainty = certain
description =
 The Plural-Forms header field does not exist,
 even though some of the messages use plural forms
 (although none of them have been translated).
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[no-project-id-version-header-field]
severity = minor
certainty = certain
description =
 The Project-Id-Version header field does not exist.
 It should contain the name and the version of the package.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-report-msgid-bugs-to-header-field]
severity = normal
certainty = certain
description =
 The Report-Msgid-Bugs-To header field does not exist or it is empty.
 It should contain an email address or URL where one can report bugs in the untranslated strings.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[no-required-plural-forms-header-field]
severity = serious
certainty = certain
description =
 The Plural-Forms header field does not exist,
 even though some of the translated messages use plural forms.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[no-version-in-project-id-version]
severity = pedantic
certainty = possible
description =
 The Project-Id-Version header field doesn't appear to contain any version.
 It should contain both the name and the version of the package.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html

[non-ascii-compatible-encoding]
severity = serious
certainty = certain
description =
 This file uses an encoding that is not compatible with ASCII.

[non-portable-encoding]
severity = important
certainty = certain
description =
 This file uses an encoding that is not widely supported by software.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-list

[os-error]
severity = serious
certainty = certain
description =
 An input/output error or another operating system error occurred while checking this file.

[partially-translated-message]
severity = serious
certainty = possible
description =
 Translation is missing for some plural forms of a message.

[perl-brace-format-string-error]
severity = serious
certainty = possible
description =
 A Perl format string could not be parsed.
references =
 https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html

[perl-brace-format-string-missing-argument]
severity = serious
certainty = possible
description =
 A Perl format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``;
 or ``msgstr`` doesn't use a named argument that is used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``.
 .
 Note that in some languages,
 the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on.
 Take this Serbian translation for example::
 .
 .  Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
 .  ...
 .  msgid "one byte"
 .  msgid_plural "{n} bytes"
 .  msgstr[0] "{n} bajt"
 .  msgstr[1] "{n} bajta"
 .  msgstr[2] "{n} bajtova"
 .
 Here ``{n}`` should not be replaced with the spelled-out form ``jedan``.
 Either ``{n}`` should be kept, or the Plural-Forms expression should be amended,
 so that there is a special case for n=1::
 .
 .  Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2
 .  ...
 .  msgid "one byte"
 .  msgid_plural "{n} bytes"
 .  msgstr[0] "{n} bajt"
 .  msgstr[1] "{n} bajta"
 .  msgstr[2] "{n} bajtova"
 .  msgstr[3] "jedan bajt"
references =
 https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[perl-brace-format-string-unknown-argument]
severity = serious
certainty = possible
description =
 A Perl format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``;
 or ``msgstr`` uses a named argument that isn't used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``.
 This indicates that the conversion would try to consume an argument that weren't supplied.
references =
 https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[python-brace-format-string-argument-type-mismatch]
severity = serious
certainty = possible
description =
 There's a type mismatch between a Python format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``;
 or between a Python format argument in ``msgstr`` and ``msgid``;
 or between a Python format argument in ``msgstr[``\ *N*\ ``]`` and ``msgid`` or ``msgid_plural``.
references =
 https://docs.python.org/2/library/string.html#formatstrings

[python-brace-format-string-error]
severity = serious
certainty = possible
description =
 A Python format string could not be parsed.
references =
 https://docs.python.org/2/library/string.html#formatstrings

[python-brace-format-string-missing-argument]
severity = serious
certainty = possible
description =
 A Python format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``;
 or ``msgstr`` doesn't use a named argument that is used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``.
 .
 Note that in some languages,
 the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on.
 Take this Serbian translation for example::
 .
 .  Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
 .  ...
 .  msgid "one byte"
 .  msgid_plural "{n} bytes"
 .  msgstr[0] "{n} bajt"
 .  msgstr[1] "{n} bajta"
 .  msgstr[2] "{n} bajtova"
 .
 Here ``{n}`` should not be replaced with the spelled-out form ``jedan``.
 Either ``{n}`` should be kept, or the Plural-Forms expression should be amended,
 so that there is a special case for n=1::
 .
 .  Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2
 .  ...
 .  msgid "one byte"
 .  msgid_plural "{n} bytes"
 .  msgstr[0] "{n} bajt"
 .  msgstr[1] "{n} bajta"
 .  msgstr[2] "{n} bajtova"
 .  msgstr[3] "jedan bajt"
references =
 https://docs.python.org/2/library/string.html#formatstrings
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[python-brace-format-string-unknown-argument]
severity = serious
certainty = possible
description =
 A Python format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``;
 or ``msgstr`` uses a named argument that isn't used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``.
 This indicates that the conversion would try to consume an argument that weren't supplied.
references =
 https://docs.python.org/2/library/string.html#formatstrings
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[python-format-string-argument-number-mismatch]
severity = serious
certainty = possible
description =
 A Python format string for ``msgid`` consumes more arguments than ``msgid_plural``;
 or ``msgstr`` consumes more arguments than ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` consumes more arguments than ``msgid`` or ``msgid_plural``.
 .
 Python, unlike C, requires that all unnamed arguments must be consumed during conversion.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations
 https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python

[python-format-string-argument-type-mismatch]
severity = serious
certainty = possible
description =
 There's a type mismatch between a Python format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``;
 or between a Python format argument in ``msgstr`` and ``msgid``;
 or between a Python format argument in ``msgstr[``\ *N*\ ``]`` and ``msgid`` or ``msgid_plural``.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-error]
severity = serious
certainty = possible
description =
 A Python format string could not be parsed.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-missing-argument]
severity = serious
certainty = possible
description =
 A Python format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``;
 or ``msgstr`` doesn't use a named argument that is used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``.
 .
 Note that in some languages,
 the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on.
 Take this Serbian translation for example::
 .
 .  Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
 .  ...
 .  msgid "one byte"
 .  msgid_plural "%(n)d bytes"
 .  msgstr[0] "%(n)d bajt"
 .  msgstr[1] "%(n)d bajta"
 .  msgstr[2] "%(n)d bajtova"
 .
 Here ``%d`` should not be replaced with the spelled-out form ``jedan``.
 Either ``%d`` should be kept, or the Plural-Forms expression should be amended,
 so that there is a special case for n=1::
 .
 .  Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2
 .  ...
 .  msgid "one byte"
 .  msgid_plural "%(n)d bytes"
 .  msgstr[0] "%(n)d bajt"
 .  msgstr[1] "%(n)d bajta"
 .  msgstr[2] "%(n)d bajtova"
 .  msgstr[3] "jedan bajt"
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations
 https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html

[python-format-string-multiple-unnamed-arguments]
severity = serious
certainty = possible
description =
 A Python format string uses multiple unnamed arguments (such as ``%d``).
 The translator might need to reorder the arguments to properly translate the message,
 but this is not possible with unnamed arguments.
 Named arguments (such as ``%(num)d``) should be used instead.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations
 https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python

[python-format-string-obsolete-conversion]
severity = pedantic
certainty = possible
description =
 A Python format string uses an obsolete conversion specifier:
 .
 * Use ``%d`` instead of ``%u``.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-redundant-flag]
severity = pedantic
certainty = possible
description =
 A Python format string includes a redundant character flag.
 Either it's a duplicate, or it has no effect:
 .
 * The ``+`` flag overrides the *space* flag.
 * The ``-`` flag overrides the ``0`` flag.
 * If a precision is given, the ``0`` flag has no effect on integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``).
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-redundant-length]
severity = pedantic
certainty = possible
description =
 A Python format string includes a redundant length modifier.
 Length modifiers (``h``, ``l``, or ``L``) have no effect in Python.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-redundant-precision]
severity = pedantic
certainty = possible
description =
 A C format string includes precision that has no effect on the conversion.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations

[python-format-string-unknown-argument]
severity = serious
certainty = possible
description =
 A Python format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``;
 or ``msgstr`` uses a named argument that isn't used in ``msgid``;
 or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``.
 This indicates that the conversion would try to consume an argument that weren't supplied.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[python-format-string-unnamed-plural-argument]
severity = wishlist
certainty = possible
description =
 A Python format string uses an unnamed arguments (such as ``%d``)
 in the context of plural forms.
 The translator might want not to use the numeric argument in the singular form;
 but this is not possible if the argument is unnamed,
 because Python, unlike C, requires that all unnamed arguments must be consumed during conversion.
 Named arguments (such as ``%(n)d``) should be used instead.
references =
 https://docs.python.org/2/library/stdtypes.html#string-formatting-operations
 https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python

[qt-plural-format-mistaken-for-c-format]
severity = important
certainty = possible
description =
 A ``c-format`` flag is associated with the message,
 but ``qt-plural-format`` should be used instead.
 .
 The only C format directive that the message uses is ``%n``.
 It is very atypical to use it alone in a C format string.
references =
 https://doc.qt.io/qt-5/i18n-source-translation.html#handling-plurals
 printf(3)

[range-flag-without-plural-string]
severity = normal
certainty = certain
description =
 A ``range:`` flag is associated with a message that doesn't have plural string.
 ``range:`` flags only make sense for translations involving plural forms.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[redundant-message-flag]
severity = pedantic
certainty = certain
description =
 A flag associated with one of the messages is redundant,
 because it's implied by another flag.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[stray-header-line]
severity = important
certainty = certain
description =
 The header contains a line that does not belong to any header field.
 Note that RFC-822-style folding of long headers is not supported.
references =
 https://lists.gnu.org/archive/html/bug-gettext/2012-12/msg00010.html

[stray-previous-msgid]
severity = minor
certainty = certain
description =
 The message entry contains annotations about previous untranslated string
 (``#| msgid``\ *...*),
 even though the message is not marked as fuzzy.
 These annotations are only useful for fuzzy messages,
 and should be removed when unfuzzying.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[syntax-error-in-plural-forms]
severity = serious
certainty = certain
description =
 Value of the Plural-Forms header field could not be parsed.
 It should be in the form ``nplurals=``\ *n*\ ``; plural=``\ *expression*.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[syntax-error-in-po-file]
severity = serious
certainty = possible
description =
 This file couldn't be parsed a PO file.
 In some rare cases this is due to incorrect or missing encoding declaration.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html
 https://bugs.debian.org/692283

[syntax-error-in-unused-plural-forms]
severity = important
certainty = certain
description =
 Value of the Plural-Forms header field could not be parsed.
 (But there are no translated messages which use plural forms.)
 It should be in the form ``nplurals=``\ *n*\ ``; plural=``\ *expression*.
references =
 https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

[trailing-junk-in-plural-forms]
severity = important
certainty = certain
description =
 The Plural-Forms header field contains unexpected text after the plural expression.
 .
 GNU gettext runtime ignores such trailing junk,
 but other header parsers might be less liberal in what they accept.

[translation-in-template]
severity = minor
certainty = certain
description =
 The PO template file contains a translated message.

[unable-to-determine-language]
severity = normal
certainty = wild-guess
description =
 i18nspector was unable to determine language of this file.
 Absence of this information will prevent it from performing further checks.

[unexpected-flag-for-header-entry]
severity = normal
certainty = possible
description =
 An unexpected flag is associated with the header entry.
 The only flag that makes sense for the header entry is ``fuzzy``.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[unknown-encoding]
severity = important
certainty = possible
description =
 This file declares an encoding that couldn't be recognized by i18nspector.
 It might be a typo.
 Absence of encoding information will prevent i18nspector from performing
 further checks.

[unknown-file-type]
severity = normal
certainty = wild-guess
description =
 File format of this file couldn't be recognized.
 It might be a bug in i18nspector.

[unknown-header-field]
severity = minor
certainty = wild-guess
description =
 The header field name is unknown to i18nspector.
 It might be a typo or a capitalization error
 (header field names are case-sensitive).
references =
 https://lists.gnu.org/archive/html/bug-gettext/2012-12/msg00010.html

[unknown-message-flag]
severity = normal
certainty = wild-guess
description =
 An unknown flag is associated with one of the messages.
 It might be a typo.
references =
 https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html

[unknown-poedit-language]
severity = minor
certainty = wild-guess
description =
 Language declared in X-Poedit-Language couldn't be recognized.
 It might be a bug in i18nspector.

[unrepresentable-characters]
severity = serious
certainty = possible
description =
 The declared encoding cannot represent all characters commonly used in this language.
 This is a strong indication that the declared encoding is incorrect.

[unusual-character-in-header-entry]
severity = important
certainty = certain
description =
 The header entry contains an unusual character.
 This is usually an indication of an encoding problem, such as:
 .
 * using ISO 2022 escape sequences, or
 * using UTF-8 despite declaring an 8-bit encoding.
references =
 https://www.unicode.org/faq/utf_bom.html#bom6

[unusual-character-in-translation]
severity = important
certainty = possible
description =
 One of the translated messages contains an unusual character.
 This is usually an indication of an encoding problem, such as:
 .
 * using ISO 2022 escape sequences, or
 * using UTF-8 despite declaring an 8-bit encoding.
references =
 https://www.unicode.org/faq/utf_bom.html#bom6

[unusual-plural-forms]
severity = serious
certainty = possible
description =
 The Plural-Forms declaration is incorrect (or unusual),
 according to i18nspector's linguistic data.

[unusual-unused-plural-forms]
severity = normal
certainty = possible
description =
 The Plural-Forms declaration is incorrect (or unusual),
 according to i18nspector's linguistic data.
 (But there are no translated messages which use plural forms.)

# vim:ft=dosini
