On Dec 12, 2007 10:08 AM, Jon <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm having some problems with utf-8 and was hoping someone could point me
> in the right direction. I've two machines and I just copied (scp:ed) from
> the one I've been playing around with to my other and then all my umlaut
> characters, when being inserted to the template by perl, like
> $c->stash->{umlaut} = 'ö' or when fetching data from the database containing
> ö. The ö itself is displayed correctly but all ö:s in the template gets
> garbled. If I don't do anything ö-related in the code the templates looks
> just fine, including their own ö:s.
>
> The thing that really confuse me is that it works fine on the machine I
> copied it all from. It's two different debian versions, stable on the
> non-working and unstable on the working. I've got the same catalyst packages
> though and both have the same locales installed. I've also tried the same
> data source on the broken I'm using on the working and it's giving the same
> result.
>
> I've been really careful trying to have the utf-8 work so I:
> In V::TT: ENCODING => 'UTF-8'
>
> in M::DB
> mysql_enable_utf8 => 1,
> on_connect_do => [
> "SET NAMES 'utf8'",
> "SET CHARACTER SET 'utf8'",
> ],
> in MyApp.pm:
> use Catalyst qw/
> ..
> Unicode
> /;
> and I've tried with and without
> use encoding 'utf8';
>
>
> All my modules are utf-8 encoded and use utf8 if they have strings with
> umlauts in them, all my templates are utf-8, the mysql-data is too and the
> response headers from apache says "Content-Typetext/html; charset=utf-8".
>
> Anyone got a clue what could be the problem?
>
> Thanks
> Jon
>
Is it possible that the broken machine has an old TT version that doesn't
support the ENCODING => 'UTF-8' parameter?
--
Jonas
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
Dev site: http://dev.catalyst.perl.org/
