Bug 369526

Summary:	Obsolete translation of kde applications
Product:	[KDE Neon] neon	Reporter:	Dimitris Kardarakos <dimkard>
Component:	Packages User Edition	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	jr, justin.zobel, neon-bugs-null, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dimitris Kardarakos 2016-09-29 11:25:37 UTC

Having an updated neon user-edition installation, I have observed missing greek translations.
Let's take kde-spectacle as en example, but I think that the same applies to the rest of kde applications.
Current kde-spectacle's version is 16.08.1-0neon+16.04+build20.
Looking into kde applications 16.08.1  sources at:
http://download.kde.org/stable/applications/16.08.1/src/kde-l10n/
I can find kde-l10n-el-16.08.1.tar.xz archive which contains spectacle.po, which in turn contains the latest translations. After generating the .mo file using msgfmt, specatcle is properly translated.
I suspect that the cause of the issue is kde-l10n-el, which is in version 4:15.12.3-0ubuntu1.1, instead of something like *16.08.1.*, which may contain the latest translations.
 

Reproducible: Always

Steps to Reproduce:
1. Open a kde application (version 16.08.1)
2. Look into translations

Actual Results:  
Translation is obsolete

Expected Results:  
Latest translation to be displayed

Comment 1 Jonathan Riddell 2016-09-29 11:30:28 UTC

adding kde-l10n-xx packages is on the todo

Comment 2 Justin Zobel 2021-03-18 05:43:07 UTC

Ping. Jonathan was this ever completed?

Comment 3 Carlos De Maine 2025-09-20 09:36:06 UTC

Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!