On Tue, Aug 07, 2007 at 07:51:35PM +0200, Tobias Kremer wrote:
> Am 07.08.2007 um 18:40 schrieb Bill Moseley:
> >On Tue, Aug 07, 2007 at 06:30:46PM +0200, Tobias Kremer wrote:
> >>Yes, that's exactly why I just don't understand the problem. The rest
> >>of my templates,
> >>which are all utf-8 encoded, are displayed correctly though. What
> >>UNICODE option do you mean?
> >>I couldn't find it in Template::Manual::Config.
> >
> >Look at the source of Template::Provider. If set it assumes the text
> >of the template is utf8 and decodes it.
> >But if your problem is displaying variables (not templates) that are
> >utf8 then sounds like something else.
>
> Exactly. utf8-encoded text in the templates is displayed correctly.
> Other
> stuff coming in from the stash that is utf8-encoded works perfectly,
> too.
Ah. So you are failing to decode the templates on input, so failing
to encode on output make it look fine. Perhaps.
> >Are you using the Unicode::Encoding plugin in your Catalyst
> >application?
>
> No. This happens even with no plugins loaded at all. You can try it
> out just by adding the following line to one of your controllers
> and putting [% monthnames %] in the TT template:
>
> $c->stash->{'monthnames'} = join ",", @{ DateTime::Locale->load('de')-
> >month_names };
I did, and *without out* Unicode::Encoding I get the broke display
(the little question marks in Firefox).
I use both the plugin and set TT to decode my templates on input. TT
will do that automatically if you have Byte Order Mark on your
templates, too, IIRC.
--
Bill Moseley
[EMAIL PROTECTED]
