Bug 31838

Summary:	MGA9 : LXQt - menu not translated
Product:	Mageia	Reporter:	psyca <linux>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	geiger.david68210
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	lxqt-l10n	CVE:
Status comment:
Attachments:	LXQt Menu - Mageia 8 LXQt Menu - Mageia 9 Showing the same unxlated menu items for a different language

Description psyca 2023-04-24 17:58:32 CEST

Description of problem:
The menu of the Mageia 9 LXQt DE is not translated in the selected language.
For example in Mageia 8 you have (install in german language) "Einstellungen", "Systemwerkzeuge" and "Sonstiges" but it shows as "Perferences" "System tools" and "Other" in Mageia 9. Same with the FR install.

Is there a problem with the config/install script or is this an upstream bug?

Comment 1 Lewis Smith 2023-04-24 19:31:39 CEST

Can you attach a screenshot to show what menu we are talking about. (It can be difficult to screenshot pop-up menus).
[I have my own unattended bug 31353 about missing icons if using Adwaita theme]

CC: (none) => lewyssmith

Comment 2 psyca 2023-04-24 19:44:47 CEST

Created attachment 13788 [details]
LXQt Menu - Mageia 8

Comment 3 psyca 2023-04-24 19:45:03 CEST

Created attachment 13789 [details]
LXQt Menu - Mageia 9

Comment 4 sturmvogel 2023-04-24 20:30:33 CEST

Confirmed in a LXQt VB installed from Mageia-Cauldron-netinstall-nonfree-x86_64.iso

Comment 5 Lewis Smith 2023-04-26 20:23:39 CEST

Created attachment 13792 [details]
Showing the same unxlated menu items for a different language

This confirm's the reporter's complaint with a different language; also shows other untranslated menu items - but perhaps translations do not exist for them?

Comment 6 Lewis Smith 2023-04-26 20:25:15 CEST

That was done on a Cauldron install.
Where do we send this? LxQt or Language people?

Comment 7 psyca 2023-05-04 09:35:54 CEST

Maybe CC the Mageia LXQt Maintainer to this ticket. Cant look who it is.

Comment 8 Lewis Smith 2023-05-04 20:42:22 CEST

There are many LxQt packages, listed for various packagers - the main one of whom I suspect is no longer active.
I wonder whether 'lxqt-l10n' is the package in question. Having to assign this globally for not knowing any better.

Source RPM: (none) => lxqt-l10n
Assignee: bugsquad => pkg-bugs

Lewis Smith 2023-05-04 20:42:33 CEST

CC: lewyssmith => (none)

Comment 9 psyca 2023-05-22 18:40:34 CEST

I figured out that under /usr/share/desktop-directories/ the file lxde-other.directory is missing the lines for the translations. If i enter the line

Name[de]=Sonstige

it shows the text i typed in for the german (de) translation. Same for
lxde-system.directory, lxde-settings.directory. Both are empty.
Maybe other files/menus are also have this problem so it would be good if somebody can check all the files if a translation is present or not.

The files are filled in MGA8 (but maybe outdated for MGA9) so the current translations for LXQt 1.3 need to be imported to the current MGA9 release.

Comment 10 psyca 2023-06-04 10:18:29 CEST

Just guessing as iam not a packager: Could this be the problem as there is no lxqt-menu-data in the MGA 9 repository? In the article its written it is needed on build time.
See : https://lxqt-project.org/blog/2023/05/19/migration-to-lxqt-menu-data/

Comment 11 David GEIGER 2023-06-04 23:02:03 CEST

Please test the new and upcoming lxqt-menu-data-1.3.0-0.git20230527.1.mga9 package in Cauldron repo!

CC: (none) => geiger.david68210

Comment 12 David GEIGER 2023-06-05 08:06:08 CEST

So lxqt-menu-data is not yet ready for current lxqt 1.3.0 but I found the issue with lxmenu-data which lack some translations during build.

A rebuild should fix this issue, please test upcoming lxmenu-data-0.1.5-5.mga9.

Comment 13 psyca 2023-06-05 17:43:59 CEST

Very nice. lxmenu-data-0.1.5-5.mga9 fixed it :D
Many many thanks David.

So lxqt-menu-data will be for future LXQt releases (a 1.3.1 or 1.4.0)?

Comment 14 David GEIGER 2023-06-05 18:07:38 CEST

Probably yes.

So closing of this bug as fixed!

Status: NEW => RESOLVED
Resolution: (none) => FIXED