27 Sep
2008
27 Sep
'08
4:46 a.m.
Bey Youcef wrote:
On 9/26/08, Paul Libbrecht <paul(a)activemath.org>
wrote:
If you don't want to use the running wiki for translation, you can work
with the XML source files that generate the documents, for example see
http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/wiki/src/main/resources…
You can make a tool that extracts the content from the wiki into files
accepted by OmegaT (or another translation tool) and back into XML files
once the translation is done.
it is well known that translating documentation
is long. It generally is
delayed ;-))
Not exactly. It depends on size of documents. The translation of XWiki pages
(not documentation) can be done in acceptable time. I'm talking about the
Wiki pages, like the main page, and some help pages.
The scenario is simple : strings must be stored in separte files.
Translators recover these files and translate them in computer-aides
translation environments (e.g OmegaT). Once the translation is done, these
files are integrated into XWiki. The last step is QA! The XWiki was not designed for localization that's
why the resources
properties are used for conversion. In fact, these resources can't be used
for managing format of document. They don't support metadata...This is one
among another reasons for which LISA proposed the XLIFF standard.
I tend to disagree here, XWiki was designed with localization in mind,
that is why also documents, not just static bundles, can be translated.
By the way, did you read
http://platform.xwiki.org/xwiki/bin/view/Features/I18N ?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/