Translation component diagnostics¶

Shows errors in the Weblate configuration or the translation project for any given translation component. Guidance on how to address found issues is also offered.

Currently the following is covered:

Duplicated source strings in translation files
Duplicated languages within translations
Merge, update, or push failures in the repository
Parse errors in the translation files
Billing limits (see Billing)
Repository containing too many outgoing or missing commits
Missing licenses
Errors when running add-on (see Add-ons)
Misconfigured monolingual translation.
Broken Component configuration
Broken URLs
Unused screenshots
Ambiguous language code
Unused new base in component settings
Duplicate file mask used for linked components
Conflicting merge request repository setup
Component seems unused (configurable by UNUSED_ALERT_DAYS)

The alerts are updated daily, or on related change (for example when Component configuration is changed or when repository is updated).

Project website availability checks can be disabled using WEBSITE_ALERTS_ENABLED, in which case Weblate will no longer generate alerts for unreachable project websites.

Alerts are listed on each respective component page as Diagnostics. If it is missing, the component clears all current checks. Problem alerts cannot be ignored, but will disappear once the underlying problem has been fixed.

Information and warning alerts are used for guidance on improving community localization. These can be dismissed and make the Diagnostics tab visible, but they do not indicate a component problem in listings.

A component with both duplicated strings and languages looks like this:

Conflicting repository setup¶

This alert is shown when multiple Git components are configured to push to the same repository and push branch without all of them pulling from that branch. This includes pull or merge request workflows, and direct pushes to a separate push branch. Such a setup can overwrite the shared branch.

To resolve this, either configure a different Push branch for each component or share the repository between components using a weblate://project/component repository URL.