Hello,
if there is the german letter ‘�’ in a message , I get an error message
like this : (I use RT Version 3.0.4 with Perl 5.8). Is this bug already
fixed in an new version?
System error
error: Internal Error () on 'mit freundlichem Gruç at
/usr/share/perl5/Text/Quoted.pm line 187.
Hello,
if there is the german letter ‘�’ in a message , I get an error message
like this : (I use RT Version 3.0.4 with Perl 5.8). Is this bug already
fixed in an new version?
System error
error: Internal Error () on 'mit freundlichem Gruç at
/usr/share/perl5/Text/Quoted.pm line 187.
Hello Jesse,
many thanks, it works now. I do not get the error anymore but german
letters are partly not displayed correctly like this:
Möglichkeit ,mit freundlichem Gru�� würde über diesen Anschlu��
greetings
Markus
I’m seing the same problem here: I can receive German Umlaut characters
by E-Mail, but I cannot store Umlaut characters in comments or replies
when I enter them via the web form. Any suggestions?
Thanks! Apparently this fixes the bug for German Umlauts - replying and
commenting on both incoming mail and web-user generated tickets are
handled correctly. I will test it with a few more charsets today.
My RT now has some odd behaviour with web-user generated tickets, but
that could be a local configuration issue. I will get back to you with that.
Thanks! Apparently this fixes the bug for German Umlauts - replying and
commenting on both incoming mail and web-user generated tickets are
handled correctly. I will test it with a few more charsets today.
My RT now has some odd behaviour with web-user generated tickets, but
that could be a local configuration issue. I will get back to you with
that.
Entwarnung.
It appears that the bug is completely fixed on my RT installation with
RT 3.0.7_01, Apache 1.3.26 (with Debian backports), Mysql 3.23.49 (with
Debian backports) .
Thanks again. I will deploy RT for an international audience now. Let’s
see how it copes with Chinese etc.
I’ve realized that when you merge more tickets into one then
in the transaction history is recorded only the first merge.
It is due database inconsistence of the Links table caused
by loosing old Id’s of merged tickets. Simple ungly patch is:
I’ve realized that when you merge more tickets into one then
in the transaction history is recorded only the first merge.
It is due database inconsistence of the Links table caused
by loosing old Id’s of merged tickets. Simple ungly patch is:
I’d be happy to apply this patch to the RT2 cvs, but with a bit more
source code context, so I know it’s actually going in the right place
(as the line numbers may be off a bit).