Per-language statistics miscalculated on nested categories

[nijel]

Discussed in #11153

^{Originally posted by vanlinh2204 March 8, 2024}
The problem arises when observing the statistics in the category ipension-front-office. Here's a breakdown of the issue:

Uniform Unfinished String Count: Within the ipension-front-office category, I've noticed that the unfinished string count remains consistent across 4 languages: fr, de, it, en. However, upon closer inspection, this count does not accurately reflect the number of strings requiring translation in each language. For instance, no strings appear for translation when selecting the French (fr) language, despite the reported count.

Correct Display in Sub-categories: Conversely, when navigating to the sub-category ipension-front-office/portal-service, the language tab correctly displays the number of unfinished strings, such as 40 in English (en). Further exploration into the components within ipension-front-office/portal-service, such as core-portal-service (10 unfinished in English) and first-portal-services (30 unfinished in English), indicates the accurate count of unfinished strings.

This inconsistency in statistic calculation poses challenges for translators and project managers relying on Weblate's data accuracy for localization efforts.

I kindly request your assistance in addressing this matter and welcome any suggestions or insights you may have regarding this issue. Additionally, if anyone has encountered similar challenges or has insights into potential solutions, please share them here.

Thank you for your attention to this matter, and I look forward to your responses.

[nijel]

#11241 should address this.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.