I believe, i found the a way to handle the encoding problems
* create project with catalyst.pl MyApp
* setup your editor to use UTF8 as *default encoding* (i am using
Eclipse with the EPIC plugin. In Eclipse you can set the project
default encoding)
* optionally use utf8; in the Perl file headers (
On Sat, Sep 08, 2007 at 08:24:51PM +0200, Daniel McBrearty wrote:
> i don't know if this helps ... i had to dig around my code to find it,
> but I have this at the top of every template (actually at the top on
> an included template that they all use ...
>
> [% USE encoding 'utf-8' %]
>
> IIRC th
i don't know if this helps ... i had to dig around my code to find it,
but I have this at the top of every template (actually at the top on
an included template that they all use ...
[% USE encoding 'utf-8' %]
IIRC this ensures that the correct headers are sent out before the
html. you can check
On 9/7/07, Matt Lawrence <[EMAIL PROTECTED]> wrote:
> AFAIK, single-byte-width \xxx escapes are always treated as bytes, not
> as characters. Even if they are outside the 7-bit range, and even in the
> presence of the utf8 pragma.
>
> Try inserting real Unicode characters into the string, explicitl
Matt Lawrence wrote:
> Stefan Kühn wrote:
>
>>GERMAN UMLAUT HERE: ___\xFC\xFC\xFC___
>>
>>
> AFAIK, single-byte-width \xxx escapes are always treated as bytes, not
> as characters. Even if they are outside the 7-bit range, and even in the
> presence of the utf8 pragma.
>
> Try insert
Stefan Kühn wrote:
>GERMAN UMLAUT HERE: ___\xFC\xFC\xFC___
>
AFAIK, single-byte-width \xxx escapes are always treated as bytes, not
as characters. Even if they are outside the 7-bit range, and even in the
presence of the utf8 pragma.
Try inserting real Unicode characters into the string, ex
what does the browser tell you is the encoding of the page it is getting?
___
List: Catalyst@lists.rawmode.org
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/
Dev si
Thanks to all of you for Your postings. I have continued to investigate.
I found, that TT is not the reason. I can reproduce the problem in 4
simple steps just by using Catalyst.
1. Create a Catalyst application
catalyst.pl CatSimple
2. cd CatSimple
3. Create a Controller
script\catsimple_
Daniel McBrearty wrote:
>> It seems to me that Template-Toolkit does no UTF-8-encoding of the
>> outputted variables.
>>
>
> well, it shouldn't.
>
> In perl, strings are already utf8, internally. If TT was to do
> encoding, they would be double-encoded.
>
The internal encoding that perl us
On 05/09/07, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> >
> > This talk was great: http://vienna.yapceurope.org/ye2007/talk/552
> > Check out the slides of his talk.
> >
>
> looks interesting - where *are* the slides? no link from the page :-)
It was front-paged on use.perl.org recently:
http:/
I guess, you have to be a participant of the conference to access the
presentations. It has been similar with the german Perl Workshop.
On 9/6/07, Hartmaier Alexander <[EMAIL PROTECTED]> wrote:
> I couldn't find it yesterday when I did a quick search for it.
> Maybe you should mail Juerd.
--
--
I couldn't find it yesterday when I did a quick search for it.
Maybe you should mail Juerd.
-Alex
-Original Message-
From: Daniel McBrearty [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 10:40 PM
To: The elegant MVC web framework
Subject: Re: [Catalyst] TT and UN
>
> This talk was great: http://vienna.yapceurope.org/ye2007/talk/552
> Check out the slides of his talk.
>
looks interesting - where *are* the slides? no link from the page :-)
thanks!
___
List: Catalyst@lists.rawmode.org
Listinfo: http://lists.rawmod
On Wed, Sep 05, 2007 at 01:14:54PM +0200, Stefan Kühn wrote:
> On 9/5/07, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> > > QUESTION: Catalyst generates Perl files in the computer's standard
> > > encoding (which is cp1252). For *unicode best practice* it should be
> > > in UTF-8 encoded. Do you agree
Hi!
This talk was great: http://vienna.yapceurope.org/ye2007/talk/552
Check out the slides of his talk.
-Alex
-Original Message-
From: Matt Rosin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 3:15 PM
To: The elegant MVC web framework
Subject: Re: [Catalyst] TT and
Have you tried setting shell locale to utf8? A long time ago there
were utf8 in tt threads but I haven't had trouble myself.
However I have indeed had massive trouble trying to get a simple
question mark (a GET url) to print that I put in the stash, like you
are doing now, because tt would url-enco
> Obviously, the string variable reaches the stash correctly. I wrote
> it's content to a UTF-8 file and i found the result correctly.
then I don't know. you could try updating the libs, but I can tell you
that I've been using TT since mid last year, and had no problems - i
have heaps of utf8 stuf
On 9/5/07, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> >
> > It seems to me that Template-Toolkit does no UTF-8-encoding of the
> > outputted variables.
>
> well, it shouldn't.
>
Maybe i should adjust my statement:
__it looks like TT uses the wrong Encoding for the output of vars.__
Obviously,
>
> It seems to me that Template-Toolkit does no UTF-8-encoding of the
> outputted variables.
well, it shouldn't.
In perl, strings are already utf8, internally. If TT was to do
encoding, they would be double-encoded.
so what you have to do is get that u-with-umlaut *into* perl as a utf8
encoded
On 9/5/07, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> how your editor is actually writing that u-with-umlaut into the text
> file will also be a fatcor (it might be entering ISO-8859-1 or UTF8).
>
> try using the appropriate \x{ ... } way of writing the char to see if
> this is your problem.
NO
On 9/5/07, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> > QUESTION: Catalyst generates Perl files in the computer's standard
> > encoding (which is cp1252). For *unicode best practice* it should be
> > in UTF-8 encoded. Do you agree?
>
> AFAIK Catalyst itself doesn't generate any Perl files at all. B
if you are going to write unicode characters in your source code,
don't you need to say "use utf8;" or something?
http://search.cpan.org/~nwclark/perl-5.8.8/lib/utf8.pm
I'm not sure what the default is.Source code is ascii by default ,
AFAIK - if you are going to use something which is in the ext
how your editor is actually writing that u-with-umlaut into the text
file will also be a fatcor (it might be entering ISO-8859-1 or UTF8).
try using the appropriate \x{ ... } way of writing the char to see if
this is your problem.
On 9/5/07, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> if you a
Quoting Stefan Kühn <[EMAIL PROTECTED]>:
> NEXT TRY:
> * i saved the controller test.pm in UTF-8 encoding,
> * adapted the broken character ...
What do you mean by "adapted" ?
> * called the url
> * and it worked!
So I guess you just had the wrong filetype encoding then?
> QUESTION: Catalyst ge
Hi Tobias
i tried both of it, but still got the same result.
NEXT TRY:
* i saved the controller test.pm in UTF-8 encoding,
* adapted the broken character ...
* called the url
* and it worked!
QUESTION: Catalyst generates Perl files in the computer's standard
encoding (which is cp1252). For *unico
Quoting Stefan Kühn <[EMAIL PROTECTED]>:
> I have a problem when outputting special characters with
> Template-Toolkit and C::P::Unicode. I passed a simple template
> parameter from the controller to the view. The parameter contains a
> special character and is being garbled in the output.
> * In c
26 matches
Mail list logo
