You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Kalle Korhonen (JIRA)" <my...@incubator.apache.org> on 2005/09/02 20:15:27 UTC

[jira] Updated: (MYFACES-272) MyFaces unnecessary encodes all non-latin characters as numeric character references even if response character encoding is set to UTF-8

     [ http://issues.apache.org/jira/browse/MYFACES-272?page=all ]

Kalle Korhonen updated MYFACES-272:
-----------------------------------

    Attachment: myfaces-272-conditionallyEncodeChars.patch

This is a slightly modified version of the previous patch, built against MyFaces head on 09/01/05. Sean, I've tested with simple examples and I didn't see the double output you reported about (neither this or the previous patch should cause anything like that). Once again, it's tested with ISO-8859-1 and UTF-8 encodings set and 7 & 8-bit (in Latin-X character sets) and multibyte characters with verified results. Could it have been caused by something else (for example, I see double output regularly when reloading a modified page the first time when a previous component tree exists)? We'll continue to do our own testing and I report the results here, but I wanted to get the patch out for others to try it out first.

A tip for people trying it out, to properly set UTF-8, you need to use an encoding filter.

> MyFaces unnecessary encodes all non-latin characters as numeric character references even if response character encoding is set to UTF-8
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: MYFACES-272
>          URL: http://issues.apache.org/jira/browse/MYFACES-272
>      Project: MyFaces
>         Type: Improvement
>   Components: Implementation
>     Versions: 1.0.10m10
>     Reporter: Kalle Korhonen
>  Attachments: myfaces-272-conditionallyEncodeChars.patch
>
> Encoding all non-latin characters is unnecessary if the response specifies UTF-8 as character encoding and causes a major performance hit. Will provide a patch to do this only when UTF-8 is not used as encoding.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Updated: (MYFACES-272) MyFaces unnecessary encodes all non-latin characters as numeric character references even if response character encoding is set to UTF-8

Posted by Adam Winer <aw...@gmail.com>.
On 9/2/05, Kalle Korhonen (JIRA) <my...@incubator.apache.org> wrote:

> A tip for people trying it out, to properly set UTF-8, you need to use an encoding filter.

Why?  This shouldn't be necessary, since a JSF implementation should
restore the character encoding during Restore View.  (I think this is
in the spec, though I'm being lazy right now and not checking...)

Cheers,
Adam Winer