DO NOT REPLY [Bug 17125] New: - 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

           Summary: Character encoding problems
           Product: Jetspeed
           Version: 1.4b4-dev /CVS
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Portlet Container
        AssignedTo: jetspeed-dev@jakarta.apache.org
        ReportedBy: sami@netorek.fi


I built our portal against the current CVS codebase of Jetspeed, and found out 
that the newest version of JetspeedTemplatePage class (updated 4 days ago) 
introduces some character encoding problems. Our system uses ISO-8859-1 as the 
character encoding, and it seems that Jetspeed performs an extraneous ISO-8859-
1 -> UTF-8 conversion before feeding the HTTP request data to the portlets.

For example, when I enter a word "p�iv�" ("day" in Finnish) to a form field 
named "word", a call to runData.getParameters().getString("word") 
returns "päivä".

I reverted to the earlier version of JetspeedTemplatePage class, and the 
problem disappeared. I also tried if removing the hard-coded value "UTF-8" from 
the MimeType class would solve this problem, but it did not have any effect. 
The "content.defaultencoding" property in my JR.p contains value "iso-8859-1", 
so the form data should be supplied as ISO-8859-1, shouldn't it?

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