From kde-i18n-doc Sat Sep 22 12:06:38 2018 From: Johnny Jazeix Date: Sat, 22 Sep 2018 12:06:38 +0000 To: kde-i18n-doc Subject: Re: gcompris website update Message-Id: X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=153761859025542 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--000000000000767e9205767497c8" --000000000000767e9205767497c8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, the last commit I did ( https://cgit.kde.org/websites/gcompris-net.git/commit/?id=3Dea8e47f02b1bf7b= 421cc05b935e2a997550a1791) 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 =C3=A0 19:33, Karl Ove Hufthammer a =C3=A9crit : > 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=E2=80=99t have time to take a look at it before now, but here=E2= =80=99s my > comments: > > * Yes, please split the news into several strings. Translating long > texts is hard, and it=E2=80=99s 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 (=E2=80=98p=E2=80=99 element) would work we= ll. And one > string for each list item (=E2=80=98li=E2=80=99 element). > * The HTML stuff doesn=E2=80=99t need to be translated. Right now, the = string > begins with this block of HTML code: > \\n3D'gcompris banner'\\n style=3D'float: right; width: 360px; padding-left: > 10px; cursor: pointer;'\\n > onclick=3D\\"window.open('news/images/gcompris360.png')\\"/>\\n\\n \\= n > * Also, the outer-most HTML elements, e.g. =E2=80=98
  • =E2=80=99, > don=E2=80=99t need to be included in the translatable strings. (But i= t would > be nice if there was a comment marking the string as a list item or > a paragraph.) It=E2=80=99s OK to include =E2=80=98inline=E2=80=99 HTM= L elements, e.g. > and . > * The line-breaking character \n has an extra \ character: \\n. This > should be fixed. > > -- > Karl Ove Hufthammer > > --000000000000767e9205767497c8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Except the ext= ra '\' for line-breaking (it's added by polib when escaping the= strings), all should be good.
    I also commited the news already tr= anslated with the previous method so no work has been lost.

    Johnny

    Le=C2=A0ven. 13 juil. 2018 =C3=A0=C2=A019:33, Karl Ove Hufthammer = <karl@huftis.org> a =C3=A9crit= =C2=A0:
    Johnny Jazeix skreiv 05. ju= ni 2018 21:08:
    > We updated strings for the GCompris website
    > (https://l10n.kde.org/stats/gui/tr= unk-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=E2=80=99t have time to take a look at it before now, but here=E2=80= =99s my comments:

    =C2=A0 * Yes, please split the news into several strings. Translating long<= br> =C2=A0 =C2=A0 texts is hard, and it=E2=80=99s easy to miss stuff. And if yo= u change just a
    =C2=A0 =C2=A0 single word in the original, the entire string changes. I thi= nk one
    =C2=A0 =C2=A0 string for each paragraph (=E2=80=98p=E2=80=99 element) would= work well. And one
    =C2=A0 =C2=A0 string for each list item (=E2=80=98li=E2=80=99 element).
    =C2=A0 * The HTML stuff doesn=E2=80=99t need to be translated. Right now, t= he string
    =C2=A0 =C2=A0 begins with this block of HTML code:
    =C2=A0 =C2=A0 \\n<img src=3D'news/images/gcompris360.png'\\n alt= =3D'gcompris
    =C2=A0 =C2=A0 banner'\\n=C2=A0=C2=A0=C2=A0=C2=A0 style=3D'float: ri= ght; width: 360px; padding-left:
    =C2=A0 =C2=A0 10px; cursor: pointer;'\\n
    =C2=A0 =C2=A0 onclick=3D\\"window.open('news/images/gcompris360.pn= g')\\"/>\\n\\n \\n
    =C2=A0 * Also, the outer-most HTML elements, e.g. =E2=80=98<li class=3D\= \"puce\\">=E2=80=99,
    =C2=A0 =C2=A0 don=E2=80=99t need to be included in the translatable strings= . (But it would
    =C2=A0 =C2=A0 be nice if there was a comment marking the string as a list i= tem or
    =C2=A0 =C2=A0 a paragraph.) It=E2=80=99s OK to include =E2=80=98inline=E2= =80=99 HTML elements, e.g. <em>
    =C2=A0 =C2=A0 and <strong>.
    =C2=A0 * The line-breaking character \n has an extra \ character: \\n. This=
    =C2=A0 =C2=A0 should be fixed.

    --
    Karl Ove Hufthammer

    --000000000000767e9205767497c8--