Bug 401823 - Localization problem in kcm_mouse
Summary: Localization problem in kcm_mouse
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 5.14.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-06 13:43 UTC by Paolo Zamponi
Modified: 2018-12-07 19:39 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of the module (137.71 KB, image/png)
2018-12-06 13:43 UTC, Paolo Zamponi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paolo Zamponi 2018-12-06 13:43:22 UTC
Created attachment 116714 [details]
screenshot of the module

Hi all, I notice a localization problem in the "Mouse" module of the Systemsettings, as you can see in my screenshot. This occours if X11 driver is "libinput", with "evdev" (on my laptop) the module itself is quite different and fully localized.

STEPS TO REPRODUCE
1. Open Systemsettings -> Hardware -> Input devices -> Mouse
2. If your X11 driver is "libinput" the situation should be the same as in my screenshot.

EXPECTED RESULT
All the messages should be displayed in my locale.

SOFTWARE/OS VERSIONS
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
Switching to another locale doesn't solve this problem. "kcmmouse.po" is fully translated into Italian, and if I look inside this file all those unlocalized messages belong to "kcm/libinput/main_deviceless.qml" source file.
Comment 1 Burkhard Lück 2018-12-07 09:35:23 UTC
was fixed with https://cgit.kde.org/plasma-desktop.git/commit/kcms/mouse?id=65dfdf25bef7635a84851603a507c17de7de35cb on 2018-11-10
and therefore fully translated in master build from sources using locale x-test
thanks for reporting
Comment 2 Luigi Toscano 2018-12-07 13:54:21 UTC
Bukrhard, would it make sense to backport the fix to 5.14.x, asking for a translation exception? There is another 5.14.x release planned.

That said, while the fix is working, it looks like a workaround. Maybe the translation file need to be renamed?
Comment 3 Burkhard Lück 2018-12-07 19:39:52 UTC
* backporting a fix for untranslated strings does not break string freeze, we would not even need to ask for an exception

* how would renaming the translation file help?