DO NOT REPLY [Bug 17125] - Character encoding problems

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17125>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17125

Character encoding problems





------- Additional Comments From shinsuke@yahoo.co.jp  2003-02-17 13:44 -------
Since Jetspeed has encoding issues, I proposed DefaultJetspeedParameterParser and 
JetspeedTemplatePage patch. But DefaultJetspeedParameterParser is commented out
in TurbineResources.properties. I think that Jetspeed will work fine if you set 
DefaultJetspeedParameterParser to services.RunDataService.default.parameter.parser.

I describe the encoding issue below:

 1) The page encoding is specified by content.defaultencoding in
JetspeedResources.properties.
    Applying the JetspeedTemplatePage patch, Jetspeed uses the encoding by the
following
    priorities.

     1. character-set parameter in media.xreg
     2. content.defaultencoding in JetspeedResources.properties
     3. UTF-8

    Using this encoding order, Jetspeed uses UTF-8 when media-type is text/html.
    Therefore Jetspeed can display a multibyte character(ex. Japanese) correctly
in the
    default environment. (For Jetspeed 1.4b3, user must change
content.defaultencoding
    in order to display the multibyte character correctly.)

 2) The form data is not parsed correctly.
    For example, in the HelloVelocity portlet, a multibyte character is displayed as
    "?" or garbage if user submits it. So the portlet developer needs to add a code
    for handling the correct encoding into the portlet. The cause is to parse
the form
    data by 8859_1. Therefore, using DefaultJetspeedParameterParser, the form data
    is parsed by correct encoding.(The portlet developer does not need to add
the special
    code) DefaultJetspeedParameterParser applies the following priorities when
determining
    a encoding information.

     1. the character encoding used in the body of the request.
     2. character-set parameter in media.xreg
     3. content.defaultencoding in JetspeedResources.properties
     4. US-ASCII

    In many cases, it will use the character-set parameter in media.xreg.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org