GCompris rss feed
Timothée Giet
animtim at gmail.com
Tue May 22 08:50:55 UTC 2018
Hi,
Right, if we can manage to setup this, that should make everyone happy :)
Timothée
Le 22/05/2018 à 09:04, Johnny Jazeix a écrit :
> Hi,
>
> on my side, I would also prefer have it on po files as I prefer it to
> be standard instead of having our own way to deal with it (and it
> should bring more translations).
> It's not just an issue of who should learn what or what is easier to
> learn or how many people have to change their habits but having it
> standard and avoiding doing exceptions for projects that could be avoided.
>
> A solution that should work for everyone is to have the last n news on
> the po file. In the release script, if there is a translation for a
> language, we generate the new html file for this locale, commit and
> push it.
> If it is scripted, there won't be more work for the releaser.
>
> This way, for French, if we create it directly via the html, we won't
> care about the po file, and for KDE translators, you don't have any
> exception to make for GCompris. And we don't lose the existing ones.
>
> Johnny
>
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20180522/3a55b212/attachment.html>
More information about the GCompris-devel
mailing list