We are very pleased to announce that our new translation platform, provided by Transifex, is now available to all.
A quick guide for getting access to the platform, with answers to some basic questions, is available here: Home - DHIS2 Documentation
Some key points:
The platform has been set up to support translations in all supported versions of DHIS2.
Translating a string in one version, will automatically fill-in empty translations of the same string in other versions and in other apps.
New and updated translations are pushed as changes to the DHIS2 source code on a nightly basis! The development team have to accept the changes into the code, but in general translations should be available in development builds within a few days.
We hope that with the new platform and processes in place, we can provide improved support for localisation of DHIS2.
We will continue to make improvements, as necessary, and welcome your feedback.
Great news! When/how would a translated doc will be published on the website? We did some work on the French part and would probably extend it to the last version if this can be useful to other (ie published).
Currently we only support French for the documentation. They are also maintained on the transifex platform, as you know.
The (localised) documentation is also built nightly and published to our documentation server. We have not set up links from our documentation page as I am awaiting reviews from a group assigned from the university. I’m sorry this has taken some time; we really appreciate the work Bluesquare put into the “End User Manual” translations!
the unofficial French translations can be viewed by replacing the /en/ with /fr/ in the URL
I’ll push on our side to make them official!
P.S. We have split app translations and doc translations into two separate groups; so translators can apply to contribute to either Apps OR Documents OR Both.
Like i have data entered in my dhis2 instance but i need it to be sent automatically to another instance. Like all data values coming from the data elements being sent to another instance having the same data elements.
I see that now I am only able to suggest translations, no longer able to directly translate. Have you lately restrict this?
Plus, what is the policy for the suggestions? Do you routinely check them? Is there someone from the core team validating them or rather is it based on the number of votes the suggestion has?
Sorry, I see now that I can only make changes in the app-properties–master, which make sense with your directions. Still the question whether in which cases should we “Change” and in which should we “Suggest” and also the procedure that the latest follows.
We have not intentionally restricted translations, but once they are accepted by someone with Review privileges (status == Reviewed) then they can no longer be edited by people with Translator privileges.
When we migrated from the previous platform, we set a large percentage of the strings to Reviewed, under the assumption that they were already “correct”. However, that assumption doesn’t hold in many cases.
That means we would definitely welcome change suggestions.
We want to build up teams of Reviewers for the various languages, and it is the role of the reviewers to check both new translations, and suggestions.
If members of the community would like to be considered as Reviewers for a particular language, they are welcome to contact us at firstname.lastname@example.org.As supporting information we are interested in your role in the community, and relevant experience.
Lastly, Although we do strongly prefer people to translate the master resources (as it simplifies the process and serves the larger community better) we are not intentionally restricting translations on any versions; we value all and any contributions from the community. If someone wants to translate an app in 2.31 only, for example, we are still very grateful!
We would ideally like to get all strings to Reviewed status, and only pull reviewed strings into the code. However, to begin with we see getting translations in as the priority; therefore all translated strings are pulled into the code.
Great to know @phil. Might work for a language team with many members. For smaller groups might be tricky. Not sure if it makes sense if I got promoted temporarily then I approved my own translation for example. But can’t always wait until the team is built, can we?