<div dir="ltr"><div class="gmail_extra"></div><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 class="gmail_extra"><div class="gmail_quote">2018-05-21 16:09 GMT+02:00 Timothée Giet <span dir="ltr"><<a href="mailto:animtim@gmail.com" target="_blank">animtim@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><div><div class="gmail-h5">
<div class="gmail-m_1304722881853105409moz-cite-prefix">Le 21/05/2018 à 12:45, Horia PELLE a
écrit :<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div>Karl Ove's thoughts about the rss news resonate with my
thoughts.
<div dir="auto">Indeed, for the translators without any git
experience, it would be much easier to just translate a text
in a PO file. Is there a size limit for PO files?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Horia Pelle</div>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">Pe 21 mai 2018 10:10, "Karl Ove
Hufthammer" <<a href="mailto:karl@huftis.org" target="_blank">karl@huftis.org</a>> a scris:<br type="attribution">
<blockquote class="gmail-m_1304722881853105409quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_1304722881853105409quoted-text">
<div class="gmail-m_1304722881853105409m_-3100835741525581953moz-cite-prefix">Timothée
Giet skreiv 19. mai 2018 11:17:<br>
</div>
<blockquote type="cite">
<p>For the news, we use a little different system
in which each news for each language is a
different html file, so translators who want to
translate the news should just clone the
gcompris-net git repo and add translated news in
the News folder. (see for example, 20180313.html
is the base English file and 20180313-fr.html is
the French version) </p>
<p>Also if some people translate a news, please
ping me here or on IRC and I'll update the
website with it.
</p>
<p>I think it would make the po file too heavy if
we added every news to it. Also it's much more
convenient and faster to translate a news and
directly push it to the website, without going
through the .po.</p>
</blockquote>
</div>
<p>Well for us translators, it’s certainly *not* more
convenient and faster to:</p>
<p> – Learn git and clone the gcompris-net repo – Find
the .html file and manually edit it – Monitor the
source .html file and manually apply any edits to
our translation – Learn to create a pull request for
the translation</p>
<p>than to</p>
<p> – Just notice that there are some new strings in a
.po file and translate them (just like we do for all
other KDE applications and documentation).</p>
<p>Couldn’t you just include the two or three *latest*
news items (i.e. the news shown on the front page)
in the PO file? Then the .po file would never get
very large.</p>
<div class="gmail-m_1304722881853105409signature-text">
<p>-- Karl Ove Hufthammer
</p>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
</div></div><p>Hi,</p>
<p>I can understand from your comments that the solution I proposed
is not ideal for you, but still I would rather avoid to put the
news in the po.</p>
<p>I don't want to restrict translations to just last 3 news, we
would risk to loose some history of existing news translated in
French, and that would also mean no backup for any older news
translations, which is bad...)<br>
</p>
<p>Also another point is that I or Johnny do the FR translations,
and personally I really don't want to have to go through the po to
add them, it's already enough complicated setup (also on my side,
I would need to learn more of SVN and the process used to apply
translations...) And also I don't want to make a different setup
for FR and other languages. <br>
</p>
<p>An other way we could do, that sounds easier for translators that
don't know git, would be:</p>
<p>-Each time we post a news, we also write a mail to translators
list with the news file to translate (would gcompris-devel list
work, or better use kde-i18n list? also it can be just a link to
the html file to download from git from browser, so no big email
content issue, and no git clone or commit involved for
translators)<br>
</p>
<p>-When someone makes a news translation, send it to
<a class="gmail-m_1304722881853105409moz-txt-link-abbreviated" href="mailto:animtim@gcompris.net" target="_blank">animtim@gcompris.net</a> with the contributor's name+email and I'll
push it to git with the author credit, and push the website update
at the same time.</p>
<p>Another positive side of this solution is that it would be easier
to directly know when a news is translated and I have to push it
on the website, rather than having to monitor every day the po
file...<br>
</p>
The main difference remaining is that translators still would have
to edit inside the html file, but really that's not very
technical... I'd say it's easier to do that than most of the things
involving po files, or than learning SVN or GIT...<br>
<br>
Could that work for you?<span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
Timothée<br>
<br>
</font></span></div>
</blockquote></div><br></div></div>