Following up on a conversion I started on the DateTime mailing-list I'd like to
ask if it is really neccessary to use C::P::Unicode if a site uses
utf8-encoding?
I have the problem that up until now everything worked absolutely fine without
C::P::Unicode, Template::Stash::ForceUTF8,
On Thu, Aug 09, 2007 at 10:27:27AM +0200, Tobias Kremer wrote:
I have the problem that up until now everything worked absolutely fine without
C::P::Unicode, Template::Stash::ForceUTF8, Template::Provider::Encoding or any
ForceUTF8 is a hack hack hack. If your program doesn't work without it,
Hi,
On Aug 9, 2007, at 9:27 AM, Tobias Kremer wrote:
Following up on a conversion I started on the DateTime mailing-list
I'd like to
ask if it is really neccessary to use C::P::Unicode if a site uses
utf8-encoding?
I have the problem that up until now everything worked absolutely
fine
Pedro Melo wrote:
Hi,
On Aug 9, 2007, at 9:27 AM, Tobias Kremer wrote:
Following up on a conversion I started on the DateTime mailing-list
I'd like to
ask if it is really neccessary to use C::P::Unicode if a site uses
utf8-encoding?
Also if you use open(), make sure you use the three
Hi,
On Aug 9, 2007, at 10:40 AM, Tatsuhiko Miyagawa wrote:
Similarly even if your templates are encoded in utf-8,
Template-Toolkit doesn't know which encoding they are in, until you
set BOM to your templates or use Template::Provider::Encoding to
explicitly specify the encoding to decode the
Tobias,
I tried jrock's advice of adding C::P::Unicode to the Cat app you sent
me a couple days ago - and it does fix the encoding problem.
I also did that but it only works in some cases. Try adding a block element to
the FormFu YAML file (or a comment for the date element) that contains
Zitat von Tatsuhiko Miyagawa [EMAIL PROTECTED]:
Similarly even if your templates are encoded in utf-8,
Template-Toolkit doesn't know which encoding they are in, until you
set BOM to your templates or use Template::Provider::Encoding to
explicitly specify the encoding to decode the template.
On 09/08/07, Pedro Melo [EMAIL PROTECTED] wrote:
Hi,
On Aug 9, 2007, at 10:40 AM, Tatsuhiko Miyagawa wrote:
Similarly even if your templates are encoded in utf-8,
Template-Toolkit doesn't know which encoding they are in, until you
set BOM to your templates or use
I've been doing Japanese web pages for such a long time now, and yet I
still can't claim to have a full grasp of things.
But anyways, what I do is:
* All my templates are in unicode (open documents
with set enc=utf-8, NO BOM), as well as my FormFu
config files.
* I do NOT use
Zitat von Tatsuhiko Miyagawa [EMAIL PROTECTED]:
Similarly even if your templates are encoded in utf-8,
Template-Toolkit doesn't know which encoding they are in, until you
set BOM to your templates or use Template::Provider::Encoding to
explicitly specify the encoding to decode the template.
I
On Thu, Aug 09, 2007 at 02:56:31PM +0200, Tobias Kremer wrote:
I just found the (undocumented?) ENCODING configuration option in
Template::Provider. Setting this to utf-8 makes the templates appear
correctly with C::P::Unicode loaded. Is there still a need for
Template::Provider::Encoding?
In
View::TT
ENCODING: UTF-8
Template provider will see you are running a modern Perl (UNICODE flag
in provider) and then look for a Byte Order Mark. If not found it
will then decode your content based on the ENCODING setting.
No, you don't need Template::Provider::Encoding if you only
On Thu, Aug 09, 2007 at 02:56:31PM +0200, Tobias Kremer wrote:
Zitat von Tatsuhiko Miyagawa [EMAIL PROTECTED]:
Similarly even if your templates are encoded in utf-8,
Template-Toolkit doesn't know which encoding they are in, until you
set BOM to your templates or use
On Thu, Aug 09, 2007 at 04:42:53PM +0200, Tobias Kremer wrote:
View::TT
ENCODING: UTF-8
Template provider will see you are running a modern Perl (UNICODE flag
in provider) and then look for a Byte Order Mark. If not found it
will then decode your content based on the ENCODING
On 8/9/07, Tobias Kremer [EMAIL PROTECTED] wrote:
View::TT
ENCODING: UTF-8
Template provider will see you are running a modern Perl (UNICODE flag
in provider) and then look for a Byte Order Mark. If not found it
will then decode your content based on the ENCODING setting.
No,
15 matches
Mail list logo
