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 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
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_
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.
--
--
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,
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
. For *unicode best practice* it should be
in UTF-8 encoded. Do you agree?
Thanks
Stefan
On 9/5/07, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> Quoting Stefan Kühn <[EMAIL PROTECTED]>:
> > * In controller test.pm > added the following (note the German Umlaut)
> > sub index
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.
I studied the mailing list the whole afternoon, but coul
