[Kst] Questions regarding the translation of Kst

[Burkhard Lück]

Am Samstag, 15. März 2014, 12:00:35 schrieb Nicolas Brisset:
> Hi Burkhard,
> 
> Following the discussions on https://bugs.kde.org/show_bug.cgi?id=328641 and
> a mail received from a Polish translator
> (http://mail.kde.org/pipermail/kst/2014-March/021801.html) interested in
> the Kst translation, I looked a bit at the code and I'm trying to
> understand all the options and tools we have for translations. I put some
> information together, see below, but I'm still looking for the details
> especially in case of dual KDE and pure Qt apps. Since you offered to
> contact you to get some help, here I am :-)
> 
[snipped a lot of correct infos]

Please let me summarize the workflow and status of translation in kst:

1) GUI

1.1) Messages.sh file in kst repo
That is in place and afaik working fine.

1.1) Proper tr() calls for all user visible strings
Here is apparently room for improvements ;-)

1.1.1) Extraction fails for two strings in aboutdialog.cpp, patch attached.

1.1.2) Missing extraction e.g. all menu items in "Create -> Standard Plugin", 
"Create -> Fit Plugin" and "Create -> Filter Plugin"
Apparently you find them by grepping for pluginName() + pluginDescription() in 
src/datasources/*/*cpp + src/plugins/dataobject/*/*.cpp +  
src/plugins/filters/*/*.cpp+src/plugins/fits/*/*.cpp
Missing extraction in labelbuilder.cpp, patch attached.

1.1.3) Word Puzzles, see 
http://techbase.kde.org/Development/Tutorials/Localization/i18n_Mistakes#Pitfall_.232:_Word_Puzzles
for example in
filterfitdialog.cpp:159:    title = tr("Edit ") + pluginName + tr(" Plugin");
filterfitdialog.cpp:161:    title = tr("New ") + pluginName + tr(" Plugin");
basicplugindialog.cpp:55:    title = tr("Edit ") + pluginName + tr(" Plugin");
basicplugindialog.cpp:57:    title = tr("New ") + pluginName + tr(" Plugin");

1.2) A script on the kde l10n server runs each night and extracts the strings 
and merges them with the existing translation, and 15 translation teams have 
already start to work. So far kst has 6 fully translated gui catalogs.
You should announce a new release on kde-i18n-doc at kde.org and give the teams 2 
or 3 weeks to update their translation.

1.3) Pulling the existing translations and build them as qm files with kst 
works

2) DOCUMENTATION
If the documentation in docbook/kst/ is adapted to kst2 please mail to kde-
i18n-doc at kde.org. Then it will be included in Scripty's workflow. The docbooks 
are extracted to po/xgettext files. If a team has finished the translation, they 
generate their language docbooks in l10-kde4/[lang]/docs/extragear-
graphics/kst. 
How is the documentation opened from kst? KDE-Apps have an action "Help->foo 
Handbook" with the shortcut F1 to display the documentation in khelpcenter.
The documentation will be then also online available on docs.kde.org in html 
and pdf format.
The script buildpdf.sh to generate pdfs is located in 
http://websvn.kde.org/trunk/www/areas/docs/

There is afaik no generation from docbooks into other formats like (.chm or 
.qch) used in kde, but afaik this is also possible.

Thanks.

-- 
Burkhard Lück
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aboutdialog.cpp.diff
Type: text/x-patch
Size: 758 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kst/attachments/20140318/af971046/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: labelbuilder.cpp.diff
Type: text/x-patch
Size: 1043 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kst/attachments/20140318/af971046/attachment-0001.diff>