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

List:       kde-devel
Subject:    Re: Translating custom XML format
From:       Burkhard =?iso-8859-1?q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2009-02-02 15:59:51
Message-ID: 200902021659.51300.lueck () hube-lueck ! de
[Download RAW message or body]

Am Montag 02 Februar 2009 14:29:36 schrieb Vladimir Kuznetsov:
> Hello All,
>
> My application uses data files with custom XML-based format which includes
> user-visible strings, and I want to make it translatable. Currently that
> files are translated by creating copies in l10n subdirectories in
> application data directory, but translators wants normal .po - based
> translation mechanism.
>
> Such mechanism is already implemented in KDE for translating docbooks. Is
> it possible to implement something similar for translating non-docbook XML
> files ?
>
> In worst case I could write scripts for extracting strings to .po files and
> putting them back myself, but will it be possible to instruct scripty to
> run my scripts ?

While the gui messages processing is handled completely by scripty, the 
documentation translation tool chain is somewhat different:

1. All documentation subdirs of the kde modules are pulled into 
l10n-kde4/documentation via svn externals from anonsvn.
Adjusting these externals is the i18n coordinators job.
The docmessage templates in l10n-kde4/templates/docmessages are generated by 
the translators with a cron job on a local machine - not on the i18 server - 
and comitted to the svn repository.
The docmessage extraction is done by running the script  
l10n-kde4/scripts/createdoctemplates.sh. The real job of extraction from 
docbook to pot is done with xml2pot from the kdesdk module. xml2pot is 
specially designed to work with the markup used in the kde docbooks and will 
not work with your xml files.

2. Second part is automatically done by scripty once a day, merging templates 
to language po files.

3. If the language po files for a documentation are fully translated, the 
generation of the translated language docbooks is done manually by the 
coordinators of each translation team by running the script  
l10n-kde4/scripts/update_xml, which invokes po2xml from kdesdk to put the 
translated messages into the language docbook.

-- 
Burkhard Lück
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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