Bug 1755439 - calligraplan doesn't load translations from calligraplanlibs.mo
Summary: calligraplan doesn't load translations from calligraplanlibs.mo
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: calligraplan
Version: 30
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-25 14:06 UTC by wojnilowicz
Modified: 2020-05-26 17:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:14:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Main window of Calligra Plan (8.49 KB, image/png)
2019-09-25 14:06 UTC, wojnilowicz
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 412325 0 NOR RESOLVED calligraplan doesn't load translations from calligraplanlibs.mo 2020-12-23 16:32:07 UTC

Description wojnilowicz 2019-09-25 14:06:29 UTC
Created attachment 1619043 [details]
Main window of Calligra Plan

Description of problem:
Calligra Plan shows half of the strings untranslated in Polish language although they have translation on https://l10n.kde.org/


Version-Release number of selected component (if applicable):
3.1.0

How reproducible:
Always.

Steps to Reproduce:
1. log in non-English but quite fully translated KDE desktop environment
2. start calligraplan
3. main window appears

Actual results:
Main window's menu is in native language and buttons are in English language (see attachment). Translated strings for buttons are in calligraplanlibs.mo although they aren't displayed.

Expected results:
Main window's menu  and buttons should be in native language.


Additional info:
1) translations from calligraplan.mo are showed correctly in the application
2) I've tried to update:

calligraplan.mo
calligraplanlibs.mo

in

/usr/share/locale/pl/LC_MESSAGES/

from

https://l10n.kde.org/

but no change.

Comment 1 Rex Dieter 2019-09-25 14:48:05 UTC
Probably best to report this upstream to bugs.kde.org .  No idea why this isn't working (perhaps upstream will know)

Comment 2 wojnilowicz 2019-09-25 14:51:31 UTC
Reported here
https://bugs.kde.org/show_bug.cgi?id=412325

Comment 3 Rex Dieter 2019-09-25 15:10:49 UTC
thanks

Comment 4 Ben Cotton 2020-04-30 21:04:23 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-05-26 17:14:45 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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