Bug 323040

Summary: libplasma translations cannot be loaded into Amarok widgets
Product: [Unmaintained] plasma4 Reporter: Yuri Chornoivan <yurchor>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: amarok-bugs-dist, lueck
Priority: NOR    
Version: 4.10.5   
Target Milestone: ---   
Platform: Mageia RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Context menu with untranslated items

Description Yuri Chornoivan 2013-07-31 11:50:53 UTC
Amarok context panel uses translations from libplasma catalog (line 172):

http://quickgit.kde.org/?p=amarok.git&a=blob&f=src%2FMainWindow.cpp

libplasma is completely translated into Ukrainian. Amarok itself loads these translations:

# # lsof | grep libplasma.mo
amarok    31014 31038    yurchor  mem       REG                8,5        16871    1068018 /usr/share/locale/uk/LC_MESSAGES/libplasma.mo

but for some reasons they are not used (see screenshot attached).

Amarok developer recommended to file a bug against Plasma.

Reproducible: Always

Steps to Reproduce:
1. Start Amarok in a locale with the appropriate coverage of libplasma.po translation.
2. Right-click on the context panel.
3. Items "Remove this ..." and "... Settings" are not translated.
Actual Results:  
Loaded catalog, but no translations used

Expected Results:  
Completely translated context menu

Thanks for triaging this bug.
Comment 1 Yuri Chornoivan 2013-07-31 11:52:02 UTC
Created attachment 81477 [details]
Context menu with untranslated items
Comment 2 Mark Kretschmann 2013-08-01 06:00:59 UTC
Still valid for KDE 4.10.95.
Comment 3 Nate Graham 2018-06-08 18:51:11 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham