I also have this problem. You could set the codepage of the httpd to iso5589-1 and the de_DE locale will be displayed correctly in the webinterface but writing umlauts to the database wont work, as they are expected in utf8 as far as i can see.
The problem in my opinion is the language file as it has the iso5589-1 in the header, but i am not sure. I would be very interessted in a solution as my colleagues really REALLY like german interfaces...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it is a problem of the translation. The one is bundled with the original source has many ugly translations. I append a corrected version.
It would be fine to substitute the original files. The problem i discovered has something to do with the encoding of that file!
On my linux laptop using poedit i recognized, the character encodig of the original po-file has been iso8895-1.
After change to UTF-8 and "save" i've got the right utf8 phpipam.mo ( binary version ).
So this is only half the truth. In this forum i found the final hint:
I can confirm this on Windows Server 2012 r2
I also have this problem. You could set the codepage of the httpd to iso5589-1 and the de_DE locale will be displayed correctly in the webinterface but writing umlauts to the database wont work, as they are expected in utf8 as far as i can see.
The problem in my opinion is the language file as it has the iso5589-1 in the header, but i am not sure. I would be very interessted in a solution as my colleagues really REALLY like german interfaces...
confirmed, too. Centos 7. This is a "Blocker" for us concerning update ....
Last edit: Peter Schultz 2016-10-07
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
We are on CentOS7 aswell with the same bug.
I checked on latest development release and it is ok. There was a bug with encoding naming.
Try this in SQL:
And rename functions/locale/de_DE/ to functions/locale/de_DE.UTF8/.
a Colleague of mine digged a little deeper (Thanks Uwe ...):
after some extended investigation i found the place the translated strings come from, the phpipam.po file:
/var/www/html/phpipam/functions/locale/de_DE/LC_MESSAGES/phpipam.po.
I think it is a problem of the translation. The one is bundled with the original source has many ugly translations. I append a corrected version.
It would be fine to substitute the original files. The problem i discovered has something to do with the encoding of that file!
On my linux laptop using poedit i recognized, the character encodig of the original po-file has been iso8895-1.
After change to UTF-8 and "save" i've got the right utf8 phpipam.mo ( binary version ).
So this is only half the truth. In this forum i found the final hint:
http://php.net/manual/de/function.bind-textdomain-codeset.php
After changing the following files in /var/www/html/phpipam:
./app/login/index.php
./api/v1/functions/functions.php
./functions/classes/class.User.php
++ bind_textdomain_codeset("phpipam", "utf-8");
and restart httpd, the characters look pretty (nice german umlauts).
So please change this code fragment in the original source code!
I'll wait to upgrade my production environment.