Bug 20840 - Plasma programs interfaces (Dolphin, Spectacle... ) use mixed language
Summary: Plasma programs interfaces (Dolphin, Spectacle... ) use mixed language
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2017-05-13 16:58 CEST by Morgan Leijström
Modified: 2017-06-01 09:54 CEST (History)
1 user (show)

See Also:
Source RPM: kde-l10n
CVE:
Status comment:


Attachments
Screenshot of Dolphin showing menu with swedish and english word mix (27.34 KB, image/png)
2017-05-13 17:00 CEST, Morgan Leijström
Details
install.log (tar.gz) (22.87 KB, application/octet-stream)
2017-05-13 17:04 CEST, Morgan Leijström
Details

Description Morgan Leijström 2017-05-13 16:58:08 CEST
Description of problem:

My desktop system with 64 bit old install mga6 shows fully translated menus OK.

But on my laptop where i installed mga6 32 bit fresh using *network install* via urpmi-proxy three weeks ago, some programs use a mix of swedish and english words in the same menu.
How can that be?

(problem persists as of updates today)

I attach screenshot and install log.
Comment 1 Morgan Leijström 2017-05-13 17:00:01 CEST
Created attachment 9295 [details]
Screenshot of Dolphin showing menu with swedish and english word mix
Comment 2 Morgan Leijström 2017-05-13 17:04:05 CEST
Created attachment 9296 [details]
install.log   (tar.gz)
Comment 3 Marja Van Waes 2017-05-13 19:59:18 CEST
Here, (64bit) starting Dolphin in a language for which the matching locales package was installed when I installed Mageia, works fine.

For all other languages, I get a mixed screen, even if I install the matching locales-* now, reinstall the dolphin packages and reboot.

However, according to your install.log, locales-sv was installed when you installed Mageia, so you shouldn't get a mixed screen :-/

I assume it is still mixed when you start Dolphin with

    LANGUAGE=sv dolphin

?

Assigning to the KDE maintainers.

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 4 Morgan Leijström 2017-05-13 23:29:43 CEST
$ LANGUAGE=sv dolphin
Trying to convert empty KLocalizedString to QString.
Cannot creat accessible child interface for object:  PlacesView(0x88203b0)  index:  14
Attempted to re-run an already running session.
kf5.kio.core: KLocalSocket(0x87a6930) Jumbo packet of 84540 bytes
kf5.kio.core: KLocalSocket(0x87a6930) Jumbo packet of 84540 bytes
kf5.kio.core: KLocalSocket(0x87a6930) Jumbo packet of 84540 bytes

And the visual apperance is the same as before.
Comment 5 Morgan Leijström 2017-05-14 20:31:26 CEST
On the old rolling 64bit cauldron workstation where dolphin shows full swedish translation, i get

$ dolphin
Trying to convert empty KLocalizedString to QString.
Cannot creat accessible child interface for object:  PlacesView(0x221feb0)  index:  31
kf5.kio.core: KLocalSocket(0x1d96d80) Jumbo packet of 87678 bytes
kf5.kio.core: KLocalSocket(0x1d96d80) Jumbo packet of 88130 bytes

Interestingly it is not the KLocalizedString that differ, but the difference is that only the not OK install show the line:

  Attempted to re-run an already running session.

What session do what try to re-run?
It say so even if it is the first launch of Dolphin since boot.
Comment 6 Rémi Verschelde 2017-05-31 11:18:53 CEST
Most likely those strings are not translated upstream in Plasma (or for some of them, in Qt 5). Not much we can do on our end, the best would be to get in touch with the Swedish Plasma translators.

Keywords: (none) => UPSTREAM

Comment 7 Morgan Leijström 2017-05-31 12:17:15 CEST
Still valid in latest Plasma.
How do i best contact Swedish translators of Plasma?
Comment 8 Rémi Verschelde 2017-05-31 12:40:21 CEST
They don't seem to have a mailing list for Swedish, so you'd have to use the general ML mentioned at the end of that page: https://l10n.kde.org/team-infos.php?teamcode=sv

I checked the current dolphin translations for kf5-stable and it's 100% complete: https://websvn.kde.org/*checkout*/branches/stable/l10n-kf5/sv/messages/applications/dolphin.po
(Actually everything is 100% translated according to the first link).

@ Nicolas, maybe we're out of the sync with upstream translations? Could we update kde-l10n to grab the latest changes from the stable branch?

Source RPM: (none) => kde-l10n

Comment 9 Morgan Leijström 2017-05-31 18:24:44 CEST
I would think there is something else wrong, because my three cauldrons that have been running cauldron for a year, and are updated frequently, do not show this problem.

Only the fresh installed from RC + updates.
One difference is that this machine is the only 32 bitter.
Another is that all other systems was installed with default plasma choice, or was upgraded from mga5 KDE4.

They all sync/install from my urpmi-proxy, except the 32 bit was installed from 6RC iso on stick with only xfce (If I Remember Correctly), and then installed plasma and updated from proxy.

Another test: When i make a new user on the systems it is the same: Dolphin display correct on the three systems where it is OK for other users, but in the 32 bitter it displays mixed language.

I also test in MATE. Tested different DM: SDDB, LXDM, LightDM, XDM. No change.

Maybe I should try a reinstall, network install.
Comment 10 Morgan Leijström 2017-06-01 09:54:44 CEST
I suddenly realised i was wrong on the install date of that problematic machine: it was in middle of april, with method: network install via my urpmi-proxy.

And then i took it with me on vacation and updated and installed programs using repos from mirrorlist.  Then one day i realised translation was partially broken Could have been like that from beginning or not.

Now i made a full fresh reinstall - like before using network install via my urpmi-proxy.

Translations are OK. :)

An nobody else have reported *this* kind of translation error i put it up to some hickup of undefined kind, but anyway rare and historic.

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


Note You need to log in before you can comment on or make changes to this bug.