Hi Sung-Gu
Please take no offense in my posts. I have never questioned sanity of
URIUtil.encodeWithinQuery, however, I still have doubts about sanity of
UTIUtil.toUsingCharset method. And the fact that you have been ignoring my and Odi's
requests to provide a unit test for that method does not really help
One more time I'll try to present my point
Transformation in URIUtil.encodeWithinQuery does make perfect sense
------------------------------------------------------------------
ISO-8859-1 URLencode
Unicode string -----------> byte[] ------------> Unicode string
------------------------------------------------------------------
Transformation in URIUtil.toUsingCharset does make any sense to me
------------------------------------------------------------------
ISO-8859-1 UTF-8 (or any other encoding)
Unicode string -----------> byte[] ------------> Unicode string
------------------------------------------------------------------
I can well accept that I am not bright enough to get it, but I am trying. Maybe that
kind of transformation has its purpose when dealing with Asian alphabets, but for
European alphabets (including Cyrillic based) its absolutely useless.
So, please help me to see the light by providing a test unit
Cheers
Oleg
>Hi Oleg,
>
>You seems like got an answer... ;)
>
>BTW, the default should be just an default, when there is no set-up to be
>referred.
>
>That would be happened to be considered for the running configuration on the
>runtime...for applications or threads.
>
>Sung-Gu
>
>> + public static final String DEFAULT_CONTENT_CHARSET = "ISO-8859-1";
>
>> Index: PostMethod.java
>> + URIUtil.encodeWithinQuery (parameter.getName(), charset);
>
>---------------------------------------------------------------------
>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]
