# Checks and fixups
The quality checks help catch common translator errors, ensuring the
translation is in good shape. The checks can be ignored in case of false positives.
For practical translation guidance around placeholders, markup, punctuation,
and plural forms, see [Translating special text safely](https://docs.weblate.org/en/weblate-2026.10/user/translating.md#translating-special-text).
Once submitting a translation with a failing check, this is immediately shown to
the user:
Checks on the edited string update immediately. Related warnings for
[inconsistent translations](#check-inconsistent) and
[reused translations](#check-reused) update in the background, so warnings
and statistics on other strings can briefly reflect the previous translation.
## Automatic fixups
In addition to [Quality checks](#checks), Weblate can fix some common
errors in translated strings automatically. Use it with caution to not have
it add errors.
#### SEE ALSO
[`AUTOFIX_LIST`](https://docs.weblate.org/en/weblate-2026.10/admin/config.md#std-setting-AUTOFIX_LIST)
### Trailing ellipsis replacer
* **Class name:**
`weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis`
Replace trailing dots (`...`) with an ellipsis (`…`) to make it consistent with the source string.
### Zero-width space removal
* **Class name:**
`weblate.trans.autofixes.chars.RemoveZeroSpace`
Zero width space is typically not desired in the translation. This fix will
remove it unless it is present in the source string as well.
### Control characters removal
* **Class name:**
`weblate.trans.autofixes.chars.RemoveControlChars`
Removes control characters if the source does not contain any.
### Devanagari danda
* **Class name:**
`weblate.trans.autofixes.chars.DevanagariDanda`
Replaces sentence full stop in Bangla by the Devanagari danda character (`।`).
### Punctuation spacing
* **Class name:**
`weblate.trans.autofixes.chars.PunctuationSpacing`
#### Versionadded
Added in version 5.3.
Ensures French uses correct punctuation spacing.
This fixup can be disabled via `ignore-punctuation-spacing` flag (which also
disables [Punctuation spacing](#check-punctuation-spacing)).
### Unsafe HTML cleanup
* **Class name:**
`weblate.trans.autofixes.html.BleachHTML`
Removes unsafe HTML markup from strings flagged as `safe-html`.
#### SEE ALSO
[Unsafe HTML](#check-safe-html)
### Trailing and leading whitespace fixer
* **Class name:**
`weblate.trans.autofixes.whitespace.SameBookendingWhitespace`
Makes leading and trailing whitespace consistent with the source string. The
behavior can be fine-tuned using `ignore-begin-space` and
`ignore-end-space` flags to skip processing parts of the string.
## Quality checks
Weblate employs a wide range of quality checks on strings. The following section
describes them all in further detail. There are also language specific checks.
Please file a bug if anything is reported in error.
#### SEE ALSO
* [`CHECK_LIST`](https://docs.weblate.org/en/weblate-2026.10/admin/config.md#std-setting-CHECK_LIST)
* [Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)
AI quality checks are populated asynchronously by the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality). Each category groups
the evaluator’s findings, including their severity and explanation, and uses the
same filtering and ignore controls as other checks. AI evaluation runs only
during add-on runs, according to its configured triggers. Regular quality check
processing does not contact the evaluator or create new AI findings; it only
retains existing findings or removes them when the source or translation changes.
## Translation checks
Executed upon every translation change, helping translators maintain
good quality translations.
### Accelerator key
#### Versionadded
Added in version 2026.7.
* **Summary:**
Source and translation contain inconsistent accelerator keys.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.AcceleratorKeyCheck`
* **Check identifier:**
`accelerator`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`accelerator`
* **Flag to ignore:**
`ignore-accelerator`
Accelerator keys (also known as mnemonics) let users trigger a UI action from
the keyboard. They are marked in the string by a single punctuation character,
typically `&` (Qt, Windows), `_` (GTK), or `~`. Literal marker characters
can usually be escaped by doubling them, and are ignored by this check. Enable
this check with the `accelerator:` flag to explicitly choose the marker, for
example `accelerator:&`, `accelerator:_`, or `accelerator:~`.
This check verifies that the source and the translation contain the same number
of accelerator keys, and that the translation does not contain more than one.
#### NOTE
A string such as `Walter & Sons` might be translated without the
ampersand and trigger a false positive. Use the `ignore-accelerator`
flag to skip the check for such strings.
### AI: Accuracy
* **Summary:**
The evaluation detected a change in meaning.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ai.AIAccuracyCheck`
* **Check identifier:**
`ai_accuracy`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ai-accuracy`
This check is populated only when the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality) runs.
Regular quality check processing does not trigger AI evaluation.
### AI: Fluency
* **Summary:**
The evaluation detected a language quality issue.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ai.AIFluencyCheck`
* **Check identifier:**
`ai_fluency`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ai-fluency`
This check is populated only when the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality) runs.
Regular quality check processing does not trigger AI evaluation.
### AI: Formatting
* **Summary:**
The evaluation detected a formatting or placeholder issue.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ai.AIFormattingCheck`
* **Check identifier:**
`ai_formatting`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ai-formatting`
This check is populated only when the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality) runs.
Regular quality check processing does not trigger AI evaluation.
### AI: Style
* **Summary:**
The evaluation detected a style or instruction mismatch.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ai.AIStyleCheck`
* **Check identifier:**
`ai_style`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ai-style`
This check is populated only when the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality) runs.
Regular quality check processing does not trigger AI evaluation.
### AI: Terminology
* **Summary:**
The evaluation detected incorrect terminology.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ai.AITerminologyCheck`
* **Check identifier:**
`ai_terminology`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ai-terminology`
This check is populated only when the
[AI quality evaluation add-on](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-ai-quality) runs.
Regular quality check processing does not trigger AI evaluation.
### AsciiDoc markup
#### Versionadded
Added in version 2026.8.
* **Summary:**
AsciiDoc markup does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.AsciiDocMarkupCheck`
* **Check identifier:**
`asciidoc-markup`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[AsciiDoc files](https://docs.weblate.org/en/weblate-2026.10/formats/asciidoc.md#asciidoc)
* **Flag to enable:**
`asciidoc-text`
* **Flag to ignore:**
`ignore-asciidoc-markup`
This check compares the markups found in the source with the markups found in the translation.
It includes:
- inline and block macros (e.g. `link:` and `image::`)
- cross-references (`<>`)
- passthroughs (e.g. `+++...+++`, `$$...$$`)
Macro attribute text and cross-reference labels may be translated; the
macro name, target, and reference identifier must stay the same in both the source and the translation.
### BBCode markup
#### Versionchanged
Changed in version 5.10: This checks no longer relies on unreliable automatic detection, it now needs to be turned on using the `bbcode-text` flag.
* **Summary:**
BBCode in translation does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.BBCodeCheck`
* **Check identifier:**
`bbcode`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`bbcode-text`
* **Flag to ignore:**
`ignore-bbcode`
BBCode represents simple markup, like for example highlighting important parts of a
message in bold font, or italics.
This check ensures they are also found in translation.
It recognizes parameters on opening tags, nested tags, and markup spanning lines.
#### NOTE
The method for detecting BBCode is currently quite simple so this check
might produce false positives.
### Chars around XML tags
* **Summary:**
Characters surrounding XML tags in translation do not align with source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.XMLCharsAroundTagsCheck`
* **Check identifier:**
`xml-chars-around-tags`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-xml-chars-around-tags`
Checks that the characters surrounding an XML tag are consistent between both
source and translation. Ensures letters are not replaced with non-letters, and vice versa.
#### NOTE
This check is disabled by the `safe-html` flag as the HTML cleanup done by
it can produce HTML markup which is not valid XML.
### Consecutive duplicated words
#### Versionadded
Added in version 4.1.
* **Summary:**
Text contains the same word twice in a row.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.duplicate.DuplicateCheck`
* **Check identifier:**
`duplicate`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-duplicate`
Checks that no consecutive duplicate words occur in a translation. This usually
indicates a mistake in the translation.
The check is skipped for Assamese, Bengali, Gujarati, Hindi, Kannada, Malayalam,
Marathi, Nepali, Odia, Punjabi, Sindhi, Sinhala, Tamil, Telugu, Toki Pona, and Urdu,
including their language variants, because word repetition carries grammatical
meaning in these languages.
#### HINT
This check includes language specific rules to avoid false positives. In
case it triggers falsely in your case, let us know. See [Reporting issues in Weblate](https://docs.weblate.org/en/weblate-2026.10/contributing/issues.md#report-issue).
### Does not follow glossary
#### Versionadded
Added in version 4.5.
* **Summary:**
The translation does not follow terms defined in a glossary.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.glossary.GlossaryCheck`
* **Check identifier:**
`check_glossary`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`check-glossary`
* **Flag to ignore:**
`ignore-check-glossary`
This check has to be turned on using `check-glossary` flag (see
[Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)). Please consider following prior to enabling it:
* It does exact string matching, the glossary is expected to contain terms in all variants.
* Checking each string against glossary is expensive, it will slow down any operation in Weblate which involves running checks like importing strings or translating.
* It also utilizes untranslatable glossary terms in [Unchanged translation](#check-same).
#### SEE ALSO
* [Glossary](https://docs.weblate.org/en/weblate-2026.10/user/glossary.md#glossary)
* [Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)
* [Translation flags](https://docs.weblate.org/en/weblate-2026.10/admin/projects.md#component-check-flags)
### Double space
* **Summary:**
Translation contains double space.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.DoubleSpaceCheck`
* **Check identifier:**
`double_space`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-double-space`
Checks that double space is present in translation to avoid false positives on other space-related checks.
Check is false when double space is found in source meaning double space is intentional.
### Fluent parts
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent parts should match.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.fluent.parts.FluentPartsCheck`
* **Check identifier:**
`fluent-parts`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-parts`
* **Flag to ignore:**
`ignore-fluent-parts`
Each Fluent Message can have an optional value (the main text content), and
optional attributes, each of which is a “part” of the Message. In Weblate, all
these parts appear within the same block, using Fluent-like syntax to specify
the attributes. For example:
```text
This is the Message value
.title = This is the title attribute
.alt = This is the alt attribute
```
This check ensures that the translated Message also has a value if the source
Message has one, or no value if the source has none. This also checks that the
same attributes used in the source Message also appear in the translation, with
no additions.
#### NOTE
This check is not applied to Fluent Terms since Terms always have a value, and
Term attributes tend to be locale-specific (used for grammar rules, etc.), and
are not expected to appear in all translations.
#### SEE ALSO
[Fluent Attributes](https://projectfluent.org/fluent/guide/attributes.html)
### Fluent references
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent references should match.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.fluent.references.FluentReferencesCheck`
* **Check identifier:**
`fluent-references`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-references`
* **Flag to ignore:**
`ignore-fluent-references`
A Fluent Message or Term can reference another Message, Term, Attribute, or a
variable. For example:
```text
Here is a { message }, a { message.attribute } a { -term } and a { $variable }.
Within a function { NUMBER($num, minimumFractionDigits: 2) }
```
Generally, translated Messages or Terms are expected to contain the same
references as the source, although not necessarily in the same order of
appearance. So this check ensures that translations use the same references in
their value as the source value, the same number of times, and with no
additions. For Messages, this will also check that each Attribute in the
translation uses the same references as the matching Attribute in the source.
When the source or translation contains Fluent Select Expressions, then each
possible variant in the source must be matched with at least one variant in the
translation with the same references, and vice versa.
Moreover, if a variable reference appears both in the Select Expression’s
selector and within one of its variants, then all variants may also be
considered as if they also contain that reference. The assumption being that the
variant’s key may have made the reference redundant for that variant. For
example:
```text
{ $num ->
[one] an apple
*[other] { $num } apples
}
```
Here, for the purposes of this check, the `[one]` variant will also be
considered to contain the `$num` reference.
However, a reference within the Select Expression’s selector, which can only be
a variable of a Term Attribute in Fluent’s syntax, will not by itself count as a
required reference because they do not form the actual text content of the
string that the end-user will see, and the presence of a Select Expression is
considered locale-specific. For example:
```text
{ -term.starts-with-vowel ->
[yes] an { -term }
*[no] a { -term }
}
```
Here a reference to `-term.starts-with-vowel` is not expected to appear in
translations, but a reference to `-term` is.
#### SEE ALSO
[Fluent Variables](https://projectfluent.org/fluent/guide/variables.html)
[Fluent Message and Term references](https://projectfluent.org/fluent/guide/references.html)
[Fluent Select Expressions](https://projectfluent.org/fluent/guide/selectors.html)
### Fluent translation inner HTML
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent target should be valid inner HTML that matches.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.fluent.inner_html.FluentTargetInnerHTMLCheck`
* **Check identifier:**
`fluent-target-inner-html`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-target-inner-html`
* **Flag to ignore:**
`ignore-fluent-target-inner-html`
This check will verify that the translated value of a Message or Term contains
the same HTML elements as the source value.
First, if the source value fails the [Fluent source inner HTML](#check-fluent-source-inner-html)
check, then this check will do nothing. Otherwise, the translated value will
also be checked under the same conditions.
Second, the HTML elements found in the translated value will be compared against
the HTML elements found in the source value. Two elements will match if they
share the exact same tag name, the exact same attributes and values, and all
their ancestors match in the same way. This check will ensure that all the
elements in the source appear somewhere in the translation, with the same
*number* of appearances, and with no additional elements added. When there are
multiple elements in the value, they need not appear in the same order in the
translation value.
When the source or translation contains Fluent Select Expressions, then each
possible variant in the source must be matched with at least one variant in the
translation with the same HTML elements, and vice versa.
When using Fluent in combination with the Fluent DOM package, this check will
ensure that the translation also includes any required `data-l10n-name`
elements that appear in the source, or any of the allowed inline elements like
`
`.
For example, the following source:
```text
Source message ![]()
with icon
```
would match with:
```text
Translated message ![]()
with icon
```
but not:
```text
Translated message ![]()
with icon
```
nor
```text
Translated message
with no icon
```
#### SEE ALSO
* [Fluent source inner HTML](#check-fluent-source-inner-html)
* [Fluent DOM](https://projectfluent.org/dom-l10n-documentation/overview.html)
### Fluent translation syntax
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent syntax error in the translation.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.fluent.syntax.FluentTargetSyntaxCheck`
* **Check identifier:**
`fluent-target-syntax`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-target-syntax`
* **Flag to ignore:**
`ignore-fluent-target-syntax`
In Weblate, Fluent strings use Fluent syntax for references and variables, but
also for more complex features like defining attributes and selector variants,
including plurals. This check ensures that the syntax used in the translation
will be valid for Fluent.
#### SEE ALSO
* [Fluent source syntax](#check-fluent-source-syntax)
* [Fluent Syntax Guide](https://projectfluent.org/fluent/guide/)
* [Mozilla Basic Syntax Guide](https://mozilla-l10n.github.io/localizer-documentation/tools/fluent/basic_syntax.html)
### Formatted strings
Checks that the formatting in strings is replicated between both source and translation.
Omitting format strings in translation usually causes severe problems, so the formatting in strings
should usually match the source.
Weblate supports checking format strings in several languages. The check is not
enabled automatically, only if a string is flagged appropriately (e.g.
c-format for C format). Gettext adds this automatically, but you will
probably have to add it manually for other file formats or if your PO files are
not generated by **xgettext**.
Most of the format checks allow omitting format strings for plural forms having
a single count. This allows translators to write nicer strings for these cases
(One apple instead of %d apple). Turn this off by adding `strict-format` flag.
The flags can be customized per string (see [Additional info on source strings](https://docs.weblate.org/en/weblate-2026.10/admin/translating.md#additional)) or in a [Component configuration](https://docs.weblate.org/en/weblate-2026.10/admin/projects.md#component).
Having it defined per component is simpler, but it can lead to false positives in
case the string is not interpreted as a formatting string, but format string syntax
happens to be used.
#### HINT
In case specific format check is not available in Weblate, you can use
generic [Placeholders](#check-placeholders).
Besides checking, this will also highlight the formatting strings to easily
insert them into translated strings:
#### AngularJS interpolation string
* **Summary:**
AngularJS interpolation strings do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.angularjs.AngularJSInterpolationCheck`
* **Check identifier:**
`angularjs_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`angularjs-format`
* **Flag to ignore:**
`ignore-angularjs-format`
* **Named format string example:**
`Your balance is {{amount}} {{ currency }}`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [AngularJS text interpolation](https://angular.io/guide/interpolation)
#### Automattic components formatting
* **Summary:**
The Automattic components’ placeholders do not match the source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.AutomatticComponentsCheck`
* **Check identifier:**
`automattic_components_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`automattic-components-format`
* **Flag to ignore:**
`ignore-automattic-components-format`
* **Simple format string example:**
`They bought {{strong}}apples{{/strong}}.`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Interpolate Components](https://github.com/Automattic/wp-calypso/tree/trunk/packages/interpolate-components)
#### C format
* **Summary:**
C format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.CFormatCheck`
* **Check identifier:**
`c_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`c-format`
* **Flag to ignore:**
`ignore-c-format`
* **Simple format string example:**
`There are %d apples`
* **Position format string example:**
`Your balance is %1$d %2$s`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [C format strings](https://www.gnu.org/software/gettext/manual/html_node/c_002dformat.html)
* [C printf format](https://en.wikipedia.org/wiki/Printf_format_string)
#### C# format
* **Summary:**
C# format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.CSharpFormatCheck`
* **Check identifier:**
`c_sharp_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[ResourceDictionary files](https://docs.weblate.org/en/weblate-2026.10/formats/resourcedict.md#resourcedictionary)
* **Flag to enable:**
`c-sharp-format`, `csharp-format`
* **Flag to ignore:**
`ignore-c-sharp-format`
* **Position format string example:**
`There are {0} apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [C# String Format](https://learn.microsoft.com/en-us/dotnet/api/system.string.format?view=netframework-4.7.2)
#### ECMAScript template literals
* **Summary:**
ECMAScript template literals do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.ESTemplateLiteralsCheck`
* **Check identifier:**
`es_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[draggable/i18n lang files](https://docs.weblate.org/en/weblate-2026.10/formats/mi18n.md#mi18n-lang)
* **Flag to enable:**
`es-format`
* **Flag to ignore:**
`ignore-es-format`
* **Interpolation example:**
`There are ${number} apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals)
#### i18next interpolation
#### Versionadded
Added in version 4.0.
* **Summary:**
The i18next interpolation does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.I18NextInterpolationCheck`
* **Check identifier:**
`i18next_interpolation`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[i18next JSON files](https://docs.weblate.org/en/weblate-2026.10/formats/i18next.md#i18next), [i18next JSON files](https://docs.weblate.org/en/weblate-2026.10/formats/i18next.md#i18nextv4)
* **Flag to enable:**
`i18next-interpolation`
* **Flag to ignore:**
`ignore-i18next-interpolation`
* **Interpolation example:**
`There are {{number}} apples`
* **Nesting example:**
`There are $t(number) apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [i18next interpolation](https://www.i18next.com/translation-function/interpolation)
#### ICU MessageFormat
#### Versionadded
Added in version 4.9.
* **Summary:**
Syntax errors and/or placeholder mismatches in ICU MessageFormat strings.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.icu.ICUMessageFormatCheck`
* **Check identifier:**
`icu_message_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[ARB File](https://docs.weblate.org/en/weblate-2026.10/formats/arb.md#arb), [Format.JS JSON file](https://docs.weblate.org/en/weblate-2026.10/formats/formatjs.md#formatjs)
* **Flag to enable:**
`icu-message-format`
* **Flag to ignore:**
`ignore-icu-message-format`
* **Interpolation example:**
`There {number, plural, one {is one apple} other {are # apples}}.`
This check has support for both pure ICU MessageFormat messages as well as ICU with simple
XML tags. You can configure the behavior of this check by using `icu-flags:*`, either by
opting into XML support or by disabling certain sub-checks. For example, the following flag
enables XML support while disabling validation of plural sub-messages:
```text
icu-message-format, icu-flags:xml:-plural_selectors
```
| `xml` | Enable support for simple XML tags. By default, XML tags
are parsed loosely. Stray `<` characters are ignored
if they are not reasonably part of a tag. |
|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `strict-xml` | Enable support for strict XML tags. All `<` characters
must be escaped if they are not part of a tag. |
| `-highlight` | Disable highlighting placeholders in the editor. |
| `-require_other` | Disable requiring sub-messages to have an `other`
selector. |
| `-submessage_selectors` | Skip checking that sub-message selectors match the source. |
| `-types` | Skip checking that placeholder types match the source. |
| `-extra` | Skip checking that no placeholders are present that were
not present in the source string. |
| `-missing` | Skip checking that no placeholders are missing that were
present in the source string. |
Additionally, when `strict-xml` is not enabled but `xml` is enabled, you can use the
`icu-tag-prefix:PREFIX` flag to require that all XML tags start with a specific string.
For example, the following flag will only allow XML tags to be matched if they start with
`click here` but not `this`.
#### SEE ALSO
* [ICU MessageFormat syntax](#check-icu-message-format-syntax)
* [Formatted strings](#check-formats)
* [ICU: Formatting Messages](https://unicode-org.github.io/icu/userguide/format_parse/messages/)
* [Format.JS: Message Syntax](https://formatjs.github.io/docs/core-concepts/icu-syntax)
#### Java format
* **Summary:**
Java format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.JavaFormatCheck`
* **Check identifier:**
`java_printf_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Android string resources](https://docs.weblate.org/en/weblate-2026.10/formats/android.md#aresource), [Mobile Kotlin resources](https://docs.weblate.org/en/weblate-2026.10/formats/moko-resources.md#moko-resource), [Compose Multiplatform resources](https://docs.weblate.org/en/weblate-2026.10/formats/compose-multiplatform-resources.md#cmp-resource)
* **Flag to enable:**
`java-printf-format`
* **Flag to ignore:**
`ignore-java-printf-format`
* **Simple format string example:**
`There are %d apples`
* **Position format string example:**
`Your balance is %1$d %2$s`
#### Versionchanged
Changed in version 4.14: This used to be toggled by the `java-format` flag, it was changed for consistency with GNU gettext.
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Java Format Strings](https://docs.oracle.com/javase/7/docs/api/java/util/Formatter.html)
#### Java MessageFormat
* **Summary:**
Java MessageFormat string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.JavaMessageFormatCheck`
* **Check identifier:**
`java_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Java properties](https://docs.weblate.org/en/weblate-2026.10/formats/java.md#properties), [GWT properties](https://docs.weblate.org/en/weblate-2026.10/formats/gwt.md#gwt)
* **Flag to enable:**
`auto-java-messageformat`, `java-format`
* **Automatic flag behavior:**
`auto-java-messageformat`: Treat a text as conditional Java MessageFormat, enabling [Java MessageFormat](#check-java-format) only when the source contains Java MessageFormat placeholders.
* **Flag to ignore:**
`ignore-java-format`
* **Position format string example:**
`There are {0} apples`
#### Versionchanged
Changed in version 4.14: This used to be toggled by `java-messageformat` flag, it was changed for consistency with GNU gettext.
This check validates that format string is valid for the Java MessageFormat
class. Besides matching format strings in the curly braces, it also verifies
single quotes as they have a special meaning. Whenever writing single quote, it
should be written as `''`. When not paired, it is treated as beginning of
quoting and will not be shown when rendering the string.
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Java MessageFormat](https://docs.oracle.com/javase/7/docs/api/java/text/MessageFormat.html)
#### JavaScript format
* **Summary:**
JavaScript format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.JavaScriptFormatCheck`
* **Check identifier:**
`javascript_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`javascript-format`
* **Flag to ignore:**
`ignore-javascript-format`
* **Simple format string example:**
`There are %d apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [JavaScript formatting strings](https://www.gnu.org/software/gettext/manual/html_node/javascript_002dformat.html)
#### Laravel format
* **Summary:**
Laravel format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.LaravelFormatCheck`
* **Check identifier:**
`laravel_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Laravel PHP strings](https://docs.weblate.org/en/weblate-2026.10/formats/laravel.md#laravel)
* **Flag to enable:**
`laravel-format`
* **Flag to ignore:**
`ignore-laravel-format`
* **Named format string example:**
`The :attribute must be :value`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Laravel translation formatting](https://laravel.com/framework/docs/localization#replacing-parameters-in-translation-strings)
#### Lua format
* **Summary:**
Lua format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.LuaFormatCheck`
* **Check identifier:**
`lua_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`lua-format`
* **Flag to ignore:**
`ignore-lua-format`
* **Simple format string example:**
`There are %d apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Lua formatting strings](https://www.gnu.org/software/gettext/manual/html_node/lua_002dformat.html#lua_002dformat)
#### Object Pascal format
* **Summary:**
Object Pascal format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.ObjectPascalFormatCheck`
* **Check identifier:**
`object_pascal_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`object-pascal-format`
* **Flag to ignore:**
`ignore-object-pascal-format`
* **Simple format string example:**
`There are %d apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Object Pascal formatting strings](https://www.gnu.org/software/gettext/manual/html_node/object_002dpascal_002dformat.html#object_002dpascal_002dformat)
* [Free Pascal formatting strings](https://www.freepascal.org/docs-html/rtl/sysutils/format.html)
* [Delphi formatting strings](https://docwiki.embarcadero.com/Libraries/Sydney/en/System.SysUtils.Format)
#### Objective-C format
#### Versionadded
Added in version 5.17.
* **Summary:**
Objective-C format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.ObjCFormatCheck`
* **Check identifier:**
`objc_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Apple iOS strings](https://docs.weblate.org/en/weblate-2026.10/formats/apple.md#strings), [Stringsdict format](https://docs.weblate.org/en/weblate-2026.10/formats/stringsdict.md#stringsdict)
* **Flag to enable:**
`objc-format`
* **Flag to ignore:**
`ignore-objc-format`
#### Percent placeholders
#### Versionadded
Added in version 4.0.
* **Summary:**
The percent placeholders do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PercentPlaceholdersCheck`
* **Check identifier:**
`percent_placeholders`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`percent-placeholders`
* **Flag to ignore:**
`ignore-percent-placeholders`
* **Simple format string example:**
`There are %number% apples`
#### SEE ALSO
[Formatted strings](#check-formats)
#### Perl brace format
* **Summary:**
Perl brace format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PerlBraceFormatCheck`
* **Check identifier:**
`perl_brace_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`perl-brace-format`
* **Flag to ignore:**
`ignore-perl-brace-format`
* **Named format string example:**
`There are {number} apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Perl Format Strings](https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html)
#### Perl format
* **Summary:**
Perl format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PerlFormatCheck`
* **Check identifier:**
`perl_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`perl-format`
* **Flag to ignore:**
`ignore-perl-format`
* **Simple format string example:**
`There are %d apples`
* **Position format string example:**
`Your balance is %1$d %2$s`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Perl sprintf](https://perldoc.perl.org/functions/sprintf)
* [Perl Format Strings](https://www.gnu.org/software/gettext/manual/html_node/perl_002dformat.html)
#### PHP format
* **Summary:**
PHP format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PHPFormatCheck`
* **Check identifier:**
`php_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`php-format`
* **Flag to ignore:**
`ignore-php-format`
* **Simple format string example:**
`There are %d apples`
* **Position format string example:**
`Your balance is %1$d %2$s`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [PHP sprintf documentation](https://www.php.net/manual/en/function.sprintf.php)
* [PHP Format Strings](https://www.gnu.org/software/gettext/manual/html_node/php_002dformat.html)
#### Python brace format
* **Summary:**
Python brace format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PythonBraceFormatCheck`
* **Check identifier:**
`python_brace_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`python-brace-format`
* **Flag to ignore:**
`ignore-python-brace-format`
* **Simple format string:**
`There are {} apples`
* **Named format string example:**
`Your balance is {amount} {currency}`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Python brace format](https://docs.python.org/3/library/string.html#formatstrings)
* [Python Format Strings](https://www.gnu.org/software/gettext/manual/html_node/python_002dformat.html)
#### Python format
* **Summary:**
Python format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.PythonFormatCheck`
* **Check identifier:**
`python_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`python-format`
* **Flag to ignore:**
`ignore-python-format`
* **Simple format string:**
`There are %d apples`
* **Named format string example:**
`Your balance is %(amount)d %(currency)s`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Python string formatting](https://docs.python.org/3/builtins/stdtypes.html#old-string-formatting)
* [Python Format Strings](https://www.gnu.org/software/gettext/manual/html_node/python_002dformat.html)
#### Qt format
* **Summary:**
Qt format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.qt.QtFormatCheck`
* **Check identifier:**
`qt_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`qt-format`
* **Flag to ignore:**
`ignore-qt-format`
* **Position format string example:**
`There are %1 apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Qt QString::arg()](https://doc.qt.io/qt-6/qstring.html#arg)
#### Qt plural format
* **Summary:**
Qt plural format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.qt.QtPluralCheck`
* **Check identifier:**
`qt_plural_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`qt-plural-format`
* **Flag to ignore:**
`ignore-qt-plural-format`
* **Plural format string example:**
`There are %Ln apple(s)`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Qt i18n guide](https://doc.qt.io/qt-6/i18n-source-translation.html#handle-plural-forms)
#### Ruby format
* **Summary:**
Ruby format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.ruby.RubyFormatCheck`
* **Check identifier:**
`ruby_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`ruby-format`
* **Flag to ignore:**
`ignore-ruby-format`
* **Simple format string example:**
`There are %d apples`
* **Position format string example:**
`Your balance is %1$f %2$s`
* **Named format string example:**
`Your balance is %+.2f %s`
* **Named template string:**
`Your balance is %{amount} %{currency}`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Ruby Kernel#sprintf](https://ruby-doc.org/current/Kernel.html#method-i-sprintf)
#### Scheme format
* **Summary:**
Scheme format string does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.SchemeFormatCheck`
* **Check identifier:**
`scheme_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`scheme-format`
* **Flag to ignore:**
`ignore-scheme-format`
* **Simple format string example:**
`There are ~d apples`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Srfi 28](https://srfi.schemers.org/srfi-28/srfi-28.html)
* [Chicken Scheme format](https://wiki.call-cc.org/eggref/5/format)
* [Guile Scheme formatted output](https://www.gnu.org/software/guile/manual/html_node/Formatted-Output.html)
#### Vue I18n formatting
* **Summary:**
The Vue I18n formatting does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.format.VueFormattingCheck`
* **Check identifier:**
`vue_format`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`vue-format`
* **Flag to ignore:**
`ignore-vue-format`
* **Named formatting:**
`There are {count} apples`
* **Rails i18n formatting:**
`There are %{count} apples`
* **Linked locale messages:**
`@:message.dio @:message.the_world!`
#### SEE ALSO
* [Formatted strings](#check-formats)
* [Vue I18n Formatting](https://kazupon.github.io/vue-i18n/guide/formatting.html)
* [Vue I18n Linked locale messages](https://kazupon.github.io/vue-i18n/guide/messages.html#linked-locale-messages)
### Has been translated
* **Summary:**
This string has been translated in the past.
* **Scope:**
all strings
* **Check class:**
`weblate.checks.consistency.TranslatedCheck`
* **Check identifier:**
`translated`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-translated`
Means a string has been translated already. This can happen when the
translations have been reverted in VCS or lost otherwise.
### Inconsistent
* **Summary:**
This string has more than one translation in this project or is untranslated in some components.
* **Scope:**
all strings
* **Check class:**
`weblate.checks.consistency.ConsistencyCheck`
* **Check identifier:**
`inconsistent`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-inconsistent`
Weblate checks translations of the same string across all translation within a
project to help you keep consistent translations.
The check fails on differing translations of one string within a project. This
can also lead to inconsistencies in displayed checks. You can find other
translations of this string on the Other occurrences tab.
This check applies to all components in a project that have
[Allow translation propagation](https://docs.weblate.org/en/weblate-2026.10/admin/projects.md#component-allow-translation-propagation) turned on.
#### HINT
For performance reasons, the check might not find all inconsistencies, it
limits number of matches.
#### NOTE
This check also fires in case the string is translated in one component and
not in another. It can be used as a quick way to manually handle strings
which are untranslated in some components just by clicking on the
Use this translation button displayed on each line in the
Other occurrences tab.
You can use [Automatic translation](https://docs.weblate.org/en/weblate-2026.10/admin/addons.md#addon-weblate-autotranslate-autotranslate) add-on to
automate translating of newly added strings which are already translated in
another component.
#### SEE ALSO
[Keeping translations same across components](https://docs.weblate.org/en/weblate-2026.10/admin/continuous.md#translation-consistency)
### Inconsistent reStructuredText
#### Versionadded
Added in version 5.10.
* **Summary:**
Inconsistent reStructuredText markup in the translated message.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.RSTReferencesCheck`
* **Check identifier:**
`rst-references`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`rst-text`
* **Flag to ignore:**
`ignore-rst-references`
reStructuredText term references or other markup do not match source, the typical causes for these errors are:
* Mismatched or missing backticks.
* Missing spaces or interpunction around the reference. The reStructuredText inline blocks need to be separated by non-word characters.
* Space between inline tag and backticks.
* The reference name is not being translated.
* Using quotes instead of backticks.
* Mismatched substitutions or footnote references.
#### SEE ALSO
* [reStructuredText Primer](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html)
* [reStructuredText syntax error](#check-rst-syntax)
### Kashida letter used
* **Summary:**
The decorative kashida letters should not be used.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.KashidaCheck`
* **Check identifier:**
`kashida`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-kashida`
The decorative Kashida letters should not be used in translation. These are
also known as Tatweel.
#### SEE ALSO
[Kashida on Wikipedia](https://en.wikipedia.org/wiki/Kashida)
### Markdown links
* **Summary:**
Markdown links do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.MarkdownLinkCheck`
* **Check identifier:**
`md-link`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Markdown files](https://docs.weblate.org/en/weblate-2026.10/formats/markdown.md#markdown), [MDX files](https://docs.weblate.org/en/weblate-2026.10/formats/mdx.md#mdx)
* **Flag to enable:**
`md-text`
* **Flag to ignore:**
`ignore-md-link`
Markdown links do not match source.
Link titles are user-visible and should be preserved and translated.
The unchanged-title check respects the language and content exceptions of
[Unchanged translation](#check-same). Links are paired by destination, with localized destinations
paired in their order of appearance.
#### SEE ALSO
[Markdown links](https://spec.commonmark.org/0.31.2/#links)
### Markdown references
* **Summary:**
Markdown link references do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.MarkdownRefLinkCheck`
* **Check identifier:**
`md-reflink`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Markdown files](https://docs.weblate.org/en/weblate-2026.10/formats/markdown.md#markdown), [MDX files](https://docs.weblate.org/en/weblate-2026.10/formats/mdx.md#mdx)
* **Flag to enable:**
`md-text`
* **Flag to ignore:**
`ignore-md-reflink`
Markdown link references do not match source.
#### SEE ALSO
[Markdown links](https://spec.commonmark.org/0.31.2/#links)
### Markdown syntax
* **Summary:**
Markdown syntax does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.MarkdownSyntaxCheck`
* **Check identifier:**
`md-syntax`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Markdown files](https://docs.weblate.org/en/weblate-2026.10/formats/markdown.md#markdown), [MDX files](https://docs.weblate.org/en/weblate-2026.10/formats/mdx.md#mdx)
* **Flag to enable:**
`md-text`
* **Flag to ignore:**
`ignore-md-syntax`
Markdown syntax does not match source
#### SEE ALSO
[Markdown inlines](https://spec.commonmark.org/0.31.2/#inlines)
### Maximum length of translation
* **Summary:**
Translation should not exceed given length.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.MaxLengthCheck`
* **Check identifier:**
`max-length`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`max-length`
* **Flag to ignore:**
`ignore-max-length`
Checks that translations are of acceptable length to fit available space.
This only checks the amount of translation characters.
Unlike the other checks, the flag should be set as a `key:value` pair like
`max-length:100`.
The `max-length` flag also triggers [Source string length](#check-source-max-length) for source
strings. For English source strings, including English variants, this check
warns when the source uses more than 85% of the configured length to leave room
for translation expansion. For other source languages, the configured
`max-length` is used directly.
#### HINT
This check looks at number of characters, which might not be the best metric when
using proportional fonts to render the text. The [Maximum size of translation](#check-max-size) check
does check actual rendering of the text.
The `replacements:` flag might be also useful to expand placeables before
checking the string.
When `xml-text` flag is also used, the length calculation ignores XML tags.
### Maximum number of lines
* **Summary:**
Translation should not exceed given number of lines.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.MaxLinesCheck`
* **Check identifier:**
`max-lines`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`max-lines`
* **Flag to ignore:**
`ignore-max-lines`
Checks that translations do not exceed the configured maximum number of lines.
This is useful for translations targeting fixed-height UI elements such as
displays, terminals, or constrained containers where a specific number of
visible lines is required.
Unlike the other checks, the flag should be set as a `key:value` pair like
`max-lines:3`.
A translation with more lines than the configured value triggers a warning.
Lines are counted by the number of newline characters plus one.
#### HINT
This check counts display lines (separated by `\\n`), not wrapped lines.
If your UI wraps text automatically, use [Maximum size of translation](#check-max-size) instead.
### Maximum size of translation
* **Summary:**
Rendered text should not exceed given size.
* **Scope:**
source and translated strings
* **Check class:**
`weblate.checks.render.MaxSizeCheck`
* **Check identifier:**
`max-size`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`max-size`
* **Flag to ignore:**
`ignore-max-size`
Rendered source or translation text should not exceed given size. It renders the
text and checks if it fits into given boundaries. Word wrapping is applied when
more than one line is configured.
This check needs one or two parameters - maximal width and maximal number of
lines. In case the number of lines is not provided, one line text is
considered.
You can also configure used font by `font-*` directives (see
[Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)), for example following translation flags say that the
text rendered with ubuntu font size 22 should fit into two lines and 500
pixels:
```text
max-size:500:2, font-family:ubuntu, font-size:22
```
#### HINT
You might want to set `font-*` directives in [Component configuration](https://docs.weblate.org/en/weblate-2026.10/admin/projects.md#component) to have the same
font configured for all strings within a component. You can override those
values per string in case you need to customize it per string.
The `replacements:` flag might be also useful to expand placeables before
checking the string.
When `xml-text` flag is also used, the length calculation ignores XML tags.
#### SEE ALSO
* [Managing fonts](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#fonts)
* [Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)
* [Maximum length of translation](#check-max-length)
### Mismatched \\n
* **Summary:**
Number of `\n` literals in translation does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EscapedNewlineCountingCheck`
* **Check identifier:**
`escaped_newline`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-escaped-newline`
Usually escaped newlines are important for formatting program output.
Check fails if the number of `\n` literals in translation does not match the source.
### Mismatched colon
* **Summary:**
Source and translation do not both end with a colon.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndColonCheck`
* **Check identifier:**
`end_colon`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-colon`
Checks that colons are replicated between both source and translation. The
presence of colons is also checked for various languages where they do not
belong (Chinese or Japanese).
#### SEE ALSO
[Colon on Wikipedia](https://en.wikipedia.org/wiki/Colon_(punctuation))
### Mismatched ellipsis
* **Summary:**
Source and translation do not both end with an ellipsis.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndEllipsisCheck`
* **Check identifier:**
`end_ellipsis`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-ellipsis`
Checks that trailing ellipses are replicated between both source and translation.
This only checks for real ellipsis (`…`) not for three dots (`...`).
An ellipsis is usually rendered nicer than three dots in print, and sounds better with text-to-speech.
#### SEE ALSO
[Ellipsis on Wikipedia](https://en.wikipedia.org/wiki/Ellipsis)
### Mismatched exclamation mark
* **Summary:**
Source and translation do not both end with an exclamation mark.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndExclamationCheck`
* **Check identifier:**
`end_exclamation`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-exclamation`
Checks that exclamations are replicated between both source and translation.
The presence of exclamation marks is also checked for various languages where
they do not belong (Chinese, Japanese, Korean, Armenian, Limbu, Myanmar or
Nko).
#### SEE ALSO
[Exclamation mark on Wikipedia](https://en.wikipedia.org/wiki/Exclamation_mark)
### Mismatched full stop
* **Summary:**
Source and translation do not both end with a full stop.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndStopCheck`
* **Check identifier:**
`end_stop`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-stop`
Checks that full stops are replicated between both source and translation.
The presence of full stops is checked for various languages where they do not belong
(Chinese, Japanese, Devanagari or Urdu).
#### SEE ALSO
[Full stop on Wikipedia](https://en.wikipedia.org/wiki/Full_stop)
### Mismatched interrobang
* **Summary:**
Source and translation do not both end with an interrobang expression.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndInterrobangCheck`
* **Check identifier:**
`end_interrobang`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-interrobang`
Checks that interrobang marks are replicated between both source and translation.
It allows the swap between “!?” and “?!”.
#### SEE ALSO
[Interrobang mark on Wikipedia](https://en.wikipedia.org/wiki/Interrobang)
### Mismatched question mark
* **Summary:**
Source and translation do not both end with a question mark.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndQuestionCheck`
* **Check identifier:**
`end_question`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-question`
Checks that question marks are replicated between both source and translation.
The presence of question marks is also checked for various languages where they
do not belong (Armenian, Arabic, Chinese, Korean, Japanese, Ethiopic, Vai or
Coptic).
#### SEE ALSO
[Question mark on Wikipedia](https://en.wikipedia.org/wiki/Question_mark)
### Mismatched semicolon
* **Summary:**
Source and translation do not both end with a semicolon.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndSemicolonCheck`
* **Check identifier:**
`end_semicolon`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-semicolon`
Checks that semicolons at the end of sentences are replicated between both source and translation.
#### SEE ALSO
[Semicolon on Wikipedia](https://en.wikipedia.org/wiki/Semicolon)
### Mismatching line breaks
* **Summary:**
Number of new lines in translation does not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.NewLineCountCheck`
* **Check identifier:**
`newline-count`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-newline-count`
Usually newlines are important for formatting program output.
Check fails if the number of new lines in translation does not match the source.
### Missing plurals
* **Summary:**
Some plural forms are untranslated.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.consistency.PluralsCheck`
* **Check identifier:**
`plurals`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-plurals`
Checks that all plural forms of a source string have been translated.
Specifics on how each plural form is used can be found in the string definition.
Failing to fill in plural forms will in some cases lead to displaying nothing when
the plural form is in use.
### Multiple capitals
#### Versionadded
Added in version 5.16.
* **Summary:**
Translation contains words with multiple misplaced capital letters.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.MultipleCapitalCheck`
* **Check identifier:**
`multiple_capital`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-multiple-capital`
Checks for misplaced capitalization by detecting words that contain consecutive
uppercase letters in otherwise lowercase or normally capitalized text (for
example, `HEllo` or `CAmelCase`). Strings that contain capitalization in the
source string are allowed to contain capitalization in the translation.
### Non‑standard characters in Kabyle
#### Versionadded
Added in version 5.12.
* **Summary:**
Use standardized Latin Kabyle characters (e.g. `ɣ` instead of Greek `γ`; `ɛ` instead of `ε`).
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.KabyleCharactersCheck`
* **Check identifier:**
`kabyle-characters`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-kabyle-characters`
Checks that Kabyle translations use correct Kabyle letters and not similar
Greek ones, which were often used before Kabyle characters were standardized in
Unicode.
### Placeholders
#### Versionchanged
Changed in version 4.3: You can use regular expression as placeholder.
#### Versionchanged
Changed in version 4.13: With the `case-insensitive` flag, the placeholders are not case-sensitive.
* **Summary:**
Translation is missing some placeholders.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.placeholders.PlaceholderCheck`
* **Check identifier:**
`placeholders`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`placeholders`
* **Flag to ignore:**
`ignore-placeholders`
Translation is missing some placeholders. These are either extracted from the
translation file or defined manually using `placeholders` flag, more can be
separated with colon, strings with space can be quoted:
```text
placeholders:$URL$:$TARGET$:"some long text"
```
In case you have some syntax for placeholders, you can use a regular expression:
```text
placeholders:r"%[^% ]%"
```
You can also have case insensitive placeholders:
```text
placeholders:$URL$:$TARGET$,case-insensitive
```
#### SEE ALSO
[Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)
### Prohibited initial character
#### Versionadded
Added in version 5.9.
* **Summary:**
The string starts with a prohibited character in CSV.
* **Scope:**
glossary strings
* **Check class:**
`weblate.checks.glossary.ProhibitedInitialCharacterCheck`
* **Check identifier:**
`prohibited_initial_character`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-prohibited-initial-character`
The glossary is often shared as CSV and using some characters at the beginning is
restricted by many applications as these can cause the text being evaluated as
an expression. This also affects [Glossaries in automatic suggestion](https://docs.weblate.org/en/weblate-2026.10/user/glossary.md#glossary-mt) where many services use CSV
for synchronizing glossaries and reject such strings.
### Punctuation spacing
#### Versionchanged
Changed in version 5.10: This check used to apply to Breton language as well, but it was limited to French only.
* **Summary:**
Missing non breakable space before double punctuation sign.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.PunctuationSpacingCheck`
* **Check identifier:**
`punctuation_spacing`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-punctuation-spacing`
Checks that there is non breakable space before double punctuation sign
(exclamation mark, question mark, semicolon and colon). This rule is used only
in a few selected languages like French, where space before double
punctuation sign is a typographic rule.
#### SEE ALSO
[French and English spacing on Wikipedia](https://en.wikipedia.org/wiki/History_of_sentence_spacing#French_and_English_spacing)
### Regular expression
#### Versionchanged
Changed in version 5.10: Extended support for advanced regular expressions including Unicode codepoint properties.
* **Summary:**
Translation does not match regular expression.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.placeholders.RegexCheck`
* **Check identifier:**
`regex`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`regex`
* **Flag to ignore:**
`ignore-regex`
Translation does not match regular expression. The expression is either extracted from the
translation file or defined manually using `regex` flag:
```text
regex:^foo|bar$
```
The matching also supports Unicode codepoint properties, including scripts and blocks:
```text
regex:^[-_\p{L}\p{N}\p{sc=Deva}\p{sc=Thai}]{1,32}$
```
#### HINT
Use [Placeholders](#check-placeholders) for detecting missing placeholders in the string.
#### SEE ALSO
[regex documentation](https://github.com/mrabarnett/mrab-regex)
### reStructuredText syntax error
#### Versionadded
Added in version 5.10.
* **Summary:**
reStructuredText syntax error in the translation.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.RSTSyntaxCheck`
* **Check identifier:**
`rst-syntax`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`rst-text`
* **Flag to ignore:**
`ignore-rst-syntax`
reStructuredText syntax error in the translation. Issues to look for:
* Mismatched closing/opening tags.
* Missing spaces or interpunction around the reference. The reStructuredText inline blocks need to be separated by non-word characters.
* Using quotes instead of backticks.
#### SEE ALSO
* [reStructuredText Primer](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html)
* [Inconsistent reStructuredText](#check-rst-references)
### Reused translation
#### Versionadded
Added in version 4.18.
* **Summary:**
Different strings are translated the same.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.consistency.ReusedCheck`
* **Check identifier:**
`reused`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-reused`
Check that fails if the same translation is used on different source strings.
Such translations can be intentional, but can also confuse users.
### Safe MDX
#### Versionadded
Added in version 2026.7.
* **Summary:**
JSX expressions in the translation do not match the source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.mdx.SafeMDXCheck`
* **Check identifier:**
`safe-mdx`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[MDX files](https://docs.weblate.org/en/weblate-2026.10/formats/mdx.md#mdx)
* **Flag to enable:**
`safe-mdx`
* **Flag to ignore:**
`ignore-safe-mdx`
### Same plurals
* **Summary:**
Some plural forms are translated in the same way.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.consistency.SamePluralsCheck`
* **Check identifier:**
`same-plurals`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-same-plurals`
Check that fails if some plural forms are duplicated in the translation.
In most languages they have to be different.
### Starting newline
* **Summary:**
Source and translation do not both start with a newline.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.BeginNewlineCheck`
* **Check identifier:**
`begin_newline`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-begin-newline`
Newlines usually appear in source strings for good reason, omissions or additions
can lead to formatting problems when the translated text is put to use.
#### SEE ALSO
[Trailing newline](#check-end-newline)
### Starting spaces
* **Summary:**
Source and translation do not both start with same number of spaces.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.BeginSpaceCheck`
* **Check identifier:**
`begin_space`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-begin-space`
A space in the beginning of a string is usually used for indentation in the interface and thus
important to keep.
### Trailing newline
* **Summary:**
Source and translation do not both end with a newline.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndNewlineCheck`
* **Check identifier:**
`end_newline`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-newline`
Newlines usually appear in source strings for good reason, omissions or additions
can lead to formatting problems when the translated text is put to use.
#### SEE ALSO
[Starting newline](#check-begin-newline)
### Trailing space
* **Summary:**
Source and translation do not both end with a space.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.EndSpaceCheck`
* **Check identifier:**
`end_space`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-end-space`
Checks that trailing spaces are replicated between both source and translation.
Trailing space is usually utilized to space out neighbouring elements, so
removing it might break layout.
### Unchanged translation
* **Summary:**
Source and translation are identical.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.same.SameCheck`
* **Check identifier:**
`same`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-same`
Happens if the source and corresponding translation strings are identical, down
to at least one of the plural forms. Some strings commonly found across all
languages are ignored, and various markups are stripped. This reduces the
number of false positives.
This check can help find strings mistakenly untranslated.
The default behavior of this check is to exclude words from the built-in terms
list from the checking. These are words which are frequently not being
translated. This is useful to avoid false positives on short strings, which
consist only of a single word which is the same in several languages. This list
can be disabled by adding `strict-same` flag to a string or component.
#### Versionchanged
Changed in version 4.17: With `check-glossary` flag (see [Does not follow glossary](#check-check-glossary)), the
untranslatable glossary terms are excluded from the checking.
#### SEE ALSO
* [Does not follow glossary](#check-check-glossary)
* [Component configuration](https://docs.weblate.org/en/weblate-2026.10/admin/projects.md#component)
* [Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)
### Unsafe HTML
* **Summary:**
The translation uses unsafe HTML markup.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.SafeHTMLCheck`
* **Check identifier:**
`safe-html`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[HTML files](https://docs.weblate.org/en/weblate-2026.10/formats/html.md#html), [Markdown files](https://docs.weblate.org/en/weblate-2026.10/formats/markdown.md#markdown), [MDX files](https://docs.weblate.org/en/weblate-2026.10/formats/mdx.md#mdx), [AsciiDoc files](https://docs.weblate.org/en/weblate-2026.10/formats/asciidoc.md#asciidoc)
* **Flag to enable:**
`auto-safe-html`, `safe-html`
* **Automatic flag behavior:**
`auto-safe-html`: Treat a text as conditional HTML, enabling [Unsafe HTML](#check-safe-html) only for plain text or source strings that contain standard HTML markup or valid custom elements. This is useful for extended Markdown variants such as MDX, where angle-bracket syntax may not be HTML.
* **Flag to ignore:**
`ignore-safe-html`
The translation uses unsafe HTML markup. This check has to be enabled using
`safe-html` flag (see [Customizing behavior using flags](https://docs.weblate.org/en/weblate-2026.10/admin/checks.md#custom-checks)). There is also accompanied
autofixer which can automatically sanitize the markup.
#### HINT
When `md-text` flag is also used, the Markdown style links are also allowed.
#### SEE ALSO
The HTML check is performed by the [Ammonia](https://github.com/rust-ammonia/ammonia)
library.
### URL
* **Summary:**
The translation does not contain a URL.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.URLCheck`
* **Check identifier:**
`url`
* **Trigger:**
This check needs to be enabled using a flag.
* **Flag to enable:**
`url`
* **Flag to ignore:**
`ignore-url`
The translation does not contain a URL. This is triggered only in case the
unit is marked as containing URL. In that case the translation has to be a
valid URL.
### XML markup
* **Summary:**
XML tags in translation do not match source.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.XMLTagsCheck`
* **Check identifier:**
`xml-tags`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-xml-tags`
This usually means the resulting output will look different. In most cases this is
not a desired result from changing the translation, but occasionally it is.
Checks that XML tags are replicated between both source and translation.
The check is automatically enabled for XML like strings. You might need to add
`xml-text` flag in some cases to force turning it on.
#### NOTE
This check is disabled by the `safe-html` flag as the HTML cleanup done by
it can produce HTML markup which is not valid XML.
### XML syntax
* **Summary:**
The translation is not valid XML.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.markup.XMLValidityCheck`
* **Check identifier:**
`xml-invalid`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-xml-invalid`
The XML markup is not valid.
The check is automatically enabled for XML like strings. You might need to add
`xml-text` flag in some cases to force turning it on.
#### NOTE
This check is disabled by the `safe-html` flag as the HTML cleanup done by
it can produce HTML markup which is not valid XML.
### Zero-width space
* **Summary:**
Translation contains extra zero-width space character.
* **Scope:**
translated strings
* **Check class:**
`weblate.checks.chars.ZeroWidthSpaceCheck`
* **Check identifier:**
`zero-width-space`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-zero-width-space`
Zero-width space () characters are used to break messages within words (word wrapping).
As they are usually inserted by mistake, this check is triggered once they are present
in translation. Some programs might have problems when this character is used.
#### SEE ALSO
[Zero width space on Wikipedia](https://en.wikipedia.org/wiki/Zero-width_space)
## Source checks
Source checks can help developers improve the quality of source strings.
### Ellipsis
* **Summary:**
The string uses three dots `...` instead of an ellipsis character `…`.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.source.EllipsisCheck`
* **Check identifier:**
`ellipsis`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-ellipsis`
This fails when the string uses three dots (`...`) when it should use an ellipsis character (`…`).
Using the Unicode character is in most cases the better approach and looks better
rendered, and may sound better with text-to-speech.
#### SEE ALSO
[Ellipsis on Wikipedia](https://en.wikipedia.org/wiki/Ellipsis)
### Fluent source inner HTML
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent source should be valid inner HTML.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.fluent.inner_html.FluentSourceInnerHTMLCheck`
* **Check identifier:**
`fluent-source-inner-html`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-source-inner-html`
* **Flag to ignore:**
`ignore-fluent-source-inner-html`
Fluent is often used in contexts where the value for a Message (or Term) is
meant to be used directly as `.innerHTML` (rather than `.textContent`) for
some HTML element. For example, when using the Fluent DOM package.
The aim of this check is to predict how the value will be parsed as inner HTML,
assuming an HTML5 conforming parser, to catch cases where there would be some
“unintended” loss of the string, without being too strict about technical
parsing errors that do *not* lead to a loss of the string.
This check is applied to the value of Fluent Messages or Terms, but not their
Attributes. For Messages, the Fluent Attributes are often just HTML attribute
values, so can be arbitrary strings. For Terms, the Fluent Attributes are
often language properties that can only be referenced in the selectors of Fluent
Select Expressions.
Generally, most Fluent values are not expected to contain any HTML markup.
Therefore, this check does not expect or want translators and developers to have
to care about strictly avoiding *any* technical HTML5 parsing errors (let alone
XHTML parsing errors). Instead, this check will just want to warn them when they
may have unintentionally opened an HTML tag or inserted a character reference.
Moreover, for the Fluent values that intentionally contain HTML tags or
character references, this check will verify some “good practices”, such as
matching closing and ending tags, valid character references, and quoted
attribute values. In addition, whilst the HTML5 specification technically allows
for quite arbitrary tag and attribute names, this check will restrain them to
some basic ASCII values that should cover the standard HTML5 element tags and
attributes, as well as allow *some* custom element or attribute names. This is
partially to ensure that the user is using HTML intentionally.
Examples:
#### Fluent inner HTML examples
| Value | Warns? | Reason |
|-------------------|----------|-----------------------------------------------------------------------|
| `three` | yes | Missing a closing tag. |
| `three ` | yes | `four` is not an HTML void element, so should not self-close. |
| `text` | no | Custom element tag with a matching closing tag. |
| `a ![]()
b` | no | `img` is an HTML void element. Self-closing is allowed. |
| `a
b` | no | `br` is an HTML void element. |
| `![]()
` | yes | The attribute value is not quoted. |
| `` | yes | Non-ASCII tag name. |
| `kindðical` | yes | The `ð` part would be converted to `ð`. |
| `kindðical` | no | The character reference seems to be intentional. |
| `three<e;four` | yes | The `<e;` part would be converted to `
### Fluent source syntax
#### Versionadded
Added in version 5.0.
* **Summary:**
Fluent syntax error in the source.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.fluent.syntax.FluentSourceSyntaxCheck`
* **Check identifier:**
`fluent-source-syntax`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[Fluent format](https://docs.weblate.org/en/weblate-2026.10/formats/fluent.md#fluent)
* **Flag to enable:**
`fluent-source-syntax`
* **Flag to ignore:**
`ignore-fluent-source-syntax`
In Weblate, Fluent strings use Fluent syntax for references and variables, but
also for more complex features like defining attributes and selector variants,
including plurals. This check ensures that the syntax used in source will be
valid for Fluent.
#### SEE ALSO
* [Fluent translation syntax](#check-fluent-target-syntax)
* [Fluent Syntax Guide](https://projectfluent.org/fluent/guide/)
* [Mozilla Basic Syntax Guide](https://mozilla-l10n.github.io/localizer-documentation/tools/fluent/basic_syntax.html)
### ICU MessageFormat syntax
#### Versionadded
Added in version 4.9.
* **Summary:**
Syntax errors in ICU MessageFormat strings.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.icu.ICUSourceCheck`
* **Check identifier:**
`icu_message_format_syntax`
* **Trigger:**
This check needs to be enabled using a flag.
* **File formats automatically enabling this check:**
[ARB File](https://docs.weblate.org/en/weblate-2026.10/formats/arb.md#arb), [Format.JS JSON file](https://docs.weblate.org/en/weblate-2026.10/formats/formatjs.md#formatjs)
* **Flag to enable:**
`icu-message-format`
* **Flag to ignore:**
`ignore-icu-message-format`
#### SEE ALSO
[ICU MessageFormat](#check-icu-message-format)
### Long untranslated
#### Versionadded
Added in version 4.1.
* **Summary:**
The string has not been translated for a long time.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.source.LongUntranslatedCheck`
* **Check identifier:**
`long_untranslated`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-long-untranslated`
When the string has not been translated for a long time, it can indicate a problem in a
source string making it hard to translate.
### Multiple failing checks
* **Summary:**
The translations in several languages have failing checks.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.source.MultipleFailingCheck`
* **Check identifier:**
`multiple_failures`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-multiple-failures`
Numerous translations of this string have failing quality checks. This is
usually an indication that something could be done to improve the source
string.
This check failing can quite often be caused by a missing full stop at the end of
a sentence, or similar minor issues which translators tend to fix in
translation, while it would be better to fix it in the source string.
### Multiple unnamed variables
#### Versionadded
Added in version 4.1.
* **Summary:**
There are multiple unnamed variables in the string, making it impossible for translators to reorder them.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.format.MultipleUnnamedFormatsCheck`
* **Check identifier:**
`unnamed_format`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-unnamed-format`
There are multiple unnamed variables in the string, making it impossible for
translators to reorder them.
Consider using named variables instead to allow translators to reorder them.
### Source string length
* **Summary:**
Source string is close to or exceeds the configured maximum length for translations.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.source.SourceMaxLengthCheck`
* **Check identifier:**
`source-max-length`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-source-max-length`
Translations often need more room than the source text, especially when the
source language is English. This check helps maintainers find source strings
that are already close to their configured `max-length` before translators
have to shorten or omit meaning to fit the limit.
For English source strings, including English variants, the check reports
strings using more than 85% of the configured `max-length`. For other source
languages, it reports source strings longer than the configured
`max-length`.
This catches source strings that are likely to make translations fail
[Maximum length of translation](#check-max-length), and source strings that already do not fit the
declared limit.
### Unpluralised
* **Summary:**
The string is used as plural, but not using plural forms.
* **Scope:**
source strings
* **Check class:**
`weblate.checks.source.OptionalPluralCheck`
* **Check identifier:**
`optional_plural`
* **Trigger:**
This check is always enabled but can be ignored using a flag.
* **Flag to ignore:**
`ignore-optional-plural`
The string is used as a plural, but does not use plural forms. In case your
translation system supports this, you should use the plural aware variant of
it.
For example with Gettext in Python it could be:
```python
from gettext import ngettext
print(ngettext("Selected %d file", "Selected %d files", files) % files)
```
## Placeables in automatic suggestion
Checks for placeables expose information on current placeables and this can be
used to instruct automatic suggestion engines to keep them. The support for
this varies in different services and in many cases there is no way to enforce
keeping placeables intact.
#### SEE ALSO
[Automatic suggestions](https://docs.weblate.org/en/weblate-2026.10/admin/machine.md)