You're right, I asked this yesterday.
I thought the problem was the way JSF was delivering its HTML content, but I
searched further and found that it was not JSF per se but the
MyFaces-Tomahawk library using the extended components marked with the <t:
tag. It uses a filter which converts all response to HTML encoding,
changing the strings like más to mÿs which I presume is a mistake, I
will investigate further in this direction.
Besides, how I write a post to tell everyone about this findings.
On Nov 28, 2007 10:33 AM, Matt Raible <[EMAIL PROTECTED]> wrote:
> I believe you asked this question yesterday. If you haven't received an
> answer yet, it's probably because no one knows the answer. You might try the
> Facelets mailing list (I'd use Nabble).
> Matt
>
> On Nov 28, 2007, at 7:15 AM, Carlos Ortiz wrote:
>
> Hi you all
>
> I am running the construction of a requirement that has embedded
> javascript, like this
>
> *<html>
> <head>
> <script language="JavaScript">
> function doOnKeyPress() {
> alert("Esto es más");
> }
>
> </script>
> </head>
> ...normal jsf content here*
>
>
> I am using the
> *<%@ page session="false" contentType="text/html;charset=ISO-8859-1"%> *
> and also the
> <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>
> But when I see the page rendered to the client, that is, see what HTML
> code JSF (I am using Tomahawk 1.6) has generated,
> the javascript line where *alert("Esto es más"); *resides gets HTML
> encoded as alert("Esto es mÿs"); and all that I want is to show the
> message as "Esto es más"
>
> Question is, What do I have to do to tell JSF engine to not HTML encode
> the resulting page, that is, emit bytes as written in the backing JSP file?
>
> Any help is appreciated.
>
>
>
