Hi all,
I’m looking at ways to support translation in a custom form (aggregate). I would like to be able to use the "built in" translation of data elements if possible, using IDs when designing the form and having a javascript function triggered by "dhis2.de.event.formReady" to put in the correct translations. I was thinking the formName, displayName or similar would be available in the dhis2 object, but I’m having difficult figuring out where.
Can any of the dev advice on where to read the translated names/formNames, if possible?
Does anyone else have any experience with something like this?
Thinking of it now, this might even be an idea for a general feature: just like you can add the data entry fields, totals and indicators when designing custom forms, there could be an option to add "name" label that would display the name/form name of an element, with translation when applicable.
I’m looking at ways to support translation in a custom form (aggregate). I would like to be able to use the “built in” translation of data elements if possible, using IDs when designing the form and having a javascript function triggered by “dhis2.de.event.formReady” to put in the correct translations. I was thinking the formName, displayName or similar would be available in the dhis2 object, but I’m having difficult figuring out where.
Can any of the dev advice on where to read the translated names/formNames, if possible?
Does anyone else have any experience with something like this?
Thinking of it now, this might even be an idea for a general feature: just like you can add the data entry fields, totals and indicators when designing custom forms, there could be an option to add “name” label that would display the name/form name of an element, with translation when applicable.
I’m looking at ways to support translation in a custom form (aggregate). I would like to be able to use the “built in” translation of data elements if possible, using IDs when designing the form and having a javascript function triggered by “dhis2.de.event.formReady” to put in the correct translations. I was thinking the formName, displayName or similar would be available in the dhis2 object, but I’m having difficult figuring out where.
Can any of the dev advice on where to read the translated names/formNames, if possible?
Does anyone else have any experience with something like this?
Thinking of it now, this might even be an idea for a general feature: just like you can add the data entry fields, totals and indicators when designing custom forms, there could be an option to add “name” label that would display the name/form name of an element, with translation when applicable.
On Mon, Feb 15, 2016 at 4:57 AM, Olav Poppe olav.poppe@me.com wrote:
Hi all,
I’m looking at ways to support translation in a custom form (aggregate). I would like to be able to use the “built in” translation of data elements if possible, using IDs when designing the form and having a javascript function triggered by “dhis2.de.event.formReady” to put in the correct translations. I was thinking the formName, displayName or similar would be available in the dhis2 object, but I’m having difficult figuring out where.
Can any of the dev advice on where to read the translated names/formNames, if possible?
Does anyone else have any experience with something like this?
Thinking of it now, this might even be an idea for a general feature: just like you can add the data entry fields, totals and indicators when designing custom forms, there could be an option to add “name” label that would display the name/form name of an element, with translation when applicable.
that sounds like a great idea. Something like a variable, e.g. ${.name} , which can be substituted based on the selected locale of the current user.
Feel free to write a blueprint.
You can load this from the API, which in 2.22 lets you use the “displayName” property of objects which are translated to the appropriate language.
My initial thinking was to see if the translated names were stored/cached somewhere and avoid API-calls for the sake of offline support (e.g. it would work even if the user went offline before a specific form was opened), but in most cases it should not be a problem.
Regards
Olav
···
On Mon, Feb 15, 2016 at 4:57 AM, Olav Poppe olav.poppe@me.com wrote:
Hi all,
I’m looking at ways to support translation in a custom form (aggregate). I would like to be able to use the “built in” translation of data elements if possible, using IDs when designing the form and having a javascript function triggered by “dhis2.de.event.formReady” to put in the correct translations. I was thinking the formName, displayName or similar would be available in the dhis2 object, but I’m having difficult figuring out where.
Can any of the dev advice on where to read the translated names/formNames, if possible?
Does anyone else have any experience with something like this?
Thinking of it now, this might even be an idea for a general feature: just like you can add the data entry fields, totals and indicators when designing custom forms, there could be an option to add “name” label that would display the name/form name of an element, with translation when applicable.
that sounds like a great idea. Something like a variable, e.g. ${.name} , which can be substituted based on the selected locale of the current user.
Feel free to write a blueprint.
You can load this from the API, which in 2.22 lets you use the “displayName” property of objects which are translated to the appropriate language.