I realise that you're probably not using template toolkit, but on a
separate but related note:
For those on the list using Template Toolkit, if your templates contain
UTF8, you need to prefix them with a UTF8 BOM for them to be recognised
as UTF8, otherwise TT gets really confused.
See here for m
To: modperl@perl.apache.org
Sent: Wednesday, April 4, 2007 7:20:01 PM
Subject: Re: UTF-8 encoding problems under Apache 2 with mod_perl 2.
>
>We also do everything (not source code, which is in ISO-8859-1, only content)
>in UTF-8 where I >work, and we support many different langua
>
>We also do everything (not source code, which is in ISO-8859-1, only content)
>in UTF-8 where I >work, and we support many different languages.
Jeff,how did you do it by using utf-8 for everything?can you give a rough
description?Thanks.
--
mailto: [EMAIL PROTECTED]
http://home.arcor.de
Jeff
- Original Message
From: Tamer Embaby <[EMAIL PROTECTED]>
To: modperl@perl.apache.org
Sent: Wednesday, April 4, 2007 1:59:37 AM
Subject: UTF-8 encoding problems under Apache 2 with mod_perl 2.
All,
I have character encoding problem with my environment:
$ uname -a
SunOS v
On 4/4/07, Tamer Embaby <[EMAIL PROTECTED]> wrote:
Server: Apache/2.0.58 (Unix) mod_perl/2.0.3 Perl/v5.8.4
You probably want a later Perl than that. Many unicode bugs have been
fixed since then.
I have a hunch that it's something to do with the Locale passed to the
mod_perl that I should be
All,
I have character encoding problem with my environment:
$ uname -a
SunOS vulcano 5.10 Generic_118844-26 i86pc i386 i86pc
Server: Apache/2.0.58 (Unix) mod_perl/2.0.3 Perl/v5.8.4
I'm hosting commercial application using mod_perl, the site we are
dealing with has Arabic character so I changed