" trying to work on data element translation for the SIScom database.
[11:29:24 IST] Randy Wilson: can't seem to find any documentation on
it. I see the translation table. and have filled it with dataelement
names in Kinyarwanda. For the moment we are using the 'sw' locale
code, since I can't find where to add new locales for 'kn' kinyarwanda
for example.
[13:39:49 IST] Randy Wilson: got the translations working finally...
but still don't know where to add new locales."
I think the properties files for a specific language must exist first right?
In this case, the code should be rw_RW. This is what we are using for
the application and MyDatamart files.
Am sure Lars can provide the definitive answer. In the meantime, I
will go ahead and commit at least one of the rw_RW files and see if
this will help to "seed" this locale.
···
On Tue, Apr 17, 2012 at 1:54 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Can anybody help Randy with this locale issue?
" trying to work on data element translation for the SIScom database.
[11:29:24 IST] Randy Wilson: can't seem to find any documentation on
it. I see the translation table. and have filled it with dataelement
names in Kinyarwanda. For the moment we are using the 'sw' locale
code, since I can't find where to add new locales for 'kn' kinyarwanda
for example.
[13:39:49 IST] Randy Wilson: got the translations working finally...
but still don't know where to add new locales."
I think we are talking about database translations, not ui.. Its
hardcoded at the moment, I will commit this one and backport as a
quick fix..
···
On Tue, Apr 17, 2012 at 3:04 PM, Jason Pickering <jason.p.pickering@gmail.com> wrote:
I think the properties files for a specific language must exist first right?
In this case, the code should be rw_RW. This is what we are using for
the application and MyDatamart files.
Am sure Lars can provide the definitive answer. In the meantime, I
will go ahead and commit at least one of the rw_RW files and see if
this will help to "seed" this locale.
On Tue, Apr 17, 2012 at 1:54 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Can anybody help Randy with this locale issue?
" trying to work on data element translation for the SIScom database.
[11:29:24 IST] Randy Wilson: can't seem to find any documentation on
it. I see the translation table. and have filled it with dataelement
names in Kinyarwanda. For the moment we are using the 'sw' locale
code, since I can't find where to add new locales for 'kn' kinyarwanda
for example.
[13:39:49 IST] Randy Wilson: got the translations working finally...
but still don't know where to add new locales."
While you are at it, can you get rid of the translations which do not
exist, such as Japanese??
···
2012/4/17 Lars Helge Øverland <larshelge@gmail.com>:
I think we are talking about database translations, not ui.. Its
hardcoded at the moment, I will commit this one and backport as a
quick fix..
On Tue, Apr 17, 2012 at 3:04 PM, Jason Pickering > <jason.p.pickering@gmail.com> wrote:
I think the properties files for a specific language must exist first right?
In this case, the code should be rw_RW. This is what we are using for
the application and MyDatamart files.
Am sure Lars can provide the definitive answer. In the meantime, I
will go ahead and commit at least one of the rw_RW files and see if
this will help to "seed" this locale.
On Tue, Apr 17, 2012 at 1:54 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Can anybody help Randy with this locale issue?
" trying to work on data element translation for the SIScom database.
[11:29:24 IST] Randy Wilson: can't seem to find any documentation on
it. I see the translation table. and have filled it with dataelement
names in Kinyarwanda. For the moment we are using the 'sw' locale
code, since I can't find where to add new locales for 'kn' kinyarwanda
for example.
[13:39:49 IST] Randy Wilson: got the translations working finally...
but still don't know where to add new locales."
Thanks for the quick reply Lars. Yes we are talking about the data element and other object translations... not the UI. It would be good to push the locales into a table for future versions.
Now that we've convinced the system that Swahili "sw" is really Kinyarwanda and I've added 3 rows for each data element into the translations table (objectproperties: name, shortName and description).
"DataElement";1318;"sw";"name";"Umubare w'ababyariye mu rugo"
"DataElement";1318;"sw";"shortName";"Ababyeyi_wa_biyare"
"DataElement";1319;"sw";"description";"AccouchDomicileRefere"
It seems to work, but we can't seem to sort out the cache issue scientifically. As I mentioned to Bob, there is some combination of deleting local cache, logging out, deleting system cache (using the data administration option) that sometimes works, but not always. I suppose most users won't be changing languages on the fly as we do, but it is difficult to demonstrate the capability.
Can we get a "clear cache for dummies" menu option under help that goes to all the right places?
Randy
···
-----Original Message-----
From: dhis2-users-bounces+rwilson=msh.org@lists.launchpad.net [mailto:dhis2-users-bounces+rwilson=msh.org@lists.launchpad.net] On Behalf Of Lars Helge Øverland
Sent: Tuesday, April 17, 2012 3:26 PM
To: Jason Pickering
Cc: dhis2-users
Subject: Re: [Dhis2-users] localization question
I think we are talking about database translations, not ui.. Its
hardcoded at the moment, I will commit this one and backport as a
quick fix..
On Tue, Apr 17, 2012 at 3:04 PM, Jason Pickering <jason.p.pickering@gmail.com> wrote:
I think the properties files for a specific language must exist first right?
In this case, the code should be rw_RW. This is what we are using for
the application and MyDatamart files.
Am sure Lars can provide the definitive answer. In the meantime, I
will go ahead and commit at least one of the rw_RW files and see if
this will help to "seed" this locale.
On Tue, Apr 17, 2012 at 1:54 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Can anybody help Randy with this locale issue?
" trying to work on data element translation for the SIScom database.
[11:29:24 IST] Randy Wilson: can't seem to find any documentation on
it. I see the translation table. and have filled it with dataelement
names in Kinyarwanda. For the moment we are using the 'sw' locale
code, since I can't find where to add new locales for 'kn' kinyarwanda
for example.
[13:39:49 IST] Randy Wilson: got the translations working finally...
but still don't know where to add new locales."
I have added rw / Kinyarwanda db language to trunk and 2.7.
···
2012/4/17 Jason Pickering <jason.p.pickering@gmail.com>:
While you are at it, can you get rid of the translations which do not
exist, such as Japanese??
I have removed Japanese. But we have went for a simple solution here
with no GUI for adding languages, detecting new ones etc. Just to keep
it simple. It is only one line in beans.xml in dhis-service-core to
change and we have a finite number of languages to support.
I recommend working with the user interface here.. just click the blue
globe-like icon next to each element in lists. I have tested on
tanzania server where they have english and swahili and it works fine
there.
If you use the database you will have to clear the application cache
in data admin module, yes. Nothing else should be required.
Removing the "default" english translations from the translation table
is recommended (if they are there). They are not in use anymore.
Lars
···
On Tue, Apr 17, 2012 at 3:37 PM, Wilson,Randy <rwilson@msh.org> wrote:
Thanks for the quick reply Lars. Yes we are talking about the data element and other object translations... not the UI. It would be good to push the locales into a table for future versions.
Now that we've convinced the system that Swahili "sw" is really Kinyarwanda and I've added 3 rows for each data element into the translations table (objectproperties: name, shortName and description).
"DataElement";1318;"sw";"name";"Umubare w'ababyariye mu rugo"
"DataElement";1318;"sw";"shortName";"Ababyeyi_wa_biyare"
"DataElement";1319;"sw";"description";"AccouchDomicileRefere"
It seems to work, but we can't seem to sort out the cache issue scientifically. As I mentioned to Bob, there is some combination of deleting local cache, logging out, deleting system cache (using the data administration option) that sometimes works, but not always. I suppose most users won't be changing languages on the fly as we do, but it is difficult to demonstrate the capability.
Can we get a "clear cache for dummies" menu option under help that goes to all the right places?
I added the translation i18n properties for commons from the
translation server. There is nothing there at the moment, but as the
translations are added, I will try and keep them in sync.
I also added the translations for MyDatamart which are present.
Regards,
Jason
···
2012/4/17 Lars Helge Øverland <larshelge@gmail.com>:
I have added rw / Kinyarwanda db language to trunk and 2.7.
2012/4/17 Jason Pickering <jason.p.pickering@gmail.com>:
While you are at it, can you get rid of the translations which do not
exist, such as Japanese??
I have removed Japanese. But we have went for a simple solution here
with no GUI for adding languages, detecting new ones etc. Just to keep
it simple. It is only one line in beans.xml in dhis-service-core to
change and we have a finite number of languages to support.