SUMMARY In version 24.05.0, kasts shows an inconsistent set of translations. While the toggles are aligned with the system presets on the language, the marks in the left column are all in English. Same applies for the settings, which are also completely in English. Since this wasn't the case in the previous stable release, it seems like a regression. STEPS TO REPRODUCE 1. Install kasts and kasts-lang in version 24.05.0 2. Set desktop language to other value than English 3. Open kasts and get the inconsistent result OBSERVED RESULT Inconsistent translation EXPECTED RESULT Consistent translation according to the language settings of the overall desktop SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed 20240531 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION
I've refactored the strings in the settings menu with additional hints and metadata for translators early in the 24.05 development cycle. This might be the reason for these strings not being translated properly anymore. - In principle, there is fuzzy matching which should match most of the old translations to the updated i18n-strings if they are similar enough. I would have expected this to be the case since I only changed the metadata and not the actual English text. - Additionally, these changes should have triggered translators to review and potentially update the translations for those strings. I've seen translation updates for several languages hitting the repo shortly after I did the refactoring. However, this doesn't mean that some strings or languages did not slip through the safeguards mentioned above. For which languages is this happening? Maybe I can have a closer look at those.
Hi, Thanks for the thorough explanation. I experiened the issue with German language settings. Kind regards Thomas Am 7. Juni 2024 15:06:28 MESZ schrieb bugzilla_noreply@kde.org: >https://bugs.kde.org/show_bug.cgi?id=487981 > >--- Comment #1 from bart@mogwai.be --- >I've refactored the strings in the settings menu with additional hints and >metadata for translators early in the 24.05 development cycle. >This might be the reason for these strings not being translated properly >anymore. > >- In principle, there is fuzzy matching which should match most of the old >translations to the updated i18n-strings if they are similar enough. >I would have expected this to be the case since I only changed the metadata and >not the actual English text. >- Additionally, these changes should have triggered translators to review and >potentially update the translations for those strings. I've seen translation >updates for several languages hitting the repo shortly after I did the >refactoring. > >However, this doesn't mean that some strings or languages did not slip through >the safeguards mentioned above. >For which languages is this happening? Maybe I can have a closer look at >those. > -- On the road again - Sent from my mobile phone