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

List:       kde-i18n-doc
Subject:    Re: gcompris website update
From:       Johnny Jazeix <jazeix () gmail ! com>
Date:       2018-09-22 12:06:38
Message-ID: CAEtcAPGF=VNVy2muKf615N=qVo6WpcYcUsf8w5gq2WTaxXmH4Q () mail ! gmail ! com
[Download RAW message or body]

Hi,

the last commit I did (
https://cgit.kde.org/websites/gcompris-net.git/commit/?id=ea8e47f02b1bf7b421cc05b935e2a997550a1791)
should separate the strings correctly.
Except the extra '\' for line-breaking (it's added by polib when escaping
the strings), all should be good.
I also commited the news already translated with the previous method so no
work has been lost.

Johnny

Le ven. 13 juil. 2018 Ã  19:33, Karl Ove Hufthammer <karl@huftis.org> a
écrit :

> Johnny Jazeix skreiv 05. juni 2018 21:08:
> > We updated strings for the GCompris website
> > (https://l10n.kde.org/stats/gui/trunk-kde4/po/gcompris-net.po/) and
> > added the latest news in the po.
> >
> > * For the latest news, is it ok with you if we always put the 3 latest
> > news in the po file (for test purpose I only put the last one)?
> > * Is the format good enough or should we split the news in more
> > paragraph so it would be easier to translate?
>
> I haven't have time to take a look at it before now, but here's my
> comments:
>
>   * Yes, please split the news into several strings. Translating long
>     texts is hard, and it's easy to miss stuff. And if you change just a
>     single word in the original, the entire string changes. I think one
>     string for each paragraph (‘p' element) would work well. And one
>     string for each list item (‘li' element).
>   * The HTML stuff doesn't need to be translated. Right now, the string
>     begins with this block of HTML code:
>     \\n<img src='news/images/gcompris360.png'\\n alt='gcompris
>     banner'\\n     style='float: right; width: 360px; padding-left:
>     10px; cursor: pointer;'\\n
>     onclick=\\"window.open('news/images/gcompris360.png')\\"/>\\n\\n \\n
>   * Also, the outer-most HTML elements, e.g. ‘<li class=\\"puce\\">',
>     don't need to be included in the translatable strings. (But it would
>     be nice if there was a comment marking the string as a list item or
>     a paragraph.) It's OK to include ‘inline' HTML elements, e.g. <em>
>     and <strong>.
>   * The line-breaking character \n has an extra \ character: \\n. This
>     should be fixed.
>
> --
> Karl Ove Hufthammer
>
>

[Attachment #3 (text/html)]

<div dir="ltr"><div><div><div><div dir="ltr"><div>Hi,<br><br></div>the last commit I \
did (<a href="https://cgit.kde.org/websites/gcompris-net.git/commit/?id=ea8e47f02b1bf7 \
b421cc05b935e2a997550a1791">https://cgit.kde.org/websites/gcompris-net.git/commit/?id=ea8e47f02b1bf7b421cc05b935e2a997550a1791</a>) \
should separate the strings correctly.<br></div>Except the extra &#39;\&#39; for \
line-breaking (it&#39;s added by polib when escaping the strings), all should be \
good.<br></div>I also commited the news already translated with the previous method \
so no work has been lost.<br></div><br></div>Johnny<br><div><div><div><br><div><div \
class="gmail_quote"><div dir="ltr">Le  ven. 13 juil. 2018 Ã   19:33, Karl Ove \
Hufthammer &lt;<a href="mailto:karl@huftis.org">karl@huftis.org</a>&gt; a écrit  \
:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">Johnny Jazeix skreiv 05. juni 2018 21:08:<br> &gt; We \
updated strings for the GCompris website <br> &gt; (<a \
href="https://l10n.kde.org/stats/gui/trunk-kde4/po/gcompris-net.po/" rel="noreferrer" \
target="_blank">https://l10n.kde.org/stats/gui/trunk-kde4/po/gcompris-net.po/</a>) \
and <br> &gt; added the latest news in the po.<br>
&gt;<br>
&gt; * For the latest news, is it ok with you if we always put the 3 latest <br>
&gt; news in the po file (for test purpose I only put the last one)?<br>
&gt; * Is the format good enough or should we split the news in more <br>
&gt; paragraph so it would be easier to translate?<br>
<br>
I haven't have time to take a look at it before now, but here's my comments:<br>
<br>
   * Yes, please split the news into several strings. Translating long<br>
      texts is hard, and it's easy to miss stuff. And if you change just a<br>
      single word in the original, the entire string changes. I think one<br>
      string for each paragraph (‘p' element) would work well. And one<br>
      string for each list item (‘li' element).<br>
   * The HTML stuff doesn't need to be translated. Right now, the string<br>
      begins with this block of HTML code:<br>
      \\n&lt;img src=&#39;news/images/gcompris360.png&#39;\\n alt=&#39;gcompris<br>
      banner&#39;\\n         style=&#39;float: right; width: 360px; padding-left:<br>
      10px; cursor: pointer;&#39;\\n<br>
      onclick=\\&quot;window.open(&#39;news/images/gcompris360.png&#39;)\\&quot;/&gt;\\n\\n \
                \\n<br>
   * Also, the outer-most HTML elements, e.g. ‘&lt;li \
                class=\\&quot;puce\\&quot;&gt;',<br>
      don't need to be included in the translatable strings. (But it would<br>
      be nice if there was a comment marking the string as a list item or<br>
      a paragraph.) It's OK to include ‘inline' HTML elements, e.g. &lt;em&gt;<br>
      and &lt;strong&gt;.<br>
   * The line-breaking character \n has an extra \ character: \\n. This<br>
      should be fixed.<br>
<br>
-- <br>
Karl Ove Hufthammer<br>
<br>
</blockquote></div></div></div></div></div></div>



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