Created attachment 53719 [details] I'm attaching a screenshot, in case that no one is able to reproduce it. Version: 4.5 (using KDE 4.5.3) OS: Linux By default keyboard layout in kde is using flags. But as we know there is an option for labels to be shown. By default labels are lower-case(us, de, es, it, bg...). But if you try to change the label and set some upper-case string, it doesn't get rendered at all in the panel. There is just a whitespace, instead. Reproducible: Always Steps to Reproduce: 0. Open System Settings 1. Go to Input devices and then Keyboard 2. Click on the Layouts tab 3. Check the "Show label" option in Layout Indicator's QGroupBox 4. Enable the "Configure Layouts", if they are disabled 5. Change the one of the layout's label to some upper-case string(like US, for example) 6. Click Apply 7. Take a look at the tray area :) Actual Results: Upper-case labels of keyboard layouts gets rendered as single whitespace in the tray area. Expected Results: Upper-case labels to be shown fine as well, just like the lower-case's. At first I thought the panel's height is responsible for this issue. But as you can see, from the attached screenshot, the same thing happens even if the panel is terrificly high.
Confirmed on 4.5 branch. Not confirmed in trunk though. The bug is that the layout label does not show if it's upper case in 4.5 branch.
Andriy can you look at it please? Would be a nice fix for 4.5 branch
It's quite hard to fix in keyboard icon, it already does too much of graphics work to just some a simple text in the tray. It's just without knowing the size of the graphics area (and KStatusNotifierItem does not provide any information about the tray icon properties) it's really hard to scale the text right. I filed a bug against KStatusNotifierItem https://bugs.kde.org/show_bug.cgi?id=251870 but does not look like it's getting much attention. As a workaround one can add keyboard applet to the taskbar - the applet should scale the letters right and it also handles dark backgrounds much nicer. *** This bug has been marked as a duplicate of bug 251870 ***