Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 614716 - xfce-extra/xfce4-quicklauncher-plugin-1.9.4: displays wrong language in preferences
Summary: xfce-extra/xfce4-quicklauncher-plugin-1.9.4: displays wrong language in prefe...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-05 03:27 UTC by adebeus
Modified: 2019-05-11 11:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
screenshot of incorrect behavior (Screenshot_2017-04-04_20-16-41.png,30.80 KB, image/png)
2017-04-05 03:27 UTC, adebeus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description adebeus 2017-04-05 03:27:53 UTC
Created attachment 469212 [details]
screenshot of incorrect behavior

On the preferences screen for the quicklauncher plugin, I see text displayed in what appears to be French, even though my locale is set to en_US. A Google search seems to show upstream fixed this back in 2008 (https://bugs.launchpad.net/ubuntu/+source/xfce4-quicklauncher-plugin/+bug/179917) - but the bug report in the link concerns version 1.9.4, the same one that is currently used in the portage tree. Maybe the ebuild is not using the upstream fix for this issue?

A screenshot of the incorrect behavior is attached.
Comment 1 adebeus 2017-04-05 03:46:50 UTC
Upon reading the link in my original report more closely, it appears the initial upstream fix may have only worked for en_GB and a further fix was applied to make the fix work for all English locales. It's unclear if that additional fix was applied upstream or not, but a quick look at the .tar.bz2 file in /usr/portage/distfiles shows there's no en.po localization file, nor is there a patch in /usr/portage/xfce-extra/xfce4-quicklauncher-plugin/files to address the issue. So it looks like neither the initial upstream fix that only worked for en_GB nor the subsequent fix to make it work for all English locales is being applied by the ebuild. Either way, we should be able to use the same fix as Ubuntu to resolve this issue.