<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
Right, if we can manage to setup this, that should make everyone
happy :)<br>
<br>
Timothée<br>
<br>
<br>
Le 22/05/2018 à 09:04, Johnny Jazeix a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAEtcAPE1oMW6s+aBTM9CuuDWLYY739G95MuUO06ofbH9w=gt6Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">Hi,<br>
<br>
</div>
<div class="gmail_extra">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).<br>
</div>
<div class="gmail_extra">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.<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">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.<br>
</div>
<div class="gmail_extra">If it is scripted, there won't be more
work for the releaser.<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">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.<br>
<br>
</div>
<div class="gmail_extra">Johnny<br>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
...<br>
</body>
</html>