Bug 409634 - Color theme name translations
Summary: Color theme name translations
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 5.16.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Matthew Woehlke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-08 22:06 UTC by Sascha Gaspar
Modified: 2020-01-15 18:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot (77.28 KB, image/png)
2019-07-08 22:08 UTC, Sascha Gaspar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Gaspar 2019-07-08 22:06:07 UTC
SUMMARY
In the German translation of the GUI I get an error message in the color theme settings dialog: "Das Farbschema "Breeze-Dunkel" ist nicht installiert. Es wird stattdessen das Standardschema installiert." This means "The color sceme "Breeze-Dark" is not installed." I think, this may be a problem with the translation. I think breeze-dark is installed.

See also the attached screenshot. I think you know what I mean.

STEPS TO REPRODUCE
Not sure:
1. Use german UI.
2. Select theme "Breeze-Dark"
3. Go to color settings

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSuSE Tumbleweed
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION
Comment 1 Sascha Gaspar 2019-07-08 22:08:19 UTC
Created attachment 121404 [details]
Screenshot
Comment 2 Kai Uwe Broulik 2019-07-09 06:56:29 UTC
Did you update from an older version before? If you re-apply it should rectify itself. Previously, we stored the translated name of the color scheme in config, which wasn't a big issue as they weren't translated. However, now they are and it results in mapping failures, which is why I changed it to store the untranslated name.
Comment 3 Sascha Gaspar 2019-07-14 13:10:54 UTC
Yes, I update the system since many month. But I don't want to delete all my settings. May be I have to live with this for a while.
Comment 4 Nate Graham 2019-07-15 20:58:05 UTC
FWIW I got the same message on upgrading to 5.16 (I guess that one time I used French for a while, the translated color scheme name got into the config file).

Sounds the root cause is already fixed, but maybe we could map the old translated strings to the new untranslated ones upon upgrade so people don't see this useless error message?
Comment 5 Nate Graham 2020-01-15 18:24:10 UTC
Root cause is fixed now, I think that's the best we can do for now. :/