Bring the translations forward from 5.x [ignore_release] - #647
Merged
Conversation
Weblate still pushes this component to 5.x-dev, so 138 strings (134 Czech, 4 French) had accrued there only. Both files changed on 5.x since the branches split and neither changed on 6.x, so nothing newer is overwritten.
AltamashShaikh
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Brings the translations forward from
5.x-dev, which had accrued strings the 6.x line never received.Weblate still pushes this component to
5.x-dev, and — this is the part that is easy to get wrong — Weblate does not backfill a branch when a component switches. It writes only the languages a translator happens to touch. LoginLdap demonstrates it: Portuguese (Brazil) strings landed on 5.x on 9 August, the component then switched and Weblate pushed French, Greek and Czech to 6.x over the following week, yetpt-br.jsonon 6.x is still the July version. So the strings do not arrive on their own.Safety of this change: every language file touched here changed on
5.x-devsince the branches diverged, and none changed on6.x-dev, so 5.x is uniformly the newer side and nothing newer is being overwritten. I also checked that no translated key is lost: every key present only on 6.x has no counterpart in 6.x'sen.json, so it is an orphan rather than a live translation. Each file was validated as JSON afterwards, and no file contains a key without anen.jsoncounterpart.This is a relocation of Weblate's own output onto the branch Weblate will adopt, not hand-authored translation, so it is not the kind of non-English edit the i18n rules warn against.
This will recur until the Weblate component itself is pointed at
6.x-dev(component settings -> Version control -> Repository branch, on Hosted Weblate). Worth doing alongside this.Issue No
Part of the Matomo 6 plugin readiness work. No separate ticket.
Steps to Replicate the Issue
lang/between5.x-devand6.x-devon this plugin.Checklist