dhis2-devs team mailing list archive

[Sam Kasozi <kasozis@xxxxxxxxx>]

No, we had not looked at the new translation app. We would not mind trying
it out as well especially if it will be easier to use.

How can we access it?


P.s Attached is the template we had developed, hoping to use it to maintain
a translation record as well.

regards,

​
 Object Translation Template
<https://docs.google.com/spreadsheets/d/1UxYERRwdUFj5Ie3ytXWJzNiRRTlnkYmuxJbHBJfMkZw/edit?usp=drive_web>
​


Sam Kasozi
+256 788-993-565
Skype: sam.kasoziug

On Thu, Jan 19, 2017 at 10:49 AM, Jason Pickering <
jason.p.pickering@xxxxxxxxx> wrote:

> Great.  Thanks.  Will let you know when we have something ready to test.
>
> Did you have a look at the new translation app?  It's only available on
> the DEV site but I think it will help with the Metadata translation.
>
> Regards,
> Jason
>
> On Thu, Jan 19, 2017, 07:29 Sam Kasozi <kasozis@xxxxxxxxx> wrote:
>
>> Hi Jason,
>>
>> Find attached the translated DHIS2 Dari (Afghanistan Persian) files for
>> upload to the DHIS2. It is the first draft that will be fine tuned as the
>> end users test the system. The Pushto translation will follow hopefully
>> within a month.
>>
>>
>> And on another note, using the DHIS2 translation manual, we have been
>> working on a translation template for the metadata. Unfortunately the
>> CREATE statement below has failed to run in 2.25. Can you please help to
>> verify if something has changed that should also be reflected in the
>> manual.
>>
>> curl -X POST -u admin:Pa$$w0rd "http://localhost:8282/dhis/
>> api/translations/" -H "Content-Type: application/json"
>> -d'{"id":"U5QzK3jiuKF", "objectId":"iJP7k1NOjJq",
>> "className":"DataElement", "locale":"fa", "property":"name", "value":"demo
>> name translation"}'
>>
>> I am attaching the error file as well as an xml of the data element in
>> question.
>>
>> Regards,
>> Sam.
>>
>>
>> Sam Kasozi
>> +256 788-993-565
>> Skype: sam.kasoziug
>>
>> On Wed, Nov 9, 2016 at 12:31 PM, Jason Pickering <
>> jason.p.pickering@xxxxxxxxx> wrote:
>>
>> Hi Sam,
>> We need to do some setup on our side first. Those languages are for the
>> user interface of the translation server, not the actual translation
>> language.
>>
>> I have now enabled translation for Dari Persian (language code = prs) and
>> Pashto ( language code = ps) for the core translations.
>>
>> There are many others which need to be translated, but I would suggest
>> that you start with the "dhis-service-core" folder, and then we can go from
>> there.
>>
>> Once you finish that, please get in touch with my via direct email, as I
>> will need to sync these with the source code.
>>
>> Translation files can be downloaded for offline translation, using a tool
>> like "POEdit". You can get the translation template from
>> https://translate.dhis2.org/export/?path=/prs/dhis2-
>> translations/dhis-service-core/dhis-service-core-prs.po for instance.
>>
>> If you have any other problems, let us know.
>>
>> Also, thanks for pointing out the manual is out of date. We will try and
>> get it updated.
>>
>> Regards,
>> Jason
>>
>>
>>
>> On Wed, Nov 9, 2016 at 10:07 AM, Sam Kasozi <kasozis@xxxxxxxxx> wrote:
>>
>> Hi Jason,
>>
>> We would like to work on the translation for 2 languages: Dari and Pashto
>> in the DHIS 2. The translation guide in the implementer's manual provides
>> some instructions that are slightly different from the current translation
>> server user interface. I have a couple of questions.
>>
>> - Do we have an updated guide?
>> - Do you need to setup the project first before we can do anything (Under
>> settings -> Translation, -> Alternative source language, I see Pashto-ps
>> and not Dari)
>> - Then also does it have a provision for downloading a translation
>> template which can be populated and used to update the server afterward?
>>
>> regards,
>>
>>
>> Sam Kasozi
>> +256 788-993-565
>> Skype: sam.kasoziug
>>
>>
>>
>>
>> --
>> Jason P. Pickering
>> email: jason.p.pickering@xxxxxxxxx
>> tel:+46764147049 <+46%2076%20414%2070%2049>
>>
>>
>>