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/08/09 18:27:36 UTC

[jira] Commented: (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=comments#action_12318183 ] 

Kalle Korhonen commented on MYFACES-272:
----------------------------------------

I'm very surprised that this change could cause double output, unless, you intentionally set the encoding to UTF-8 in header and then back to Latin-1 with a page directive which can lead to unpredictable results. Anyway, I have a little more elegant patch for this which we've been successfully using for months. Will check the examples and commit a new patch.

> 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: JSF 1.1
>     Versions: Nightly Build
>     Reporter: Kalle Korhonen
>      Fix For: Nightly Build
>  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