Helping to translate PackageKit

Due to the way PolicyKit works, not all the translations can be done in the client tools. The authentication dialogs come from the daemon and thus don’t get translated by the GNOME translation team. The GNOME guys are rocking doing the client stuff, but the daemon remains untranslated.

If you have a spare few minutes (only 88 short strings), please send me a .po file from this pot file. You can see what po files already exist in gitweb. I really appreciate it, thanks.

Richard.

Published by

hughsie

Richard has over 10 years of experience developing open source software. He is the maintainer of GNOME Software, PackageKit, GNOME Packagekit, GNOME Power Manager, GNOME Color Manager, colord, and UPower and also contributes to many other projects and opensource standards. Richard has three main areas of interest on the free desktop, color management, package management, and power management. Richard graduated a few years ago from the University of Surrey with a Masters in Electronics Engineering. He now works for Red Hat in the desktop group, and also manages a company selling open source calibration equipment. Richard's outside interests include taking photos and eating good food.

14 thoughts on “Helping to translate PackageKit”

  1. Wouldn’t it be a lot easier to also include the policy file in gnome-packagekit and the manually sync the translations to the PackageKit tarball? I’m pretty sure you can have separate po/ directories – for buildsys stuff, look at the weather applet and/or libgweather for Locations.xml.

  2. Please email me an url or email address where you want receive a hungarian translation. hrgyster WORM GMail POINT com

  3. Richard,

    I’m sure the Fedora translation community would love to contribute to PackageKit, so you might want to allow them to use Transifex to send translations directly to your repo.

    https://translate.fedoraproject.org/submit/maintainers/info
    http://fedoraproject.org/wiki/L10N/FAQ#add-transifex

    Contrary to Launchpad, you don’t need to copy your files downstream: commits from the downstream community are sent directly to the upstream repo. Oh, and it’s open source.

  4. >include the policy file in gnome-packagekit

    Yes, this is a good idea. I’ll see how feasable it is to keep the two in sync.

  5. >Launchpad.net could help

    It’s just not upstream, sorry. It adds another layer above the intl team and just doesn’t work, sorry.

  6. >use Transifex to send translations directly to your repo

    Yes, I’m thinking about this. I want to be careful not to tie things exclusively into a Red Hat / Fedora system, but it certainly looks more “upstream” than Launchpad.

Comments are closed.