My organisationunits are not well stored. When I type a name with an accent or cedil DHIS stores on database something else. Example:
The province “Província de Cabo Delgado” (there is an acute accent on the first I) is stored like “ProvÃncia de Cabo Delgado” on the database and it is shown with this evil name. And check on the logs I see that bad name again.
So I have changed mannually on the database to correct it. Then DHIS renders it on the form correctly.
To make sure that everything is UTF-8 I made these changes:
Set LANG bash environment variable to LANG=“en_US.UTF-8”
Modify JAVA_OPTS to include -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8
Check dhis2 database:
postgres=# \l
List of databases
There was some issues with this, but it should be fixed now (it was fixed a couple of days ago)
···
–
Morten
On Sat, Dec 1, 2012 at 4:28 PM, Orvalho Augusto orvaquim@gmail.com wrote:
My organisationunits are not well stored. When I type a name with an accent or cedil DHIS stores on database something else. Example:
The province “Província de Cabo Delgado” (there is an acute accent on the first I) is stored like “ProvÃncia de Cabo Delgado” on the database and it is shown with this evil name. And check on the logs I see that bad name again.
So I have changed mannually on the database to correct it. Then DHIS renders it on the form correctly.
To make sure that everything is UTF-8 I made these changes:
Set LANG bash environment variable to LANG=“en_US.UTF-8”
Modify JAVA_OPTS to include -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8
Check dhis2 database:
postgres=# \l
List of databases
Yes this new war file has some angelic actions.
Caveman
···
–
Morten
On Sat, Dec 1, 2012 at 4:28 PM, Orvalho Augusto orvaquim@gmail.com wrote:
My organisationunits are not well stored. When I type a name with an accent or cedil DHIS stores on database something else. Example:
The province “Província de Cabo Delgado” (there is an acute accent on the first I) is stored like “ProvÃncia de Cabo Delgado” on the database and it is shown with this evil name. And check on the logs I see that bad name again.
So I have changed mannually on the database to correct it. Then DHIS renders it on the form correctly.
To make sure that everything is UTF-8 I made these changes:
Set LANG bash environment variable to LANG=“en_US.UTF-8”
Modify JAVA_OPTS to include -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8
Check dhis2 database:
postgres=# \l
List of databases
The war file on DHIS official site is dated Dec 4. Is that war file include accent corrections?
It is because on dataset reports when I choose parent organization unit the numbers are not summed. So I am wondering if it is a bug already corrected.
Thank you
Caveman
···
–
Morten
On Sat, Dec 1, 2012 at 4:28 PM, Orvalho Augusto orvaquim@gmail.com wrote:
My organisationunits are not well stored. When I type a name with an accent or cedil DHIS stores on database something else. Example:
The province “Província de Cabo Delgado” (there is an acute accent on the first I) is stored like “ProvÃncia de Cabo Delgado” on the database and it is shown with this evil name. And check on the logs I see that bad name again.
So I have changed mannually on the database to correct it. Then DHIS renders it on the form correctly.
To make sure that everything is UTF-8 I made these changes:
Set LANG bash environment variable to LANG=“en_US.UTF-8”
Modify JAVA_OPTS to include -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8
Check dhis2 database:
postgres=# \l
List of databases
You can also subscribe to email notifications for that release branch on the link above.
Ola
···
–
Morten
On Sat, Dec 1, 2012 at 4:28 PM, Orvalho Augusto orvaquim@gmail.com wrote:
My organisationunits are not well stored. When I type a name with an accent or cedil DHIS stores on database something else. Example:
The province “Província de Cabo Delgado” (there is an acute accent on the first I) is stored like “ProvÃncia de Cabo Delgado” on the database and it is shown with this evil name. And check on the logs I see that bad name again.
So I have changed mannually on the database to correct it. Then DHIS renders it on the form correctly.
To make sure that everything is UTF-8 I made these changes:
Set LANG bash environment variable to LANG=“en_US.UTF-8”
Modify JAVA_OPTS to include -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8
Check dhis2 database:
postgres=# \l
List of databases