https://bugs.kde.org/show_bug.cgi?id=390899
--- Comment #8 from Yoann Laissus <yoann.lais...@gmail.com> --- (In reply to Guo Yunhe from comment #7) > Comparing the KCM of plasma-nm and plasma-pa: > > https://github.com/KDE/plasma-nm/blob/master/kcm/kcm.cpp > > https://github.com/KDE/plasma-pa/blob/master/src/kcm/module.cpp > > plasma-nm set its text domain: > > kdeclarative.setTranslationDomain(QStringLiteral(TRANSLATION_DOMAIN)); > > But plasma-pa didn't. Indeed, it's a translation domain problem. But the problem is more complex than that. The problem appears in the KCM view in the settings but not in systemsettings. I tracked it down some months ago but I forgot to finish that. Based on what I found, it's a problem during the QML context initialisation in KDecalarative : https://cgit.kde.org/kdeclarative.git/tree/src/quickaddons/configmodule.cpp#n142 You can find it's done here for the context : https://cgit.kde.org/plasma-framework.git/tree/src/plasmaquick/configview.cpp#n96 But for some reasons the translation domain gets lost with this line : https://cgit.kde.org/plasma-framework.git/tree/src/plasmaquick/configmodel.cpp#n274 I'll try to find some time to do a proper fix because for now it's more like a hack. I also need to make sure it doesn't break anything else because those parts are used in many areas. -- You are receiving this mail because: You are watching all bug changes.
