Unicode encoding problems in the agent frontend
Hi folks, I wanted to give OTRS 4.0 a spin, so I made a backup of my test instance and checkout the the rel-4.0 branch and followed the update instructions. I was using 3.3 previously where I had not the followig problems. I'm running OTRS behind fastcgiwrap behind nginx, which also is working flawless. My problem is, that the generated HTML garbles up all the unicode characters as you can see in this screenshot (for Example under 'Ticket-Einstellungen', 'Agenten-Benachrichtigungen): https://picdump.datenknoten.me/060e60cbb676db5500344e38c97dad5b0a83b1e5b2a56... This also includes customer correspondences. The Database is configured correctly I think: Name | Owner | Encoding | Collate | Ctype | Access privileges ------+-------+----------+-------------+-------------+------------------- otrs | otrs | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 | Is there anything else I may have missed? greetings Tim
Please check if the translation files (Kernel/Language/*.pm) are stored with utf-8... - Renée On 23.11.2014 16:38, Tim Schumacher wrote:
Hi folks,
I wanted to give OTRS 4.0 a spin, so I made a backup of my test instance and checkout the the rel-4.0 branch and followed the update instructions. I was using 3.3 previously where I had not the followig problems. I'm running OTRS behind fastcgiwrap behind nginx, which also is working flawless.
My problem is, that the generated HTML garbles up all the unicode characters as you can see in this screenshot (for Example under 'Ticket-Einstellungen', 'Agenten-Benachrichtigungen): https://picdump.datenknoten.me/060e60cbb676db5500344e38c97dad5b0a83b1e5b2a56...
This also includes customer correspondences.
The Database is configured correctly I think:
Name | Owner | Encoding | Collate | Ctype | Access privileges ------+-------+----------+-------------+-------------+------------------- otrs | otrs | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 |
Is there anything else I may have missed?
greetings
Tim --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
Jup, it is. There are no modifications to the gut tree:
$ file de.pm
de.pm: Perl5 module source, UTF-8 Unicode text, with very long
lines
What i forgot to mention is that all content is garbled, also the customer emails. I looked into the database with psql and the content is correct.
The box is a Debian jessy.
Greetings and thanks for your time
Tim
Am 23. November 2014 23:00:26 MEZ, schrieb Renee B
Please check if the translation files (Kernel/Language/*.pm) are stored with utf-8...
- Renée
On 23.11.2014 16:38, Tim Schumacher wrote:
Hi folks,
I wanted to give OTRS 4.0 a spin, so I made a backup of my test instance and checkout the the rel-4.0 branch and followed the update instructions. I was using 3.3 previously where I had not the followig problems. I'm running OTRS behind fastcgiwrap behind nginx, which also is working flawless.
My problem is, that the generated HTML garbles up all the unicode characters as you can see in this screenshot (for Example under 'Ticket-Einstellungen', 'Agenten-Benachrichtigungen):
https://picdump.datenknoten.me/060e60cbb676db5500344e38c97dad5b0a83b1e5b2a56...
This also includes customer correspondences.
The Database is configured correctly I think:
Name | Owner | Encoding | Collate | Ctype | Access
privileges
------+-------+----------+-------------+-------------+-------------------
otrs | otrs | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 |
Is there anything else I may have missed?
greetings
Tim --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
On 23.11.2014 23:14, Tim Schumacher wrote:
Jup, it is. There are no modifications to the gut tree:
$ file de.pm de.pm: Perl5 module source, UTF-8 Unicode text, with very long lines
What i forgot to mention is that all content is garbled, also the customer emails. I looked into the database with psql and the content is correct.
Then check the HTTP-Headers. Is there any charset set? Check the browser - what charset is used to show the content... - Renée -- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
At Sun, 23 Nov 2014 23:29:13 +0100, Renee B wrote:
On 23.11.2014 23:14, Tim Schumacher wrote:
Jup, it is. There are no modifications to the gut tree:
$ file de.pm de.pm: Perl5 module source, UTF-8 Unicode text, with very long lines
What i forgot to mention is that all content is garbled, also the customer emails. I looked into the database with psql and the content is correct.
Then check the HTTP-Headers. Is there any charset set? Check the browser - what charset is used to show the content...
Content-Type: text/html; charset=utf-8;
<meta http-equiv="Content-type" content="text/html;charset=utf-8" />
And firefox says unicode. You can try for yourself on
https://support.datenknoten.me/
Whats realy strange, when I run /opt/otrs/bin/cgi-bin/index.pl from
the shell, the unicode characters are correct. When I run
/opt/otrs/bin/fcgi-bin/index.pl they are garbled up like in the web
interface.
My nginx config looks like this:
location ~ ^/otrs/(.*\.pl)(/.*)?$ {
gzip off;
# Enter your fcgiwrap socket here
fastcgi_pass unix:/var/run/fcgiwrap.socket;
fastcgi_index index.pl;
# Enter your OTRS cgi-bin path,
e.g.
Vielleicht liefert http://stackoverflow.com/questions/7285215/nginx-fastcgi-utf-8-encoding-outp... die Lösung -- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
At Tue, 25 Nov 2014 08:26:01 +0100, Renee B wrote:
Vielleicht liefert http://stackoverflow.com/questions/7285215/nginx-fastcgi-utf-8-encoding-outp... die Lösung
Thanks, figured it out! Thanks to your link I dumped the env to a file and then checked variable for variable[1] which was the culprit. If „FCGI_ROLE="RESPONDER"“ is set, all the umlauts are garbled. I then grepd the source for FCGI_ROLE and then discovered Layout.pm[2] and then comented the encoding stuff and now all the umlauts work. What should I do? Should I comment in the tickets that this change breaks stuff for me? greetings Tim [1] http://pastebin.geany.org/2HTNv/ [2] https://github.com/OTRS/otrs/blob/rel-4_0/Kernel/Output/HTML/Layout.pm#L1440
On 25.11.2014 09:22, Tim Schumacher wrote:
What should I do? Should I comment in the tickets that this change breaks stuff for me?
Yes, please do so. But provide some details: * OTRS version * Perl version * FCGI, CGI::Fast version ( "perl -MFCGI\ 999 -e 1" and "perl -MCGI::Fast\ 999 -e 1") * nginx version * nginx configuration - Renée -- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
participants (2)
-
Renee B -
Tim Schumacher