Hello list,
I have just installed RT 3.8.0 on our team’s server. Our browsers operate in
hungarian language, so as we open the main (login) page of RT, it gets to us
in hungarian. The hungarian i18n file is encoded in UTF-8, the server also
sends the Content-Type header with encoding=utf-8, but the page itself is
iso-encoded. How can this be? Is this an RT, perl or apache problem?
Thanks in advance.
Best,
Gergely Polonkai
Hello list,
I have just installed RT 3.8.0 on our team’s server. Our browsers operate in
hungarian language, so as we open the main (login) page of RT, it gets to us
in hungarian. The hungarian i18n file is encoded in UTF-8, the server also
sends the Content-Type header with encoding=utf-8, but the page itself is
iso-encoded. How can this be? Is this an RT, perl or apache problem?
Do you have a “AddDefaultCharset UTF-8” in your apache vhost
configuration, it’s needed.
I do, and the server sends the correct encoding in the headers. Only the
encoding of the page itself is wrong.
I forgot to mention that RT is running under FastCGI, if this means
anything.2008/10/8 Emmanuel Lacour elacour@easter-eggs.com
On Wed, Oct 08, 2008 at 04:38:58PM +0200, Gergely Polonkai wrote:
Hello list,
I have just installed RT 3.8.0 on our team’s server. Our browsers operate
in
hungarian language, so as we open the main (login) page of RT, it gets to
us
in hungarian. The hungarian i18n file is encoded in UTF-8, the server
also
sends the Content-Type header with encoding=utf-8, but the page itself is
iso-encoded. How can this be? Is this an RT, perl or apache problem?Do you have a “AddDefaultCharset UTF-8” in your apache vhost
configuration, it’s needed.
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
3.8.1 has a change that may fix this. It’s really bad idea to use
3.8.0 for a new installation when 3.8.1 available.On Wed, Oct 8, 2008 at 6:38 PM, Gergely Polonkai polesz@w00d5t0ck.info wrote:
Hello list,
I have just installed RT 3.8.0 on our team’s server. Our browsers operate in
hungarian language, so as we open the main (login) page of RT, it gets to us
in hungarian. The hungarian i18n file is encoded in UTF-8, the server also
sends the Content-Type header with encoding=utf-8, but the page itself is
iso-encoded. How can this be? Is this an RT, perl or apache problem?Thanks in advance.
Best,
Gergely Polonkai
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Best regards, Ruslan.
I have tried some things, still not succeeding in my task. However, I
have realized that my browser sends a request-header:
Accept-Charset: ISO-8859-2,utf-8;q=0.7,*;0=0.7
Does RT process these kind of request lines, or ignores them? If it
processes, may this cause that even if apache sends out the utf-8
charset, perl and rt generates an iso-8859-2 html?
signature.asc (197 Bytes)
smime.p7s (3.21 KB)