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

List:       kde-i18n-doc
Subject:    Re: gcompris website update
From:       Karl Ove Hufthammer <karl () huftis ! org>
Date:       2018-07-13 17:33:02
Message-ID: a928a1cf-ffc5-ab30-68aa-e03d63cd3a62 () huftis ! org
[Download RAW message or body]

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

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