- Renée
--
Perl / OTRS development: http://perl-services.de
OTRS AddOn repository: http://opar.perl-services.de
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/060e60cbb676db5500344e38c97dad5b0a83b1e5b2a5656dbf509e999e990727_orig
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
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
---------------------------------------------------------------------
--
Perl / OTRS development: http://perl-services.de
OTRS AddOn repository: http://opar.perl-services.de
---------------------------------------------------------------------
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
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
---------------------------------------------------------------------