| 1 |
[ancient-date] |
| 2 |
severity = normal |
| 3 |
certainty = certain |
| 4 |
description = |
| 5 |
The date refers to the time before the first GNU gettext release. |
| 6 |
As such, it's extremely unlikely to be correct. |
| 7 |
references = |
| 8 |
https://git.savannah.gnu.org/cgit/gettext.git/tree/ChangeLog.0#n1767 |
| 9 |
|
| 10 |
[arithmetic-error-in-plural-forms] |
| 11 |
severity = serious |
| 12 |
certainty = possible |
| 13 |
description = |
| 14 |
Computing a plural form value triggers division by zero or integer overflow. |
| 15 |
This normally indicates an error in the plural form expression. |
| 16 |
references = |
| 17 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 18 |
|
| 19 |
[arithmetic-error-in-unused-plural-forms] |
| 20 |
severity = normal |
| 21 |
certainty = possible |
| 22 |
description = |
| 23 |
Computing a plural form value triggers division by zero or integer overflow. |
| 24 |
(But there are no translated messages which use plural forms.) |
| 25 |
This normally indicates an error in the plural form expression. |
| 26 |
references = |
| 27 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 28 |
|
| 29 |
[boilerplate-in-content-type] |
| 30 |
severity = important |
| 31 |
certainty = certain |
| 32 |
description = |
| 33 |
The Content-Type header field contains xgettext boilerplate. |
| 34 |
It should be in the form ``text/plain; charset=``\ *encoding*. |
| 35 |
references = |
| 36 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files |
| 37 |
|
| 38 |
[boilerplate-in-date] |
| 39 |
severity = normal |
| 40 |
certainty = certain |
| 41 |
description = |
| 42 |
The date header field contains xgettext boilerplate. |
| 43 |
The date format should be ``YYYY-MM-DD hh:mm+ZZzz``, |
| 44 |
e.g. ``2011-11-05 10:14+0100``. |
| 45 |
|
| 46 |
[boilerplate-in-initial-comments] |
| 47 |
severity = minor |
| 48 |
certainty = possible |
| 49 |
description = |
| 50 |
The initial comments contain xgettext or msginit boilerplate. |
| 51 |
references = |
| 52 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 53 |
|
| 54 |
[boilerplate-in-language-team] |
| 55 |
severity = minor |
| 56 |
certainty = certain |
| 57 |
description = |
| 58 |
The Language-Team header field contains xgettext boilerplate. |
| 59 |
It should contain English name of the language, |
| 60 |
and the email address or homepage URL of the language team. |
| 61 |
references = |
| 62 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 63 |
|
| 64 |
[boilerplate-in-last-translator] |
| 65 |
severity = normal |
| 66 |
certainty = certain |
| 67 |
description = |
| 68 |
The Last-Translator header field contains xgettext boilerplate. |
| 69 |
It should contain the last translator's name and email address. |
| 70 |
references = |
| 71 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 72 |
|
| 73 |
[boilerplate-in-project-id-version] |
| 74 |
severity = minor |
| 75 |
certainty = certain |
| 76 |
description = |
| 77 |
The Project-Id-Version header field contains xgettext boilerplate. |
| 78 |
It should contain the name and the version of the package. |
| 79 |
references = |
| 80 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 81 |
|
| 82 |
[boilerplate-in-report-msgid-bugs-to] |
| 83 |
severity = normal |
| 84 |
certainty = certain |
| 85 |
description = |
| 86 |
The Report-Msgid-Bugs-To header field contains xgettext boilerplate. |
| 87 |
It should contain an email address |
| 88 |
or URL where one can report bugs in the untranslated strings. |
| 89 |
references = |
| 90 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 91 |
|
| 92 |
[broken-encoding] |
| 93 |
severity = serious |
| 94 |
certainty = possible |
| 95 |
description = |
| 96 |
Header fields and messages contained by this file couldn't be decoded to Unicode. |
| 97 |
The usual cause of this is incorrect or missing encoding declaration. |
| 98 |
. |
| 99 |
Note that in the absence of encoding declaration, |
| 100 |
i18nspector assumes ASCII encoding. |
| 101 |
references = |
| 102 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files |
| 103 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-5 |
| 104 |
|
| 105 |
[c-format-string-argument-type-mismatch] |
| 106 |
severity = serious |
| 107 |
certainty = possible |
| 108 |
description = |
| 109 |
There's a type mismatch between a C format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``; |
| 110 |
or between a C format argument in ``msgstr`` and ``msgid``; |
| 111 |
or between a C format argument in ``msgstr[``\ *N*\ ``]`` and corresponding ``msgid`` or ``msgid_plural``. |
| 112 |
references = |
| 113 |
printf(3) |
| 114 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 115 |
|
| 116 |
[c-format-string-error] |
| 117 |
severity = serious |
| 118 |
certainty = possible |
| 119 |
description = |
| 120 |
A C format string could not be parsed. |
| 121 |
references = |
| 122 |
printf(3) |
| 123 |
|
| 124 |
[c-format-string-excess-arguments] |
| 125 |
severity = serious |
| 126 |
certainty = possible |
| 127 |
description = |
| 128 |
A C format string for ``msgid`` consumes more arguments than ``msgid_plural``; |
| 129 |
or ``msgstr`` consumes more arguments than ``msgid``; |
| 130 |
or ``msgstr[``\ *N*\ ``]`` consumes more arguments than corresponding ``msgid`` or ``msgid_plural``. |
| 131 |
references = |
| 132 |
printf(3) |
| 133 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 134 |
|
| 135 |
[c-format-string-missing-arguments] |
| 136 |
severity = serious |
| 137 |
certainty = possible |
| 138 |
description = |
| 139 |
A C format string for ``msgid`` consumes fewer arguments than ``msgid_plural``; |
| 140 |
or ``msgstr`` consumes fewer arguments than ``msgid``; |
| 141 |
or ``msgstr[``\ *N*\ ``]`` consumes fewer arguments than corresponding ``msgid`` or ``msgid_plural``. |
| 142 |
. |
| 143 |
Note that in some languages, |
| 144 |
the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on. |
| 145 |
Take this Serbian translation for example:: |
| 146 |
. |
| 147 |
. 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; |
| 148 |
. ... |
| 149 |
. msgid "one byte" |
| 150 |
. msgid_plural "%d bytes" |
| 151 |
. msgstr[0] "%d bajt" |
| 152 |
. msgstr[1] "%d bajta" |
| 153 |
. msgstr[2] "%d bajtova" |
| 154 |
. |
| 155 |
Here ``%d`` should not be replaced with the spelled-out form ``jedan``. |
| 156 |
Either ``%d`` should be kept, or the Plural-Forms expression should be amended, |
| 157 |
so that there is a special case for n=1:: |
| 158 |
. |
| 159 |
. 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 |
| 160 |
. ... |
| 161 |
. msgid "one byte" |
| 162 |
. msgid_plural "%d bytes" |
| 163 |
. msgstr[0] "%d bajt" |
| 164 |
. msgstr[1] "%d bajta" |
| 165 |
. msgstr[2] "%d bajtova" |
| 166 |
. msgstr[3] "jedan bajt" |
| 167 |
references = |
| 168 |
printf(3) |
| 169 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 170 |
|
| 171 |
[c-format-string-non-portable-conversion] |
| 172 |
severity = pedantic |
| 173 |
certainty = possible |
| 174 |
description = |
| 175 |
A C format string uses a conversion specified or length modifier, |
| 176 |
for which a more portable replacement exists: |
| 177 |
. |
| 178 |
* For integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``), use the ``ll`` length modifier instead of ``L`` or ``q``. |
| 179 |
* For floating-point conversions (``%a``, ``%A``, ``%e``, ``%E``, ``%f``, ``%F``, ``%g``, and ``%G``), don't use the ``l`` length modifier. |
| 180 |
* Use the ``z`` length modifier instead of ``Z``. |
| 181 |
* Use ``%lc`` instead of ``%C``. |
| 182 |
* Use ``%ls`` instead of ``%S``. |
| 183 |
references = |
| 184 |
printf(3) |
| 185 |
|
| 186 |
[c-format-string-redundant-flag] |
| 187 |
severity = pedantic |
| 188 |
certainty = possible |
| 189 |
description = |
| 190 |
A C format string includes a redundant character flag. |
| 191 |
Either it's a duplicate, or it has no effect: |
| 192 |
. |
| 193 |
* The ``+`` flag overrides the *space* flag. |
| 194 |
* The ``-`` flag overrides the ``0`` flag. |
| 195 |
* If a precision is given, the ``0`` flag has no effect on integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``). |
| 196 |
references = |
| 197 |
printf(3) |
| 198 |
|
| 199 |
[codomain-error-in-plural-forms] |
| 200 |
severity = serious |
| 201 |
certainty = certain |
| 202 |
description = |
| 203 |
Either a plural form value is outside the declared range, |
| 204 |
or some values within the declared range can never be reached. |
| 205 |
This normally indicates an error in the plural form expression. |
| 206 |
references = |
| 207 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 208 |
|
| 209 |
[codomain-error-in-unused-plural-forms] |
| 210 |
severity = normal |
| 211 |
certainty = certain |
| 212 |
description = |
| 213 |
Either a plural form value is outside the declared range, |
| 214 |
or some values within the declared range can never be reached. |
| 215 |
(But there are no translated messages which use plural forms.) |
| 216 |
This normally indicates an error in the plural form expression. |
| 217 |
references = |
| 218 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 219 |
|
| 220 |
[conflict-marker-in-header-entry] |
| 221 |
severity = serious |
| 222 |
certainty = certain |
| 223 |
description = |
| 224 |
The header contains a conflict marker (``#-#-#-#-#`` *…* ``#-#-#-#-#``). |
| 225 |
The conflict will have to be resolved manually. |
| 226 |
references = |
| 227 |
https://www.gnu.org/software/gettext/manual/html_node/Creating-Compendia.html#Creating-Compendia |
| 228 |
|
| 229 |
[conflict-marker-in-translation] |
| 230 |
severity = serious |
| 231 |
certainty = possible |
| 232 |
description = |
| 233 |
One of the translated messages appear to contain a conflict marker |
| 234 |
(``#-#-#-#-#`` *…* ``#-#-#-#-#``). |
| 235 |
The conflict will have to be resolved manually. |
| 236 |
references = |
| 237 |
https://www.gnu.org/software/gettext/manual/html_node/Creating-Compendia.html#Creating-Compendia |
| 238 |
|
| 239 |
[conflicting-message-flags] |
| 240 |
severity = important |
| 241 |
certainty = possible |
| 242 |
description = |
| 243 |
Two flags with conflicting meanings are associated with one of the messages. |
| 244 |
references = |
| 245 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 246 |
|
| 247 |
[date-from-future] |
| 248 |
severity = normal |
| 249 |
certainty = certain |
| 250 |
description = |
| 251 |
The date refers to the future. |
| 252 |
As such, it's extremely unlikely to be correct. |
| 253 |
|
| 254 |
[distant-header-entry] |
| 255 |
severity = important |
| 256 |
certainty = certain |
| 257 |
description = |
| 258 |
The header entry in this file is preceded by other entries. |
| 259 |
The header entry should be always the first one. |
| 260 |
|
| 261 |
[duplicate-flag-for-header-entry] |
| 262 |
severity = minor |
| 263 |
certainty = certain |
| 264 |
description = |
| 265 |
Multiple identical flags are associated with the header entry. |
| 266 |
|
| 267 |
[duplicate-header-entry] |
| 268 |
severity = serious |
| 269 |
certainty = certain |
| 270 |
description = |
| 271 |
This file contains multiple header entries. |
| 272 |
|
| 273 |
[duplicate-header-field] |
| 274 |
severity = minor |
| 275 |
certainty = wild-guess |
| 276 |
description = |
| 277 |
This file contains multiple header fields of the same name. |
| 278 |
|
| 279 |
[duplicate-header-field-content-transfer-encoding] |
| 280 |
severity = pedantic |
| 281 |
certainty = certain |
| 282 |
description = |
| 283 |
This file contains multiple Content-Transfer-Encoding header fields. |
| 284 |
|
| 285 |
[duplicate-header-field-content-type] |
| 286 |
severity = serious |
| 287 |
certainty = certain |
| 288 |
description = |
| 289 |
This file contains multiple Content-Type header fields. |
| 290 |
|
| 291 |
[duplicate-header-field-date] |
| 292 |
severity = normal |
| 293 |
certainty = certain |
| 294 |
description = |
| 295 |
This file contains multiple date header fields of the same name. |
| 296 |
|
| 297 |
[duplicate-header-field-language] |
| 298 |
severity = important |
| 299 |
certainty = certain |
| 300 |
description = |
| 301 |
This file contains multiple Language header fields. |
| 302 |
|
| 303 |
[duplicate-header-field-language-team] |
| 304 |
severity = normal |
| 305 |
certainty = certain |
| 306 |
description = |
| 307 |
This file contains multiple Language-Team header fields. |
| 308 |
|
| 309 |
[duplicate-header-field-last-translator] |
| 310 |
severity = normal |
| 311 |
certainty = certain |
| 312 |
description = |
| 313 |
This file contains multiple Last-Translator header fields. |
| 314 |
|
| 315 |
[duplicate-header-field-mime-version] |
| 316 |
severity = pedantic |
| 317 |
certainty = certain |
| 318 |
description = |
| 319 |
This file contains multiple MIME-Version header fields. |
| 320 |
|
| 321 |
[duplicate-header-field-plural-forms] |
| 322 |
severity = serious |
| 323 |
certainty = certain |
| 324 |
description = |
| 325 |
This file contains multiple Plural-Forms header fields. |
| 326 |
|
| 327 |
[duplicate-header-field-project-id-version] |
| 328 |
severity = minor |
| 329 |
certainty = certain |
| 330 |
description = |
| 331 |
This file contains multiple Project-Id-Version header fields. |
| 332 |
|
| 333 |
[duplicate-header-field-report-msgid-bugs-to] |
| 334 |
severity = normal |
| 335 |
certainty = certain |
| 336 |
description = |
| 337 |
This file contains multiple Report-Msgid-Bugs-To header fields. |
| 338 |
|
| 339 |
[duplicate-header-field-x-poedit] |
| 340 |
severity = normal |
| 341 |
certainty = certain |
| 342 |
description = |
| 343 |
This file contains multiple X-Poedit-*\** header fields. |
| 344 |
|
| 345 |
[duplicate-message-definition] |
| 346 |
severity = serious |
| 347 |
certainty = certain |
| 348 |
description = |
| 349 |
This file contains multiple definitions of the same message. |
| 350 |
|
| 351 |
[duplicate-message-flag] |
| 352 |
severity = minor |
| 353 |
certainty = certain |
| 354 |
description = |
| 355 |
Multiple identical flags are associated with one of the messages. |
| 356 |
|
| 357 |
[empty-file] |
| 358 |
severity = normal |
| 359 |
certainty = certain |
| 360 |
description = |
| 361 |
This file doesn't contain any messages. |
| 362 |
|
| 363 |
[empty-msgid-message-with-plural-forms] |
| 364 |
severity = serious |
| 365 |
certainty = certain |
| 366 |
description = |
| 367 |
The message with empty msgid contains plural forms. |
| 368 |
Such messages are reserved by GNU gettext for header entries, |
| 369 |
and your code should not call ``ngettext("", …)``. |
| 370 |
|
| 371 |
[empty-msgid-message-with-source-code-references] |
| 372 |
severity = serious |
| 373 |
certainty = possible |
| 374 |
description = |
| 375 |
The message with empty msgid contains plural forms. |
| 376 |
Such messages are reserved by GNU gettext for header entries, |
| 377 |
and your code should not call ``gettext("")``. |
| 378 |
|
| 379 |
[encoding-in-language-header-field] |
| 380 |
severity = minor |
| 381 |
certainty = certain |
| 382 |
description = |
| 383 |
The language header field contains encoding declaration. |
| 384 |
Such information shouldn't be included in this field. |
| 385 |
references = |
| 386 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 387 |
|
| 388 |
[fuzzy-header-entry] |
| 389 |
severity = pedantic |
| 390 |
certainty = certain |
| 391 |
description = |
| 392 |
The header entry is marked as fuzzy. |
| 393 |
For compatibility with very old (<< 0.11) **msgfmt**\ (1) versions, |
| 394 |
which didn't support fuzzy header entries, it shouldn't be marked as such. |
| 395 |
references = |
| 396 |
https://git.savannah.gnu.org/cgit/gettext.git/tree/NEWS?id=v0.11#n44 |
| 397 |
|
| 398 |
[inconsistent-leading-newlines] |
| 399 |
severity = important |
| 400 |
certainty = possible |
| 401 |
description = |
| 402 |
Some strings in an entry start with a newline, but some don't. |
| 403 |
Either all of them should start with a newline, or none of them should. |
| 404 |
|
| 405 |
[inconsistent-number-of-plural-forms] |
| 406 |
severity = serious |
| 407 |
certainty = certain |
| 408 |
description = |
| 409 |
Number of plural forms in a message definition doesn't match number of plural forms declared in another message definition. |
| 410 |
references = |
| 411 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 412 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 413 |
|
| 414 |
[inconsistent-trailing-newlines] |
| 415 |
severity = important |
| 416 |
certainty = possible |
| 417 |
description = |
| 418 |
Some strings in an entry end with a newline, but some don't. |
| 419 |
Either all of them should end with a newline, or none of them should. |
| 420 |
|
| 421 |
[incorrect-number-of-plural-forms] |
| 422 |
severity = serious |
| 423 |
certainty = certain |
| 424 |
description = |
| 425 |
Number of plural forms in a message definition doesn't match number of plural forms declared in the header. |
| 426 |
references = |
| 427 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 428 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 429 |
|
| 430 |
[invalid-content-transfer-encoding] |
| 431 |
severity = pedantic |
| 432 |
certainty = certain |
| 433 |
description = |
| 434 |
Value of the Content-Transfer-Encoding header field is invalid. |
| 435 |
It should be ``8bit``. |
| 436 |
references = |
| 437 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 438 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-6.1 |
| 439 |
|
| 440 |
[invalid-content-type] |
| 441 |
severity = important |
| 442 |
certainty = possible |
| 443 |
description = |
| 444 |
Value of the Content-Type header field should is invalid. |
| 445 |
It should be in the form ``text/plain; charset=``\ *encoding*. |
| 446 |
references = |
| 447 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files |
| 448 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-5 |
| 449 |
|
| 450 |
[invalid-date] |
| 451 |
severity = normal |
| 452 |
certainty = certain |
| 453 |
description = |
| 454 |
The date is invalid or in an invalid format. |
| 455 |
The format should be ``YYYY-MM-DD hh:mm+ZZzz``, |
| 456 |
e.g. ``2011-11-05 10:14+0100``. |
| 457 |
references = |
| 458 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 459 |
|
| 460 |
[invalid-language] |
| 461 |
severity = important |
| 462 |
certainty = possible |
| 463 |
description = |
| 464 |
The Language header field couldn't be parsed, |
| 465 |
or it contains an unknown language. |
| 466 |
references = |
| 467 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 468 |
|
| 469 |
[invalid-language-team] |
| 470 |
severity = normal |
| 471 |
certainty = possible |
| 472 |
description = |
| 473 |
The Language-Team header field contains an e-mail address |
| 474 |
that uses a reserved domain name, |
| 475 |
or a partially qualified domain name. |
| 476 |
references = |
| 477 |
https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml |
| 478 |
|
| 479 |
[invalid-last-translator] |
| 480 |
severity = normal |
| 481 |
certainty = possible |
| 482 |
description = |
| 483 |
The Last-Translator header field could neither be parsed as an e-mail, |
| 484 |
or the e-mail address uses a reserved domain name, |
| 485 |
or a partially qualified domain name. |
| 486 |
references = |
| 487 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 488 |
https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml |
| 489 |
|
| 490 |
[invalid-mime-version] |
| 491 |
severity = pedantic |
| 492 |
certainty = certain |
| 493 |
description = |
| 494 |
Value of the MIME-Version header field is invalid. |
| 495 |
It should be ``1.0``. |
| 496 |
references = |
| 497 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-4 |
| 498 |
|
| 499 |
[invalid-mo-file] |
| 500 |
severity = serious |
| 501 |
certainty = certain |
| 502 |
description = |
| 503 |
This file couldn't be parsed a MO file. |
| 504 |
|
| 505 |
[invalid-range-flag] |
| 506 |
severity = important |
| 507 |
certainty = certain |
| 508 |
description = |
| 509 |
A ``range:`` flag couldn't be parsed, or the designated range contained fewer than two numbers. |
| 510 |
The syntax is ``range:``\ *min*\ ``..``\ *max*, where both values are non-negative integers. |
| 511 |
references = |
| 512 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 513 |
|
| 514 |
[invalid-report-msgid-bugs-to] |
| 515 |
severity = normal |
| 516 |
certainty = possible |
| 517 |
description = |
| 518 |
The Report-Msgid-Bugs-To header field could neither be parsed as an e-mail nor as a URL, |
| 519 |
or the e-mail address uses a reserved domain name, |
| 520 |
or a partially qualified domain name. |
| 521 |
references = |
| 522 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 523 |
https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml |
| 524 |
|
| 525 |
[language-disparity] |
| 526 |
severity = normal |
| 527 |
certainty = possible |
| 528 |
description = |
| 529 |
Language of this file has been declared in multiple places, |
| 530 |
but the declarations don't match. |
| 531 |
|
| 532 |
[language-team-equal-to-last-translator] |
| 533 |
severity = minor |
| 534 |
certainty = possible |
| 535 |
description = |
| 536 |
Language-Team and Last-Translator header fields contain the same e-mail address. |
| 537 |
|
| 538 |
[language-variant-does-not-affect-translation] |
| 539 |
severity = minor |
| 540 |
certainty = possible |
| 541 |
description = |
| 542 |
The Language header field contains a variant designator that is not relevant for the message translation. |
| 543 |
references = |
| 544 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 545 |
|
| 546 |
[leading-junk-in-plural-forms] |
| 547 |
severity = important |
| 548 |
certainty = certain |
| 549 |
description = |
| 550 |
The Plural-Forms header field contains unexpected text before the ``nplurals=`` string. |
| 551 |
. |
| 552 |
GNU gettext runtime ignores such leading junk, |
| 553 |
but other header parsers might be less liberal in what they accept. |
| 554 |
|
| 555 |
[malformed-xml] |
| 556 |
severity = serious |
| 557 |
certainty = possible |
| 558 |
description = |
| 559 |
The original string or the translated string contains an XML fragment, |
| 560 |
which is not well-formed. |
| 561 |
references = |
| 562 |
https://www.w3.org/TR/REC-xml/#sec-well-formed |
| 563 |
|
| 564 |
[no-content-transfer-encoding-header-field] |
| 565 |
severity = pedantic |
| 566 |
certainty = certain |
| 567 |
description = |
| 568 |
The Content-Transfer-Encoding header field doesn't exist. |
| 569 |
It should be set to ``8bit``. |
| 570 |
references = |
| 571 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 572 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-6.1 |
| 573 |
|
| 574 |
[no-content-type-header-field] |
| 575 |
severity = important |
| 576 |
certainty = certain |
| 577 |
description = |
| 578 |
The Content-Type header field doesn't exist. |
| 579 |
It should be set to ``text/plain; charset=``\ *encoding*. |
| 580 |
. |
| 581 |
Note that in the absence of encoding declaration, |
| 582 |
i18nspector assumes ASCII encoding. |
| 583 |
references = |
| 584 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-of-PO-files |
| 585 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-5 |
| 586 |
|
| 587 |
[no-date-header-field] |
| 588 |
severity = minor |
| 589 |
certainty = certain |
| 590 |
description = |
| 591 |
The date header field doesn't exist. |
| 592 |
references = |
| 593 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 594 |
|
| 595 |
[no-language-header-field] |
| 596 |
severity = pedantic |
| 597 |
certainty = certain |
| 598 |
description = |
| 599 |
The Language header field doesn't exist. |
| 600 |
references = |
| 601 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 602 |
|
| 603 |
[no-language-team-header-field] |
| 604 |
severity = pedantic |
| 605 |
certainty = certain |
| 606 |
description = |
| 607 |
The Language-Team header field does not exist. |
| 608 |
It should contain English name of the language, |
| 609 |
and the email address or homepage URL of the language team. |
| 610 |
references = |
| 611 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 612 |
|
| 613 |
[no-last-translator-header-field] |
| 614 |
severity = normal |
| 615 |
certainty = certain |
| 616 |
description = |
| 617 |
The Last-Translator header field doesn't exist. |
| 618 |
It should contain the last translator's name and email address. |
| 619 |
references = |
| 620 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 621 |
|
| 622 |
[no-mime-version-header-field] |
| 623 |
severity = pedantic |
| 624 |
certainty = certain |
| 625 |
description = |
| 626 |
The MIME-Version header field doesn't exist. |
| 627 |
It should be to set to ``1.0``. |
| 628 |
references = |
| 629 |
https://www.rfc-editor.org/rfc/rfc2045.html#section-4 |
| 630 |
|
| 631 |
[no-package-name-in-project-id-version] |
| 632 |
severity = minor |
| 633 |
certainty = possible |
| 634 |
description = |
| 635 |
The Project-Id-Version header field doesn't appear to contain any name. |
| 636 |
It should contain both the name and the version of the package. |
| 637 |
references = |
| 638 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 639 |
|
| 640 |
[no-plural-forms-header-field] |
| 641 |
severity = minor |
| 642 |
certainty = certain |
| 643 |
description = |
| 644 |
The Plural-Forms header field does not exist, |
| 645 |
even though some of the messages use plural forms |
| 646 |
(although none of them have been translated). |
| 647 |
references = |
| 648 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 649 |
|
| 650 |
[no-project-id-version-header-field] |
| 651 |
severity = minor |
| 652 |
certainty = certain |
| 653 |
description = |
| 654 |
The Project-Id-Version header field does not exist. |
| 655 |
It should contain the name and the version of the package. |
| 656 |
references = |
| 657 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 658 |
|
| 659 |
[no-report-msgid-bugs-to-header-field] |
| 660 |
severity = normal |
| 661 |
certainty = certain |
| 662 |
description = |
| 663 |
The Report-Msgid-Bugs-To header field does not exist or it is empty. |
| 664 |
It should contain an email address or URL where one can report bugs in the untranslated strings. |
| 665 |
references = |
| 666 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 667 |
|
| 668 |
[no-required-plural-forms-header-field] |
| 669 |
severity = serious |
| 670 |
certainty = certain |
| 671 |
description = |
| 672 |
The Plural-Forms header field does not exist, |
| 673 |
even though some of the translated messages use plural forms. |
| 674 |
references = |
| 675 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 676 |
|
| 677 |
[no-version-in-project-id-version] |
| 678 |
severity = pedantic |
| 679 |
certainty = possible |
| 680 |
description = |
| 681 |
The Project-Id-Version header field doesn't appear to contain any version. |
| 682 |
It should contain both the name and the version of the package. |
| 683 |
references = |
| 684 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html |
| 685 |
|
| 686 |
[non-ascii-compatible-encoding] |
| 687 |
severity = serious |
| 688 |
certainty = certain |
| 689 |
description = |
| 690 |
This file uses an encoding that is not compatible with ASCII. |
| 691 |
|
| 692 |
[non-portable-encoding] |
| 693 |
severity = important |
| 694 |
certainty = certain |
| 695 |
description = |
| 696 |
This file uses an encoding that is not widely supported by software. |
| 697 |
references = |
| 698 |
https://www.gnu.org/software/gettext/manual/html_node/Header-Entry.html#index-encoding-list |
| 699 |
|
| 700 |
[os-error] |
| 701 |
severity = serious |
| 702 |
certainty = certain |
| 703 |
description = |
| 704 |
An input/output error or another operating system error occurred while checking this file. |
| 705 |
|
| 706 |
[partially-translated-message] |
| 707 |
severity = serious |
| 708 |
certainty = possible |
| 709 |
description = |
| 710 |
Translation is missing for some plural forms of a message. |
| 711 |
|
| 712 |
[perl-brace-format-string-error] |
| 713 |
severity = serious |
| 714 |
certainty = possible |
| 715 |
description = |
| 716 |
A Perl format string could not be parsed. |
| 717 |
references = |
| 718 |
https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html |
| 719 |
|
| 720 |
[perl-brace-format-string-missing-argument] |
| 721 |
severity = serious |
| 722 |
certainty = possible |
| 723 |
description = |
| 724 |
A Perl format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``; |
| 725 |
or ``msgstr`` doesn't use a named argument that is used in ``msgid``; |
| 726 |
or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``. |
| 727 |
. |
| 728 |
Note that in some languages, |
| 729 |
the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on. |
| 730 |
Take this Serbian translation for example:: |
| 731 |
. |
| 732 |
. 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; |
| 733 |
. ... |
| 734 |
. msgid "one byte" |
| 735 |
. msgid_plural "{n} bytes" |
| 736 |
. msgstr[0] "{n} bajt" |
| 737 |
. msgstr[1] "{n} bajta" |
| 738 |
. msgstr[2] "{n} bajtova" |
| 739 |
. |
| 740 |
Here ``{n}`` should not be replaced with the spelled-out form ``jedan``. |
| 741 |
Either ``{n}`` should be kept, or the Plural-Forms expression should be amended, |
| 742 |
so that there is a special case for n=1:: |
| 743 |
. |
| 744 |
. 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 |
| 745 |
. ... |
| 746 |
. msgid "one byte" |
| 747 |
. msgid_plural "{n} bytes" |
| 748 |
. msgstr[0] "{n} bajt" |
| 749 |
. msgstr[1] "{n} bajta" |
| 750 |
. msgstr[2] "{n} bajtova" |
| 751 |
. msgstr[3] "jedan bajt" |
| 752 |
references = |
| 753 |
https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html |
| 754 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 755 |
|
| 756 |
[perl-brace-format-string-unknown-argument] |
| 757 |
severity = serious |
| 758 |
certainty = possible |
| 759 |
description = |
| 760 |
A Perl format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``; |
| 761 |
or ``msgstr`` uses a named argument that isn't used in ``msgid``; |
| 762 |
or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``. |
| 763 |
This indicates that the conversion would try to consume an argument that weren't supplied. |
| 764 |
references = |
| 765 |
https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html |
| 766 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 767 |
|
| 768 |
[python-brace-format-string-argument-type-mismatch] |
| 769 |
severity = serious |
| 770 |
certainty = possible |
| 771 |
description = |
| 772 |
There's a type mismatch between a Python format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``; |
| 773 |
or between a Python format argument in ``msgstr`` and ``msgid``; |
| 774 |
or between a Python format argument in ``msgstr[``\ *N*\ ``]`` and ``msgid`` or ``msgid_plural``. |
| 775 |
references = |
| 776 |
https://docs.python.org/2/library/string.html#formatstrings |
| 777 |
|
| 778 |
[python-brace-format-string-error] |
| 779 |
severity = serious |
| 780 |
certainty = possible |
| 781 |
description = |
| 782 |
A Python format string could not be parsed. |
| 783 |
references = |
| 784 |
https://docs.python.org/2/library/string.html#formatstrings |
| 785 |
|
| 786 |
[python-brace-format-string-missing-argument] |
| 787 |
severity = serious |
| 788 |
certainty = possible |
| 789 |
description = |
| 790 |
A Python format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``; |
| 791 |
or ``msgstr`` doesn't use a named argument that is used in ``msgid``; |
| 792 |
or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``. |
| 793 |
. |
| 794 |
Note that in some languages, |
| 795 |
the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on. |
| 796 |
Take this Serbian translation for example:: |
| 797 |
. |
| 798 |
. 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; |
| 799 |
. ... |
| 800 |
. msgid "one byte" |
| 801 |
. msgid_plural "{n} bytes" |
| 802 |
. msgstr[0] "{n} bajt" |
| 803 |
. msgstr[1] "{n} bajta" |
| 804 |
. msgstr[2] "{n} bajtova" |
| 805 |
. |
| 806 |
Here ``{n}`` should not be replaced with the spelled-out form ``jedan``. |
| 807 |
Either ``{n}`` should be kept, or the Plural-Forms expression should be amended, |
| 808 |
so that there is a special case for n=1:: |
| 809 |
. |
| 810 |
. 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 |
| 811 |
. ... |
| 812 |
. msgid "one byte" |
| 813 |
. msgid_plural "{n} bytes" |
| 814 |
. msgstr[0] "{n} bajt" |
| 815 |
. msgstr[1] "{n} bajta" |
| 816 |
. msgstr[2] "{n} bajtova" |
| 817 |
. msgstr[3] "jedan bajt" |
| 818 |
references = |
| 819 |
https://docs.python.org/2/library/string.html#formatstrings |
| 820 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 821 |
|
| 822 |
[python-brace-format-string-unknown-argument] |
| 823 |
severity = serious |
| 824 |
certainty = possible |
| 825 |
description = |
| 826 |
A Python format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``; |
| 827 |
or ``msgstr`` uses a named argument that isn't used in ``msgid``; |
| 828 |
or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``. |
| 829 |
This indicates that the conversion would try to consume an argument that weren't supplied. |
| 830 |
references = |
| 831 |
https://docs.python.org/2/library/string.html#formatstrings |
| 832 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 833 |
|
| 834 |
[python-format-string-argument-number-mismatch] |
| 835 |
severity = serious |
| 836 |
certainty = possible |
| 837 |
description = |
| 838 |
A Python format string for ``msgid`` consumes more arguments than ``msgid_plural``; |
| 839 |
or ``msgstr`` consumes more arguments than ``msgid``; |
| 840 |
or ``msgstr[``\ *N*\ ``]`` consumes more arguments than ``msgid`` or ``msgid_plural``. |
| 841 |
. |
| 842 |
Python, unlike C, requires that all unnamed arguments must be consumed during conversion. |
| 843 |
references = |
| 844 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 845 |
https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python |
| 846 |
|
| 847 |
[python-format-string-argument-type-mismatch] |
| 848 |
severity = serious |
| 849 |
certainty = possible |
| 850 |
description = |
| 851 |
There's a type mismatch between a Python format argument in ``msgid`` and the corresponding format argument in ``msgid_plural``; |
| 852 |
or between a Python format argument in ``msgstr`` and ``msgid``; |
| 853 |
or between a Python format argument in ``msgstr[``\ *N*\ ``]`` and ``msgid`` or ``msgid_plural``. |
| 854 |
references = |
| 855 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 856 |
|
| 857 |
[python-format-string-error] |
| 858 |
severity = serious |
| 859 |
certainty = possible |
| 860 |
description = |
| 861 |
A Python format string could not be parsed. |
| 862 |
references = |
| 863 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 864 |
|
| 865 |
[python-format-string-missing-argument] |
| 866 |
severity = serious |
| 867 |
certainty = possible |
| 868 |
description = |
| 869 |
A Python format string for ``msgid`` doesn't use a named argument that is used in ``msgid_plural``; |
| 870 |
or ``msgstr`` doesn't use a named argument that is used in ``msgid``; |
| 871 |
or ``msgstr[``\ *N*\ ``]`` doesn't use a named argument that is used in corresponding ``msgid`` or ``msgid_plural``. |
| 872 |
. |
| 873 |
Note that in some languages, |
| 874 |
the commonly used Plural-Forms expression evaluates to the same value for n=1 and n=21, n=31, and so on. |
| 875 |
Take this Serbian translation for example:: |
| 876 |
. |
| 877 |
. 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; |
| 878 |
. ... |
| 879 |
. msgid "one byte" |
| 880 |
. msgid_plural "%(n)d bytes" |
| 881 |
. msgstr[0] "%(n)d bajt" |
| 882 |
. msgstr[1] "%(n)d bajta" |
| 883 |
. msgstr[2] "%(n)d bajtova" |
| 884 |
. |
| 885 |
Here ``%d`` should not be replaced with the spelled-out form ``jedan``. |
| 886 |
Either ``%d`` should be kept, or the Plural-Forms expression should be amended, |
| 887 |
so that there is a special case for n=1:: |
| 888 |
. |
| 889 |
. 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 |
| 890 |
. ... |
| 891 |
. msgid "one byte" |
| 892 |
. msgid_plural "%(n)d bytes" |
| 893 |
. msgstr[0] "%(n)d bajt" |
| 894 |
. msgstr[1] "%(n)d bajta" |
| 895 |
. msgstr[2] "%(n)d bajtova" |
| 896 |
. msgstr[3] "jedan bajt" |
| 897 |
references = |
| 898 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 899 |
https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-forms.html |
| 900 |
|
| 901 |
[python-format-string-multiple-unnamed-arguments] |
| 902 |
severity = serious |
| 903 |
certainty = possible |
| 904 |
description = |
| 905 |
A Python format string uses multiple unnamed arguments (such as ``%d``). |
| 906 |
The translator might need to reorder the arguments to properly translate the message, |
| 907 |
but this is not possible with unnamed arguments. |
| 908 |
Named arguments (such as ``%(num)d``) should be used instead. |
| 909 |
references = |
| 910 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 911 |
https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python |
| 912 |
|
| 913 |
[python-format-string-obsolete-conversion] |
| 914 |
severity = pedantic |
| 915 |
certainty = possible |
| 916 |
description = |
| 917 |
A Python format string uses an obsolete conversion specifier: |
| 918 |
. |
| 919 |
* Use ``%d`` instead of ``%u``. |
| 920 |
references = |
| 921 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 922 |
|
| 923 |
[python-format-string-redundant-flag] |
| 924 |
severity = pedantic |
| 925 |
certainty = possible |
| 926 |
description = |
| 927 |
A Python format string includes a redundant character flag. |
| 928 |
Either it's a duplicate, or it has no effect: |
| 929 |
. |
| 930 |
* The ``+`` flag overrides the *space* flag. |
| 931 |
* The ``-`` flag overrides the ``0`` flag. |
| 932 |
* If a precision is given, the ``0`` flag has no effect on integer conversions (``%d``, ``%i``, ``%o``, ``%u``, ``%x``, and ``%X``). |
| 933 |
references = |
| 934 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 935 |
|
| 936 |
[python-format-string-redundant-length] |
| 937 |
severity = pedantic |
| 938 |
certainty = possible |
| 939 |
description = |
| 940 |
A Python format string includes a redundant length modifier. |
| 941 |
Length modifiers (``h``, ``l``, or ``L``) have no effect in Python. |
| 942 |
references = |
| 943 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 944 |
|
| 945 |
[python-format-string-redundant-precision] |
| 946 |
severity = pedantic |
| 947 |
certainty = possible |
| 948 |
description = |
| 949 |
A C format string includes precision that has no effect on the conversion. |
| 950 |
references = |
| 951 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 952 |
|
| 953 |
[python-format-string-unknown-argument] |
| 954 |
severity = serious |
| 955 |
certainty = possible |
| 956 |
description = |
| 957 |
A Python format string for ``msgid`` uses a named argument that isn't used in ``msgid_plural``; |
| 958 |
or ``msgstr`` uses a named argument that isn't used in ``msgid``; |
| 959 |
or ``msgstr[``\ *N*\ ``]`` uses a named argument that isn't used in corresponding ``msgid`` or ``msgid_plural``. |
| 960 |
This indicates that the conversion would try to consume an argument that weren't supplied. |
| 961 |
references = |
| 962 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 963 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 964 |
|
| 965 |
[python-format-string-unnamed-plural-argument] |
| 966 |
severity = wishlist |
| 967 |
certainty = possible |
| 968 |
description = |
| 969 |
A Python format string uses an unnamed arguments (such as ``%d``) |
| 970 |
in the context of plural forms. |
| 971 |
The translator might want not to use the numeric argument in the singular form; |
| 972 |
but this is not possible if the argument is unnamed, |
| 973 |
because Python, unlike C, requires that all unnamed arguments must be consumed during conversion. |
| 974 |
Named arguments (such as ``%(n)d``) should be used instead. |
| 975 |
references = |
| 976 |
https://docs.python.org/2/library/stdtypes.html#string-formatting-operations |
| 977 |
https://www.gnu.org/software/gettext/manual/html_node/Python.html#Python |
| 978 |
|
| 979 |
[qt-plural-format-mistaken-for-c-format] |
| 980 |
severity = important |
| 981 |
certainty = possible |
| 982 |
description = |
| 983 |
A ``c-format`` flag is associated with the message, |
| 984 |
but ``qt-plural-format`` should be used instead. |
| 985 |
. |
| 986 |
The only C format directive that the message uses is ``%n``. |
| 987 |
It is very atypical to use it alone in a C format string. |
| 988 |
references = |
| 989 |
https://doc.qt.io/qt-6/i18n-source-translation.html#handle-plural-forms |
| 990 |
printf(3) |
| 991 |
|
| 992 |
[range-flag-without-plural-string] |
| 993 |
severity = normal |
| 994 |
certainty = certain |
| 995 |
description = |
| 996 |
A ``range:`` flag is associated with a message that doesn't have plural string. |
| 997 |
``range:`` flags only make sense for translations involving plural forms. |
| 998 |
references = |
| 999 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1000 |
|
| 1001 |
[redundant-message-flag] |
| 1002 |
severity = pedantic |
| 1003 |
certainty = certain |
| 1004 |
description = |
| 1005 |
A flag associated with one of the messages is redundant, |
| 1006 |
because it's implied by another flag. |
| 1007 |
references = |
| 1008 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1009 |
|
| 1010 |
[stray-header-line] |
| 1011 |
severity = important |
| 1012 |
certainty = certain |
| 1013 |
description = |
| 1014 |
The header contains a line that does not belong to any header field. |
| 1015 |
Note that RFC-822-style folding of long headers is not supported. |
| 1016 |
references = |
| 1017 |
https://lists.gnu.org/archive/html/bug-gettext/2012-12/msg00010.html |
| 1018 |
|
| 1019 |
[stray-previous-msgid] |
| 1020 |
severity = minor |
| 1021 |
certainty = certain |
| 1022 |
description = |
| 1023 |
The message entry contains annotations about previous untranslated string |
| 1024 |
(``#| msgid``\ *...*), |
| 1025 |
even though the message is not marked as fuzzy. |
| 1026 |
These annotations are only useful for fuzzy messages, |
| 1027 |
and should be removed when unfuzzying. |
| 1028 |
references = |
| 1029 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1030 |
|
| 1031 |
[syntax-error-in-plural-forms] |
| 1032 |
severity = serious |
| 1033 |
certainty = certain |
| 1034 |
description = |
| 1035 |
Value of the Plural-Forms header field could not be parsed. |
| 1036 |
It should be in the form ``nplurals=``\ *n*\ ``; plural=``\ *expression*. |
| 1037 |
references = |
| 1038 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 1039 |
|
| 1040 |
[syntax-error-in-po-file] |
| 1041 |
severity = serious |
| 1042 |
certainty = possible |
| 1043 |
description = |
| 1044 |
This file couldn't be parsed a PO file. |
| 1045 |
In some rare cases this is due to incorrect or missing encoding declaration. |
| 1046 |
references = |
| 1047 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1048 |
https://bugs.debian.org/692283 |
| 1049 |
|
| 1050 |
[syntax-error-in-unused-plural-forms] |
| 1051 |
severity = important |
| 1052 |
certainty = certain |
| 1053 |
description = |
| 1054 |
Value of the Plural-Forms header field could not be parsed. |
| 1055 |
(But there are no translated messages which use plural forms.) |
| 1056 |
It should be in the form ``nplurals=``\ *n*\ ``; plural=``\ *expression*. |
| 1057 |
references = |
| 1058 |
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html |
| 1059 |
|
| 1060 |
[trailing-junk-in-plural-forms] |
| 1061 |
severity = important |
| 1062 |
certainty = certain |
| 1063 |
description = |
| 1064 |
The Plural-Forms header field contains unexpected text after the plural expression. |
| 1065 |
. |
| 1066 |
GNU gettext runtime ignores such trailing junk, |
| 1067 |
but other header parsers might be less liberal in what they accept. |
| 1068 |
|
| 1069 |
[translation-in-template] |
| 1070 |
severity = minor |
| 1071 |
certainty = certain |
| 1072 |
description = |
| 1073 |
The PO template file contains a translated message. |
| 1074 |
|
| 1075 |
[unable-to-determine-language] |
| 1076 |
severity = normal |
| 1077 |
certainty = wild-guess |
| 1078 |
description = |
| 1079 |
i18nspector was unable to determine language of this file. |
| 1080 |
Absence of this information will prevent it from performing further checks. |
| 1081 |
|
| 1082 |
[unexpected-flag-for-header-entry] |
| 1083 |
severity = normal |
| 1084 |
certainty = possible |
| 1085 |
description = |
| 1086 |
An unexpected flag is associated with the header entry. |
| 1087 |
The only flag that makes sense for the header entry is ``fuzzy``. |
| 1088 |
references = |
| 1089 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1090 |
|
| 1091 |
[unknown-encoding] |
| 1092 |
severity = important |
| 1093 |
certainty = possible |
| 1094 |
description = |
| 1095 |
This file declares an encoding that couldn't be recognized by i18nspector. |
| 1096 |
It might be a typo. |
| 1097 |
Absence of encoding information will prevent i18nspector from performing |
| 1098 |
further checks. |
| 1099 |
|
| 1100 |
[unknown-file-type] |
| 1101 |
severity = normal |
| 1102 |
certainty = wild-guess |
| 1103 |
description = |
| 1104 |
File format of this file couldn't be recognized. |
| 1105 |
It might be a bug in i18nspector. |
| 1106 |
|
| 1107 |
[unknown-header-field] |
| 1108 |
severity = minor |
| 1109 |
certainty = wild-guess |
| 1110 |
description = |
| 1111 |
The header field name is unknown to i18nspector. |
| 1112 |
It might be a typo or a capitalization error |
| 1113 |
(header field names are case-sensitive). |
| 1114 |
references = |
| 1115 |
https://lists.gnu.org/archive/html/bug-gettext/2012-12/msg00010.html |
| 1116 |
|
| 1117 |
[unknown-message-flag] |
| 1118 |
severity = normal |
| 1119 |
certainty = wild-guess |
| 1120 |
description = |
| 1121 |
An unknown flag is associated with one of the messages. |
| 1122 |
It might be a typo. |
| 1123 |
references = |
| 1124 |
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html |
| 1125 |
|
| 1126 |
[unknown-poedit-language] |
| 1127 |
severity = minor |
| 1128 |
certainty = wild-guess |
| 1129 |
description = |
| 1130 |
Language declared in X-Poedit-Language couldn't be recognized. |
| 1131 |
It might be a bug in i18nspector. |
| 1132 |
|
| 1133 |
[unrepresentable-characters] |
| 1134 |
severity = serious |
| 1135 |
certainty = possible |
| 1136 |
description = |
| 1137 |
The declared encoding cannot represent all characters commonly used in this language. |
| 1138 |
This is a strong indication that the declared encoding is incorrect. |
| 1139 |
|
| 1140 |
[unusual-character-in-header-entry] |
| 1141 |
severity = important |
| 1142 |
certainty = certain |
| 1143 |
description = |
| 1144 |
The header entry contains an unusual character. |
| 1145 |
This is usually an indication of an encoding problem, such as: |
| 1146 |
. |
| 1147 |
* using ISO 2022 escape sequences, or |
| 1148 |
* using UTF-8 despite declaring an 8-bit encoding. |
| 1149 |
references = |
| 1150 |
https://www.unicode.org/faq/utf_bom.html#bom6 |
| 1151 |
|
| 1152 |
[unusual-character-in-translation] |
| 1153 |
severity = important |
| 1154 |
certainty = possible |
| 1155 |
description = |
| 1156 |
One of the translated messages contains an unusual character. |
| 1157 |
This is usually an indication of an encoding problem, such as: |
| 1158 |
. |
| 1159 |
* using ISO 2022 escape sequences, or |
| 1160 |
* using UTF-8 despite declaring an 8-bit encoding. |
| 1161 |
references = |
| 1162 |
https://www.unicode.org/faq/utf_bom.html#bom6 |
| 1163 |
|
| 1164 |
[unusual-plural-forms] |
| 1165 |
severity = serious |
| 1166 |
certainty = possible |
| 1167 |
description = |
| 1168 |
The Plural-Forms declaration is incorrect (or unusual), |
| 1169 |
according to i18nspector's linguistic data. |
| 1170 |
|
| 1171 |
[unusual-unused-plural-forms] |
| 1172 |
severity = normal |
| 1173 |
certainty = possible |
| 1174 |
description = |
| 1175 |
The Plural-Forms declaration is incorrect (or unusual), |
| 1176 |
according to i18nspector's linguistic data. |
| 1177 |
(But there are no translated messages which use plural forms.) |
| 1178 |
|
| 1179 |
# vim:ft=dosini |