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

List:       kde-i18n-doc
Subject:    Re: gcompris website in kde
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2017-04-30 21:59:47
Message-ID: cdb96aab-f4d0-d47c-6ea4-6717e2d99c1c () tiscali ! it
[Download RAW message or body]

JAZEIX Johnny ha scritto:
> Hi,
> 
> We'd like to use the KDE infrastructure to translate the GCompris website.
> The actual site is a jinja2 static (no php) generated website
> (https://cgit.kde.org/websites/gcompris-net.git/).
> It uses babel to extract the strings ({% trans %}text{% endtrans %}) and
> create the pot file.
> 
> The news are html pages manually translated without any i18n support
> (https://cgit.kde.org/websites/gcompris-net.git/tree/news/20161223.html and
> its French translation:
> https://cgit.kde.org/websites/gcompris-net.git/tree/news/20161223-fr.html).
> My first thought was to replace the html file with a xml (with tags for
> translation), generate the pot (via Messages.sh like for okular website for
> example) and then create again the html file with the translated strings (via
> xslt).

But why not use the same mechanism already used for the site also for the news
(jinja2 templates marked as translatable)?

> 
> My questions are:
> * Regarding the website itself, can we still use babel and its pot file (so
> for now, the Messages.sh would just be do a copy of this file to the
> $podir/gcompris-net.pot)?

More than "copy it", it would generate it directly in that location.

> 
> * We already have existing translations for some languages in
> https://cgit.kde.org/websites/gcompris-net.git/tree/locale, is it possible to
> keep them (without having to copy/paste each one of them, else I can do it)?

We can import them on SVN.

> 
> * Regarding the news, once we have the po files with the translations, is it
> possible to apply it to the xml (via xslt or script) to get the translated xml?

Let's see if we can find another easier way first :)

Ciao
-- 
Luigi
[prev in list] [next in list] [prev in thread] [next in thread]