[Kst] Tasks for Google Code-In

[Alexander Potashev]

2011/11/26  <nicolas.brisset at free.fr>:
> yes, I remember that mail very well, and one mail from this discussion is referenced in the Google Code-In proposal:
> http://google-melange.appspot.com/gci/task/view/google/gci2011/7134268 which contains very interesting pointers.
>
> My idea for this task is to define clearly the steps required to get Kst2 infrastruture set up so that translations can be done as for other KDE apps.
> I believe that things have changed a bit since KDE switched to git, but nobody in the Kst team is completely aware of how things work now. So a detailed list of steps would be nice, maybe we can even achieve some straight away:
> - where to put the code? (svn or git, which repository, ...)

I think, you should firstly try to move Kst code into KDE Playground
(start reading from here:
http://community.kde.org/Sysadmin/GitKdeOrgManual#Personal_scratch_repositories).
I can't guarantee that KDE admins will approve the move of a Qt-only
application into KDE Playground, so I would recommend to firstly as
people in the "kde-core-devel" mailing list. Don't forget to say that
Kst has some plans to optionally support KdeLibs features in the
future.

> - how to pass messages on to translators (how to generate .pot files and back, as Marble does)?

Since all translatable messages in Kst source code are currently
wrapped in Qt-style "tr()" function calls, you only need a line
similar to the last line from
http://quickgit.kde.org/?p=marble.git&a=blob&f=Messages.sh in your
Messages.sh. Then you enable extraction of messages in your project
settings at projects.kde.org, and the next day the translation
template (kst2_qt.pot?) will appear in the KDE SVN.

A .po translation file can then be converted into a Qt-style .ts or
.qm file (look here:
http://quickgit.kde.org/?p=marble.git&a=tree&f=tools/translations)
when you need to make a Qt-only package for Kst2.


-- 
Alexander Potashev