Thanks for your mail. We will certainly take you up on your offer! Some of us will meet in the next few days to try and come up with a better translation work flow. We still have a few loose ends to tie up. I will contact you next week with more information about how to get started with the translations.
Sent fr om my HTC
----- Reply message -----
From: “Japhet Kamala” email@example.com
Date: Wed, Sep 15, 2010 13:10
Subject: [Dhis2-devs] [Dhis2-documenters] Translation workflow
To: firstname.lastname@example.org, “Knut Staring” email@example.com
Cc: “philippe” firstname.lastname@example.org, “dhis2-documenters” email@example.com, “Johan Lemarchand” firstname.lastname@example.org, “narodar” email@example.com, “DHIS 2 developers” firstname.lastname@example.org
Thanks for this debate
May I know how many languages do we need to translate this manuals
Am in Tanzania is Swahili needed
If so am ready to work on it
Hope to hear from you
University Computing Centre Ltd
Tel: +255 22 2410645
Fax: +255 22 2410690
Cell +255 717 001807
+255 787 123115
From: “email@example.com” firstname.lastname@example.org
To: Knut Staring email@example.com
Cc: philippe firstname.lastname@example.org; DHIS 2 developers
email@example.com; Johan Lemarchand firstname.lastname@example.org;
narodar email@example.com; dhis2-documenters
Sent: Wed, 15 September, 2010 14:05:35
Subject: Re: [Dhis2-documenters] [Dhis2-devs] Translation workflow
Thanks for raising this topic. I have tried to get the french translation
done with the help of Lars using the PO Editor, but I gave up because of
problems with commit process. But this is a technical problem that can be
solved with little work. I found the PO Editor ok and quite easy to use.
And maybe it is the best way to go.
The problem here for me is organizational. Because for instance I know
that Edem also is working on French translation too, so we need to
synchronize our work to avoid duplication of efforts. I think we first need
to create translation teams by languages and select a head for each team.
Then we must provide a timeline to get the job done. Each team will
organise itself to meet the goal in the requested time. The mean they will
use (machine or human or both) is not in that case important if the team
can ensure that they are ok with the translation provided at the end of the
Hope this contribution is helpful…
On Wed, 15 Sep 2010 09:34:44 +0200, Knut Staring firstname.lastname@example.org wrote:
Moving this discussion to the main developer list as well as the
documentation list to ensure input from all concerned.
Thanks to the team currently contributing to a French translation of
the DHIS manual and inline help. Jason and I have been working on find
the best workflow for this work, but it is not obvious that there is
really a good one, because there are a number of issues that may be
Ideally, we would like to:
keep the original English documentation in DocBook XML format,
which allows us to generate many formats, such as PDF and HTML, as
well as incorporate the text into the online help inside DHIS 2
keep both the DocBook structure and translated text (which can be
in PO files) under some sort of version control, so we can track
changes, and readily generate artefacts such as PDFs
make it easy for translators, so they can concentrate on the
language rather than tools like Bazaar, Maven, and DocBook/XML
3b) I thought it would be easier to start from a machine translation
and do corrections, rather than start with just the English and write
everything. I would very much like the opinion of people who have some
actual experience correcting Google translations to French (the
quality is likely to differ for each language). A third possibility
would be that you just used Google translate or something similar
yourself by copy/paste, I guess.
easily share translations, and especially have a common and
consistently used glossary for DHIS terms such as organisation unit
and data element.
have an easy way of identifying which parts have changed in the
original, so the translations can be updated.
A translator could work directly with DocBook, using and XML editor
like Serna, but then machine translation becomes more tricky. For PO
files, you can use a PO editor. They can be generated and re-inserted
into DocBook (though there are some minor issues). Launchpad also
supports the PO format. For raw text, you can use Google Docs or any
editor but the issue is then how to get the translated strings back
into the DocBook structure.
And throughout, the problem of changes in the original presents
itself. To my mind, most parts of the manual will quickly
stabilize.The alternative would be to almost completely decouple the
different languages, and just keep the chapter or section headings,
sort of like Wikipedia does for different languages.
Appreciate your input - for example on which of the considerations
above you find most important.
Mailing list: https://launchpad.net/~dhis2-devs