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")
*
At Tue, 25 Nov 2014 08:26:01 +0100,
Renee B wrote:
>
> Vielleicht liefert
> http://stackoverflow.com/questions/7285215/nginx-fastcgi-utf-8-encoding-output-iso-8859-1-instead-of-utf8
> die Lösung
Thanks, figured it out! Thanks to your link I dumped the env to a file and
then checked variable for v
Vielleicht liefert
http://stackoverflow.com/questions/7285215/nginx-fastcgi-utf-8-encoding-output-iso-8859-1-instead-of-utf8
die Lösung
--
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
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
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
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
> instru
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 fla
