Sorry i missed this one i my inbox But Knut is on point.
How it works in the most basic sense (if i remember correctly) is that if the modules action[1] returns a description that one is used. This is the case for installed apps, the description is pulled from the description field in the manifest.
For “default” modules, the modules action does not return a description, if there is no description a lookup is done against the i18n endpoint for that module name where “intro_” is prepended to the name. If the value is not equal the key then then that is used for the description.
intro_dhis-web-caseentry: “Register beneficiaries, enter data for encounters and events and view reports.”
···
[1] /dhis-web-commons/menu/getModules.action
Regards,
Mark
On Thu, Jun 18, 2015 at 1:11 AM, Alan Hill ahill@2paths.com wrote:
Hi Morten
OK…thanks for the information.
Regards
Alan
On Tue, Jun 16, 2015 at 7:40 PM, Morten Olav Hansen mortenoh@gmail.com wrote:
Hi,
As far as I know, this is not currently supported, it might be something to look into in the future though.
Mark: how is this handled for internal apps in the menu?
–
Morten
On Tue, Jun 16, 2015 at 10:12 PM, Alan Hill ahill@2paths.com wrote:
I have been trying to internationalize the name/description fields in our DHIS2 app manifest.webapp file.