Wrong translation catalogue filename (KPackageKit)

[Rivo Laks]

KPackageKit translations (.mo files) use wrong filename. Currently they're named "KPackageKit.mo" while the correct variant would be "kpackagekit.mo" (all lowercase).
Because of this, KPackageKit currently shows up untranslated. When I manually copy /usr/share/locale-langpack/et/LC_MESSAGES/KPackageKit.mo to kpackagekit.mo, then it becomes translated.

Also note that this is a regression from Jaunty (in jaunty the files are names kpackagekit.mo). A testcase can be found here: https://bugs.launchpad.net/ubuntu/+source/kpackagekit/+bug/368538/comments/4

Found in Kubuntu Karmic alpha5, with updated packages.

[Jonathan Thomas (echidnaman)]

From what I see, KPackageKit's Messages.sh script is exporting the po files correctly as all lowercase, so I would doubt that this is a problem with the upstream code. Transferring this to the language-pack-kde-et-base package and filing a bug against the Ubuntu Translation project for further triaging.

[David Planella (dpm)]

I'll need to further investigate this, but both the Jaunty and Karmic templates in Launchpad use the KPackageKit translation domain, which if I'm not mistaken is the one used upstream as well.

There don't seem to be changes between Jaunty and Karmic in Launchpad, then.

[Alessandro Ghersi (alessandro-ghersi)]

Using italian localization, KpackageKit is all untranslated in Karmic

[Jonathan Thomas (echidnaman)]

The translation templates in Rosetta need to be changed to reflect upstream's change of translation domain. (KPackageKit -> kpackagekit)

[Aron Xu (happyaron)]

it *is* kpackagekit as its domain name before I have taken any action, could you please check if this is fixed or caused by something else?

[David Planella (dpm)]

Thanks Aron for looking into this. I changed the domain to kpackagekit some days ago and I notified Jonathan by replying to his message on kubuntu-devel (https://lists.ubuntu.com/archives/kubuntu-devel/2009-October/003366.html), I just hadn't realised that the u-t-c list was not on CC. Sorry for any inconvenience.

Rivo, you reported the original bug. Could you please test if this has now been solved in your system?

[Rivo Laks (rivol)]

Yup, I can confirm that the problem is solved now.
Thanks :-)