Hi,
As you know the Plasma desktop has since the release of Leap a new updater instead of Apper. The new package is plasma-pk-updates and has been created by the makers of the plasma networkmanager. The applet seems to work fine, but doesn't have any translations.
I have checked out the source and fortunately the source has been prepared to work with translations, so I have the .pot files for it. At the moment there are two pot files (one for the setup dialog and one for the plasmoid itself)
I found an old page on the openSUSE wiki indicating the procedure to ask for translations of a new program. I am not sure how up-to-date this page is but it indicated that I should first send an email to this mailinglist. Hi, Raymond. I'm not sure how old that page is, but the information looks correct -
2015-11-16 22:52 GMT+03:00 Raymond Wooninck <tittiatcoke@gmail.com>: this list is the best place to discuss new translations. Basically you should consider 3 main issues: 0) Maintainership on SVN side. While for the first time you can send those pot files here, general case is that you need an svn account to send us newer versions of pot files (checking out new translations can be done anonimously). You can search this list for recent requests for new languages to find the password generation script and target email for such a request. 1) Maintainership on distro side. Getting the fresh pot and pushing new translations back to the real distro users is (and always was) the main problem of the whole translation process here. We are informed of some files, where translations were not used in a distro for several years. Another example is that there are already five KDE-related files for translation available in our repo, with kde-maintainers@suse.de enlisted as maintainer for those files. The sad truth is that at least some of them belong to software not used anymore in openSUSE (like simple-ccsm-kde) and just rot there without any attention from a so called maintainer. If you would like to submit a new file for translation, you should also keep in mind that you'll have to keep it updated and also check out new translations on a regular basis. 2) Upstream conflicts. If the source code is written in translation-ready form, then sooner or later we will face the fact that upstream translations will appear and it should be decided now how to handle them. We already have an experience with KDE desktop files, where our translations get overwrited by upstream content, and it is pretty demotivating. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org