Hi Jay,
the quoted source lines are correct, as the request parameters have
already been decoded by Tomcat using ISO-8859-1. So, you get the raw
values by paramValues[i].getBytes("ISO-8859-1") and do decode them
(again) using the configured encoding (browser dependent, mostly UTF-8)
in the String constructor.
I remember those lines, as I had another decoding problem with
ServletRequestImpl some time ago ;)
Regards, Thorsten
(Jay) Jun Yan wrote:
> If the encoding is customizable, it proves more that to have ISO-8895-1
> hardcoded is a bug of Jetspeed.
>
> Thanks,
>
> Jay
>
> On 7/23/06, Shinsuke SUGAYA <[EMAIL PROTECTED]> wrote:
>
>>
>> The encoding is customizable. You can find it in:
>> etc/sql/populate-db-default.sql
>>
>> INSERT INTO MEDIA_TYPE (MEDIATYPE_ID,NAME, CHARACTER_SET, TITLE,
>> DESCRIPTION)
>> VALUES(1,'html','UTF-8','HTML','Rich HTML for HTML 4.0 compliants
>> browsers');
>>
>> INSERT INTO MEDIA_TYPE (MEDIATYPE_ID,NAME, CHARACTER_SET, TITLE,
>> DESCRIPTION)
>> VALUES(2,'wml','UTF-8','WML','Format for mobile phones and PDAs
>> compatible
>> with WML 1.1');
>>
>> INSERT INTO MEDIA_TYPE (MEDIATYPE_ID,NAME, CHARACTER_SET, TITLE,
>> DESCRIPTION)
>> VALUES(3,'vxml','UTF-8','VoiceXML','Format suitable for use with an
>> audio
>> VoiceXML server');
>>
>> INSERT INTO MEDIA_TYPE (MEDIATYPE_ID,NAME, CHARACTER_SET, TITLE,
>> DESCRIPTION)
>> VALUES(4,'xml','','XML','XML 1.0');
>>
>> INSERT INTO MEDIA_TYPE (MEDIATYPE_ID,NAME, CHARACTER_SET, TITLE,
>> DESCRIPTION)
>> VALUES(5,'xhtml-basic','UTF-8','XHTML','XHTML Basic');
>>
>>
>> Thanks,
>> shinsuke
>>
>>
>> (Jay) Jun Yan wrote:
>> > I use Tomcat 5.5.
>> >
>> > I am not sure how pipeline parameters are encoded as a part of URL,
>> but
>> if
>> > they were always encoded in ISO-8895-1, that would be wrong, as that
>> would
>> > make to pass unicodes in URL impossible. On the contrary, if they were
>> > encoded in UTF-8, everybody would be happy.
>> >
>> > Any encoding related calls should use a customizable encoding, if
>> > situations
>> > like that UTF-8 is not good enough in the future are considered.
>> Otherwise,
>> > to use a hardcoded "UTF-8" would be better to use a haredcoded
>> "ISO-8895-1"
>> >
>> > Thanks,
>> >
>> > Jay
>> >
>> >
>> > On 7/22/06, Shinsuke SUGAYA <[EMAIL PROTECTED]> wrote:
>> >>
>> >> I'm not sure what web container you use.. But if I remember
>> correctly,
>> >> usually, parameters will be parsed by ISO-8859-1 to get pipeline
>> >> parameter.
>> >>
>> >> Thanks,
>> >> shinsuke
>> >>
>> >> (Jay) Jun Yan wrote:
>> >> > I am using Jetspee 2.0
>> >> >
>> >> > In org.apache.jetspeed.engine.servlet.ServletRequestImpl. 348855
>> >> > 2005-11-25
>> >> > 02:36:22Z ate
>> >> > Method getParameterMap, there is a line
>> >> > paramValues[i] = new
>> String(paramValues[i].getBytes("ISO-8859-1"),
>> >> > encoding);
>> >> >
>> >> > This is probably wrong, as it assumes parameters are ISO-8859-1
>> >> encoded,
>> >> > and
>> >> > that will cause UTF-8 encoded parameters, like
>> >> > request.jsp?name=%E9%A1%B9%E7%9B%AE
>> >> >
>> >> > be understood as "??", while actually it should be "项目"
>> (Project in
>> >> > Chinese)
>> >> >
>> >> > I changed it to use UTF-8 at my place.
>> >> >
>> >> > Any suggestion/comments?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Jay
>> >> >
>> >>
>> >> --------------------------------------
>> >> Let's start Yahoo! Auction - Free Campaign Now!
>> >> http://pr.mail.yahoo.co.jp/auction/
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> --------------------------------------
>> Let's start Yahoo! Auction - Free Campaign Now!
>> http://pr.mail.yahoo.co.jp/auction/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
