[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Questions about releasing playground app
From:       Simon Persson <simon.persson () mykolab ! com>
Date:       2019-09-20 0:20:00
Message-ID: 20190920002019.BAAE2282829 () letterbox ! kde ! org
[Download RAW message or body]


On Sep 20, 2019 03:48, Luigi Toscano <luigi.toscano@tiscali.it> wrote:
> 
> Luigi Toscano ha scritto: 
> > Simon Persson ha scritto: 
> > > Hello! 
> > > 
> > > 
> > > I recently started moving the Kup backup scheduler from github to KDE hosting. 
> > > As part of this migration I have some questions, I have looked all over KDE's 
> > > web pages but not found any answers. I hope someone here can help to start 
> > > sorting this out for me. 
> > > 
> > > 
> > > How are translations handled for playground applications - should my release 
> > > tarball still include .po files? 
> > 
> > Yes, but the releaseme script does it automatically. Please refer to: 
> > 
> > https://community.kde.org/ReleasingSoftware 
> > 
> > (with the caveat that applications in playground ends up into the 
> > download.kde.org/unstable/) 
> > 
> > > If so, how do I work with KDE translation teams? Translators commit updated 
> > > files directly in the source repo? 
> > > 
> > > If not, that would mean making use of KDE's translation team and then my 
> > > message catalog will be included in the KDE localisation packages, right? And 
> > > in this case, how to handle setting up translations and importing all the 
> > > existing messages? I already made a Messages.sh file in the root of the repo. 
> > > Should I go around contacting all individual language teams and provide them 
> > > the existing .po files for them to check and incorporate? 
> > 
> > Translation templates are automatically extracted every day in a separate 
> > place by a set of script called scripty (on the subversion repository, see 
> > https://l10n.kde.org/docs/translation-howto/ ). The releaseme script knows 
> > where to find them. 
> > 
> > That said, before releasing, we need to move the po/ folder away from the kup 
> > repository and configure the extraction for kup on the scripty side. I can 
> > work on it later today or tomorrow. 
> > 
> Sorry, I'm a bit late on this (still on my TODO). In the meantime, could you 
> please tell the existing Kup translators that the workflow for translating Kup 
> is now different and they should get in touch with the various KDE team 
> coordinator for their languages? (see https://l10n.kde.org/). 
> 

No worries, thanks for the info so far. I agree, I should inform the team on \
transifex about the change and also pull the latest translations from there into the \
git repo.

I've been adding screenshots and working on appstream metadata as described in the \
document you linked.

> Ciao 
> -- 
> Luigi 


[prev in list] [next in list] [prev in thread] [next in thread]