Opened 11 years ago

Closed 11 years ago

#42311 closed enhancement (wontfix)

kde-l10n-* kmymoney.po from the extragear-office package not included

Reported by: malmuc@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: NicosPavlov
Port: kde-l10n-

Description

In order to localize the kmymoney4 port I had to download kmymoney.po from l10n.kde.org and manually create the .mo file within the LC_MESSAGES folder. It would be great to have the translation for kmymoney (or probably all extragear packages?) included in the kde-l10n-* ports.

Change History (2)

comment:1 Changed 11 years ago by NicosPavlov

The content of the kde-l10n-* ports is not decided by Macports, as all the language packages are directly distributed by KDE. The fact that the extragear translations are not included in the standard packages is therefore the choice of the KDE team.

We could think about adding a Portfile for extragear translations, but these files are not, to my knowledge, distributed through standard packages, and would have to be downloaded from the repository. The issue is that the svn repositories are currently being taken down (http://community.kde.org/Sysadmin/SVNInfrastructureShutdown), so that I am not sure about which location should be used, as this is exactly the transition period.

comment:2 Changed 11 years ago by NicosPavlov

Resolution: wontfix
Status: newclosed

After a more detailed look, it appears that the svn repository containing extragear translations is a pure data repository, without any installation script. This implies that including these translations would require to create all the installation structure internally in Macports.

Furthermore, another issue is that there are messages for both very different softwares and languages, so that the Portfile would have to be huge (installing everything), or be a multitude of small ports by either software or language, which would be very difficult to maintain.

Compared to these issues, manually installing the required file does not seem to much of a hassle, or, if a more automated way should made, it should be prepared upstream beforehand before it could be used by package managers.

Note: See TracTickets for help on using tickets.