Bug 483720 - Kirigami search field are not translated in system settings
Summary: Kirigami search field are not translated in system settings
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-16 05:41 UTC by Guo Yunhe
Modified: 2024-04-13 01:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
compare search field of system settings and discover (130.47 KB, image/png)
2024-03-16 05:41 UTC, Guo Yunhe 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Guo Yunhe 2024-03-16 05:41:29 UTC 
Created attachment 167291 [details]
compare search field of system settings and discover

SUMMARY

Krigami SearchField component is used in many places of system settings. All of them are not translated. However, the same component in other KDE apps, like Discover, are properly translated.

STEPS TO REPRODUCE
1. Switch system to other language than English
2. Open system settings, check the search field placeholder text
3. Open Discover app center, check the search field placeholder text

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-04-10 19:19:34 UTC 
Cannot reproduce by running `LANGUAGE=zh_CN systemsettings`; the search field looks to me like it's got Chinese characters in it. It's also properly translated with fr_FR and de_DE.

Localization folks, any idea what might be going on here?
Comment 2 Guo Yunhe 2024-04-13 01:38:08 UTC 
Tried the latest nightly build of Kirigami from openSUSE Build Service, and it works fine. Seems only affect 6.0.0 and will be fixed in next version.