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

List:       kde-i18n-doc
Subject:    Re: GCompris rss feed
From:       Johnny Jazeix <jazeix () gmail ! com>
Date:       2018-05-27 13:10:10
Message-ID: CAEtcAPH2HLLeqFmnPz8M=hnr9x7dMcAei-SDUYEvJnj7PL-KxA () mail ! gmail ! com
[Download RAW message or body]

hi,

I'm planning to commit the python script to update the pot file with the
news.

Is the python3 module 'polib' installed on the machine running the script?

Johnny


2018-05-22 10:50 GMT+02:00 Timoth=C3=A9e Giet <animtim@gmail.com>:

> Hi,
>
> Right, if we can manage to setup this, that should make everyone happy :)
>
> Timoth=C3=A9e
>
>
> Le 22/05/2018 =C3=A0 09:04, Johnny Jazeix a =C3=A9crit :
>
> 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 bri=
ng
> more translations).
> It's not just an issue of who should learn what or what is easier to lear=
n
> 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 th=
e
> 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 car=
e
> 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
>
> ...
>

[Attachment #3 (text/html)]

<div dir="ltr"><div>hi,<br><br>I&#39;m planning to commit the python script to update \
the pot file with the news.<br><br>Is the python3 module &#39;polib&#39; installed on \
the machine running the script?<br><br></div>Johnny<br><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">2018-05-22 10:50 GMT+02:00 Timothée \
Giet <span dir="ltr">&lt;<a href="mailto:animtim@gmail.com" \
target="_blank">animtim@gmail.com</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_4911885888700685013moz-cite-prefix">Hi,<br>
      <br>
      Right, if we can manage to setup this, that should make everyone
      happy :)<span class="HOEnZb"><font color="#888888"><br>
      <br>
      Timothée</font></span><span class=""><br>
      <br>
      <br>
      Le 22/05/2018 à 09:04, Johnny Jazeix a écrit  :<br>
    </span></div><span class="">
    <blockquote type="cite">
      <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&#39;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&#39;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&#39;t care about the po file, and
          for KDE translators, you don&#39;t have any exception to make for
          GCompris. And we don&#39;t lose the existing ones.<br>
          <br>
        </div>
        <div class="gmail_extra">Johnny<br>
        </div>
        <div class="gmail_extra"><br>
        </div>
      </div>
    </blockquote></span>
    ...<br>
  </div>

</blockquote></div><br></div>



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