You will be able to support more characters descriptors by using only
utf8 (ie: unicode) than trying to support individual charsets ** ie: if
you are resorting to entities, then you should simply use utf8 as they
both print the same character.
** I can say this from experience, eg: I had a req
Alex Teslik wrote:
> So I propose that the HTML::Template escaping does not squash HTML entities.
> Something like (quick off the cuff)
This seems like a very specific case to me. You are having a problem because
your text contains some HTML encoded things, but not all and because of the
limitati
On Wed, 19 Mar 2008 22:24:36 -0500, Karen wrote
> On 3/19/08, Alex Teslik <[EMAIL PROTECTED]> wrote:
>
> > But then I can no longer do all my escaping in the template.
>
> Well, you're effectively handing it a half-escaped string. That's
> kind of a special case.
I disagree. The string I'm givi
I completely agree. Unfortunately I've inherited a lot of the code and it
needs to support all charsets. :(
On Thu, 20 Mar 2008 14:31:54 +1100, Mathew Robertson wrote
> Have you tried using utf8 as the encoding? You will get far more
> millage out of utf8 than using entities.
>
> regards,
> Mat
Have you tried using utf8 as the encoding? You will get far more
millage out of utf8 than using entities.
regards,
Mathew
Alex Teslik wrote:
Hello,
I'm developing an app where there are some strings that have HTML entities
in them, such as:
This is a "Tést"
These strings need to go into
On 3/19/08, Alex Teslik <[EMAIL PROTECTED]> wrote:
> But then I can no longer do all my escaping in the template.
Well, you're effectively handing it a half-escaped string. That's kind
of a special case.
> So I propose that the HTML::Template escaping does not squash HTML entities.
That would
